Nicholas Clark <[EMAIL PROTECTED]> wrote:
On Tue, Jul 26, 2005 at 08:48:10AM -0700, rajarshi das wrote:> > For the code points being tested> > ("\x{0442}\x{0435}\x{0441}\x{0442}")> > does the perl source file contain the correct byte> > sequence in UTF-EBCDIC?> Yes it does, since I ran the test, >
On Wed, Jul 27, 2005 at 11:01:08PM +0100, Nicholas Clark wrote:
> My question is, what are the bytes in UTF-EBCDIC that encode code point 3500?
http://www.unicode.org/reports/tr16/
I *think* codepoint 3500, ie 0xdac, ie [0011][01101][01100]
maps to the i8 bytes
1110[0011] 101[01101] 101[01100],
--- rajarshi das <[EMAIL PROTECTED]> wrote:
>
>
> --- Nicholas Clark <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Jul 26, 2005 at 08:34:02AM -0700, rajarshi
> > das wrote:
> >
> > > Yes, the second call to NATIVE_TO_UTF is still
> > present
> > > in the modified code. Typically, one wouldnt
> wa
On Thu, Jul 28, 2005 at 02:37:36AM -0700, rajarshi das wrote:
> However, if I change the first instance to :
> --- utf8.c 2004-11-17 18:22:09.0 +0530
> +++ utf8.c.22005-07-28 13:48:24.0 +0530
> @@ -363,6 +363,11 @@ Perl_utf8n_to_uvuni(pTHX_ U8 *s,
> STRLEN
> warnin
--- Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 28, 2005 at 02:37:36AM -0700, rajarshi
> das wrote:
>
> > However, if I change the first instance to :
> > --- utf8.c 2004-11-17 18:22:09.0
> +0530
> > +++ utf8.c.22005-07-28 13:48:24.0
> +0530
> > @@ -363,6 +3
On Thu, Jul 28, 2005 at 12:35:13AM -0700, rajarshi das wrote:
> Nicholas Clark wrote:
>> If you put those 3 bytes directly between the '{' and '}' characters in
>> the EBCDIC version of that 1 liner, does it also print 3500?
> I am unable to put those three bytes in the 1-liner you mentioned above
