Re: [toolbox] Extended Attributes
Status: Planning
Brought to you by:
jlaurens
From: Will R. <wi...@gu...> - 2005-07-05 22:19:47
|
On 6 Jul 2005, at 7:03 AM, Maxwell, Adam R wrote: > If you store aliases as data in a plist, though (BDAlias is handy > for this), renaming isn't a problem for the front-end specific info. Ooo, that sounds much nicer than hard coded links at the top of the document...(even if they are relative) > Why put the name of the master file in the slaves if TeX doesn't > 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 doesn't have anything but document text, you can still hit "Typeset" and have something come out :) > I think XeTeX accepts either UTF-16 or UTF-8. Also, trying to read > Latin 1 files in as UTF-8 will cause an error in Cocoa, and you get > nothing back (although this is arguably better than the 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 document that is unique for each encoding (is this even possible?) is the only way to do it if the information is going to be kept in-file. Will |