On Nov 8, 2011, at 14:10, Christiaan Hofman wrote: > On Nov 8, 2011, at 22:56, Daniel Becker wrote: > >> Am 06.11.2011 um 09:38 schrieb Daniel Becker:
[re: TeXShop encoding comment] >>> Having to remember to use the File -> open dialogue every time I am opening >>> an UTF8-encoded file is not very convenient. (I almost every time try to >>> double-click, then get the warning about utf8, ....) > > It's fragile. It gives just some indication, nothing more. It's not a > standard, very far from it. We actually do use something that is a standard > on Mac to show you the warning. But even that is still fragile, an > indication, that's why we ask you about how to handle it. Just to reinforce what Christiaan wrote: the extended attribute that BibDesk uses is quite fragile, since not all APIs read or write it, and I think you can easily end up with a stale value of it (not from BibDesk, but from a text editor or some other process, like iconv). Exactly the same problem applies to the encoding-as-comment line, and if BibDesk supported one, it would be more useful to accept multiple styles as Python does: # -*- coding: latin-1 -*- # vim: set fileencoding=latin-1 # encoding: utf-8 I'm still against it because of the potential for data loss; encoding corruption in my bib file is actually the reason I started contributing to BibDesk back in 2003 or so. It's much better to have the onus on the user to determine encoding, so BibDesk doesn't get blamed for destroying files. -- Adam ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
