Re: [toolbox] Extended Attributes

[<jer...@u-...>]

Le 6 juil. 05, =E0 00:19, Will Robertson a =E9crit :

> 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=20=

>> 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=20
> document...(even if they are relative)

This is not a portable solution. Aliases are mac specific.
A solution viable on other systems must also be considered

In the iTM2 I am implementing, nothing is put in the header...

>
>> Why put the name of the master file in the slaves if TeX doesn't need=20=

>> 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 "Typeset"=20=

> and have something come out :)

The problem comes from multipart documents, should the whole document=20
be typeset or only the chapter (if relevant)
We can think of books made with collections of disconnected articles.=20
It that case, it really makes sense to either typeset the whole=20
document or only one chapter...

>
>> I think XeTeX accepts either UTF-16 or UTF-8.  Also, trying to read=20=

>> Latin 1 files in as UTF-8 will cause an error in Cocoa, and you get=20=

>> nothing back (although this is arguably better than the corruption=20
>> 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?) is=20=

> the only way to do it if the information is going to be kept in-file.

Or an ascii name?