Re: [toolbox] Extended Attributes
Status: Planning
Brought to you by:
jlaurens
From: Will R. <wi...@gu...> - 2005-07-05 23:09:48
|
On 6 Jul 2005, at 8:26 AM, Maxwell, Adam R wrote: > And this is one of the reasons we use OS X, right? BTW, one of the =20= > reasons we want to get BibDesk away from using BibTeX as a storage =20 > format is that PDF files and such can be linked as aliases, so =20 > renaming and moving them outside the app is transparent. What would this mean? That when you saved a BibDesk document, it =20 would automatically export from its own fancy doc format to .bib in =20 the same breath? I guess that's transparent enough... >>> Why put the name of the master file in the slaves if TeX doesn't =20 >>> need it (or maybe it does...I'm not much of a TeXpert)? >> >> So that when you open up the chapter file you're working on that =20 >> doesn't have anything but document text, you can still hit =20 >> "Typeset" and have something come out :) > > Right, but is that specific to the front end, or does TeX itself =20 > use that info? I use iTeXMac's projects to define a master file, =20 > so I've not explored putting this stuff in the file. Oh, sorry, I though you were asking about the utility of the =20 metadata, not where it's put. >>> I think XeTeX accepts either UTF-16 or UTF-8. Also, trying to =20 >>> read Latin 1 files in as UTF-8 will cause an error in Cocoa, and =20 >>> you get nothing back (although this is arguably better than the =20 >>> corruption you get when reading MacOSRoman as UTF-8 or something). >> >> In that case, it sounds like a "checksum" string at the end of the =20= >> document that is unique for each encoding (is this even possible?) =20= >> is the only way to do it if the information is going to be kept in-=20= >> file. > > Not sure if that's possible; you're thinking of something along the =20= > lines of the Unicode BOM?. Apple and Omni Group both have tools =20 > for sniffing text encoding, but it's a pretty dodgy business at best. I guess I was thinking along the lines of writing a string like abcABC=E9=EE=FC=F8=E7... at the very end of the document, and depending what encoding the file =20= is, this would be represented as a different stream of bytes. I would =20= be surprised if it works, however, since the encodings map to =20 different character sets so you wouldn't be able to write the same =20 string in each of them. Oops. Will |