Re: [toolbox] Extended Attributes

[Adam R. M. <ama...@ma...>]

On Jul 6, 2005, at 04:41, J=E9r=F4me Laurens wrote:

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

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

Personally, I don't care about other systems, but if they must be =20
considered for the mactextoolbox, why not add another piece of =20
metadata?  Store a path and an alias in the plist.

>>
>>
>>> 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.
>>
>
> Or an ascii name?

If you can write into the byte stream without corrupting it...

Adam