#360 interpret latex sequences for export

[michel_cuendet]

When exporting to rtf or Endnote XML, the latex sequences apprearing in author names and titles should be interpreted. Some latex sequences are a must when using bibdesk with latex, such as accents and enforcing capital letters (see example below). I suppose Endnote can handle accents, but I don't know if it deals with capitalization in titles... All I know is that it is a pain to change everything by hand...

Thanks,

Michel Cuendet

Example:

Energetics of ion conduction through the {K}+ channel (article)
Author
S. Bern\`eche and B. Roux
Journal
Nature
Year
2001
Volume
414
Pages
73

[Adam Maxwell]

Logged In: YES
user_id=732757
Originator: NO

In general, you should enter accents in BibDesk directly. If you use the correct BibTeX idiom of {\`e}, BibDesk will convert your characters from Unicode to LaTeX and vice versa, and you'll always see the Unicode form in the UI (and, I believe, EndNote/RIS export), and always have the LaTeX form in your .bib file. This can be disabled in the Files preferences.

The braces around the {K} should probably be removed, though, if we're not doing that.

[Christiaan Hofman]

Logged In: YES
user_id=1162009
Originator: NO

The nature of template handling makes it impossible to automatically interpret this. Moreover we cannot possibly write a latex interpreter for this. We could possibly create modifier keys to do tex character conversion (though this would not handle your example, as it does not contain the necessary braces).

[Christiaan Hofman]

Logged In: YES
user_id=1162009
Originator: NO

In fact this is already supported. The keys are stringByTeXifyingString and stringByDeteXifyingString. I'll add that to the help.

[Adam Maxwell]

Logged In: YES
user_id=732757
Originator: NO

Missed the part about the rtf template; I was commenting on the EndNote XML question. That uses the deTeXified strings, right?

For templates, it might make sense to implicitly deTeXify everything (if possible), since the TeX stuff is only useful in TeX. The user could then use stringByTeXifyingString to force TeXification.

[Christiaan Hofman]

Logged In: YES
user_id=1162009
Originator: NO

Whether you want to texify or detexify in the export determines entirely on the type of template you have. Also you may not want to detexify for all fields. Eg if you want to export bibtex you'd want it texified. The string in the field may or may not be texified, as a value can be entered in either form.

Also note that we just use KVC to get values of a field, and this is used in other places. So we cannot simply return a detexified value just for templating, as this would affect other things as well.