On Fri, Aug 19, 2005 at 05:01:04PM +0530, Sastry wrote:
Hi Nicholas
With reference to my previous mail on encoding module
use Encode;
$string = a;
$enc_string = encode(iso-8859-16, $string);
print \n String: $string\n;
print \n enc_string: $enc_string\n;
a)How different are those
On Fri, Aug 19, 2005 at 05:51:10PM +0530, Sastry wrote:
Hi
The test case uses the invariant character that is below 127 on
ISO-8859-16 codepage. Since character 'a' has a codepoint of 129 on
EBCDIC, is there a place in the code where it should apply
NATIVE_TO_ASCII macro on the input
Hi Nicholas
With reference to my previous mail on encoding module
use Encode;
$string = a;
$enc_string = encode(iso-8859-16, $string);
print \n String: $string\n;
print \n enc_string: $enc_string\n;
a)How different are those ext/Encode/def_t.c and
ext/Encode/Byte/byte_t.c files in EBCDIC and
Hi
The test case uses the invariant character that is below 127 on
ISO-8859-16 codepage. Since character 'a' has a codepoint of 129 on
EBCDIC, is there a place in the code where it should apply
NATIVE_TO_ASCII macro on the input character?
-Sastry
On 8/19/05, Nicholas Clark [EMAIL
On Wed, Aug 10, 2005 at 02:11:45PM +0530, Sastry wrote:
On 8/9/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Tue, Aug 09, 2005 at 10:58:48AM +0530, Sastry wrote:
$enc_string = encode(iso-8859-16, $string);
So $enc_string should be a single byte, 97, everywhere.
Can you suggest some
On 8/9/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Tue, Aug 09, 2005 at 10:58:48AM +0530, Sastry wrote:
Hi
I get 73 printed on EBCDIC platform. I think it is supposed to print
129 as it is the numeric equivalent of 'a'.
-Sastry
On 8/8/05, Nicholas Clark [EMAIL PROTECTED]
Hi
I get 73 printed on EBCDIC platform. I think it is supposed to print
129 as it is the numeric equivalent of 'a'.
-Sastry
On 8/8/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Thu, Aug 04, 2005 at 11:51:44AM +0530, Sastry wrote:
Hi
I am running the following script on EBCDIC
On Tue, Aug 09, 2005 at 10:58:48AM +0530, Sastry wrote:
Hi
I get 73 printed on EBCDIC platform. I think it is supposed to print
129 as it is the numeric equivalent of 'a'.
-Sastry
On 8/8/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On your EBCDIC platform, what does this give?
Hi Nicholas Clark
I agree that it is supposed to print the numerical equivalent 97.
I attempted to see if there is any bug in the encode module.
Surprisingly, I noticed that there are two .c files in
ext/Encode/def_t.c and ext/Encode/Byte/byte_t.c which are generated
using enc2xs. They are
On Thu, Aug 04, 2005 at 11:51:44AM +0530, Sastry wrote:
Hi
I am running the following script on EBCDIC
use Encode;
$string = a;
$enc_string = encode(iso-8859-16, $string);
print \n String: $string\n;
print \n enc_string: $enc_string\n;
The output:
String: a
enc_string: ñ (This
Hi
I am running the following script on EBCDIC
use Encode;
$string = a;
$enc_string = encode(iso-8859-16, $string);
print \n String: $string\n;
print \n enc_string: $enc_string\n;
The output:
String: a
enc_string: ñ (This is the character for codepoint \xF1 on iso-8859-16)
What is the
11 matches
Mail list logo
