Hmm, I must've had some other syntax in mind there, yenc only has verbatim
encoding for most stuff in the regular text range it seems, or at least
that's how it appears when looking at the provided sample zips.
But yeah, to enter whitespace manually, hex all the way. Definitely not
R6RSs decimal-based syntax.
EDIT: Nevermind that comment about the regular text range, it's always
shuffled around. I really had a totally different encoding in mind there.
On Fri, 22 Oct 2010 17:14:57 +0200, John Cowan <[email protected]>
wrote:
Magnus Achim Deininger scripsit:
=ybegin<text>=yend
<text> is mostly the blob contents verbatim, i.e. without converting it
to hex first, except for some special characters.
According to http://www.yenc.org/yenc-draft.1.3.txt , the format is
much more complex than that (involving multiple lines and keywords on
the header and trailer lines) and the contents are *not* verbatim: for
example, #x00 is encoded as '*' and #x32 (digit '2') is encoded as 'T'.
Furthermore, there is a hidden dependency on the character encoding of
a file in which yEnc objects are embedded: the encoded form of #x7E is
whatever character has a codepoint at #xA8 in that encoding, which is
not necessarily U+00A8.
If we must have blob syntax at all, I agree that hex is The Right Thing,
but allowing interspersed whitespace.
_______________________________________________
Chicken-hackers mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-hackers
