Peter Prymmer <[EMAIL PROTECTED]> writes:
>Hi,
>
>I've finally been looking at the Encode module and I am
>somewhat perplexed by the stuff at the head of the Encode/*.enc
>files.
The Tcl documentaion needs PODifying or some such.
Attached is a 1st stab at this generated by hacking at the Tcl n
Peter> Also: since the .enc files seem to have adopted the four hex digit
Peter> per code point format how is the Encode module going to handle
Peter> UTF16 surrogates?
I haven't looked into the format for .enc files, but another thing that
happens for example, is more that a single
On Wed, 25 Oct 2000, Philip Newton wrote:
> I didn't read up on the format, but I would gess that this maps from
> EBCDIC position to Unicode in this way: take the EBCDIC code point and
> treat it as an index into an array of four-character Unicode code points.
> In which case, your table looks
On 25 Oct 2000, at 15:32, Nick Ing-Simmons wrote:
> The next line
> identifies the type of encoding file. It can be one of the following
> letters:
>
> =item "[1]
>
> =item "[2]
>
> =item "[3]
>
> =item "[4]
You seem to have dropped the letters in the transcoding nroff-to-pod,
which is bad
Philip Newton <[EMAIL PROTECTED]> writes:
>On 25 Oct 2000, at 15:32, Nick Ing-Simmons wrote:
>
>> The next line
>> identifies the type of encoding file. It can be one of the following
>> letters:
>>
>> =item "[1]
>>
>> =item "[2]
>>
>> =item "[3]
>>
>> =item "[4]
>
>You seem to have dropped t
Nick> Following the first page will be all the other pages, each in the
Nick> same format as the first: one number identifying the page followed
Nick> by 256 double-byte Unicode characters. If a character in the
Nick> encoding maps to the Unicode character , it means that the
Mark Leisher <[EMAIL PROTECTED]> writes:
>Peter> Also: since the .enc files seem to have adopted the four hex digit
>Peter> per code point format how is the Encode module going to handle
>Peter> UTF16 surrogates?
>
>I haven't looked into the format for .enc files, but another thing tha
Nick> I would be delighted if people start fixing or improving the
Nick> prototype - but we really want to prove that the API is "suitable"
Nick> for actual use (by XS modules like Tk, PerlIO, EBCDIC, ...).
I have been itching to implement this myself for quite a while now. But like
On Tue, 24 Oct 2000, Peter Prymmer wrote:
> I am curious about the viability of an EBCDIC based .enc file so
> I took the Encode/iso8859-1.enc and came up with one that I
> might call Encode/cp1047.enc. Would this be the correct form/format?
> If so I can prepare this and a cp37.enc and a posix-
