Re: ASCII vs. MacRoman (was Re: Standard Additions 'read' command - basic questions)
Re: ASCII vs. MacRoman (was Re: Standard Additions 'read' command - basic questions)
- Subject: Re: ASCII vs. MacRoman (was Re: Standard Additions 'read' command - basic questions)
- From: Walter Ian Kaye <email@hidden>
- Date: Tue, 20 Jan 2004 06:55:31 -0800
At 01:08p +0100 01/20/2004, Axel Luttgens didst inscribe upon an
electronic papyrus:
To be more precise, the default was "read ... as text ...", which
happened to provide that mapping between characters and bytes.
Now, it seems that the stream may be structured through the unicode
encoding scheme under certain circumstances; should this really be
the case, this would be a departure from the default behavior as
soon as you are handling bytes with values in the range 128-255.
In the above, Chris N. said the bug is that the delimiter is
erroneously fetched as unicode, so that a search for a unicode
sequence is undertaken.
But this also means that the traditional "as text" default was
defeated, as the code started a search for groups of bytes...
Should the class of the delimiter define the interpretation of a
file contents?
Should the "as ..." part (defaulting to some class -which one?)
induce a coercion of the delimiter?
Should the "as... " and the delimiter mandatoryly be of the same class?
Should the idea of byte-per-byte access to any file just be abandoned?
What -- and give up binary data?
-boo
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.