On 08/21/08 12:23, "Jung-Tsung Shen" <[EMAIL PROTECTED]> wrote:
> On 8/21/08, Maxwell, Adam R <[EMAIL PROTECTED]> wrote:
>
>> In BibTeX, you should generally use {\`e} instead of \`{e}, but that's
>> beside the point :). You can change encoding of .ris files using iconv in
>> Terminal, or open the files in a text editor and resave with a different
>> encoding.
>
> \`{e} seems to work well for me so far. :D
http://newton.ex.ac.uk/tex/pack/bibtex/btxdoc/node3.html
See item 4 in the list. Another reason for using the {\`e} idiom is that
BibDesk can convert it to รจ for display in the interface, and back to {\`e}
when you save.
> Couldn't BibDesk open the file first, gives me some proper warning,
> and allow me to modify *within* BibDesk? For a naive end-user, it
> should always go like this:
>
> double click a file -> BibDesk opens it, regardless of the encoding
> etc, but warns you that there are some problems in what fields -> the
> end-user manually corrects the errors within BibDesk.
>
> Of course, it would be much better if BibDesk could also do the last
> step for me. :-)
Encoding errors are serious, because BibDesk has no idea how extensive the
problems are. Hence it takes the safest approach and bails out on opening
the file, rather than allowing you to continue and likely corrupt your data.
In fact, I originally got involved in BibDesk development to try and fix an
encoding corruption bug that messed up my .bib file!
--
Adam
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
