ascii to unicode line endings

[fidtz]

The code:

import codecs

udlASCII = file("c:\\temp\ \CSVDB.udl",'r' )
udlUNI = codecs.open("c: \\temp\\CSVDB2. udl",'w',"utf_1 6")

udlUNI.write(ud lASCII.read())

udlUNI.close()
udlASCII.close( )

This doesn't seem to generate the correct line endings. Instead of
converting 0x0D/0x0A to 0x0D/0x00/0x0A/0x00, it leaves it as 0x0D/
0x0A

I have tried various 2 byte unicode encoding but it doesn't seem to
make a difference. I have also tried modifying the code to read and
convert a line at a time, but that didn't make any difference either.

I have tried to understand the unicode docs but nothing seems to
indicate why an seemingly incorrect conversion is being done.
Obviously I am missing something blindingly obvious here, any help
much appreciated.

Dom

[fidtz]

On 2 May, 17:29, Jean-Paul Calderone <exar...@divmod .comwrote:

On 2 May 2007 09:19:25 -0700, [e-mail].u k wrote:

The code:

import codecs

udlASCII = file("c:\\temp\ \CSVDB.udl",'r' )
udlUNI = codecs.open("c: \\temp\\CSVDB2. udl",'w',"utf_1 6")

udlUNI.write(ud lASCII.read())

udlUNI.close()
udlASCII.close( )

This doesn't seem to generate the correct line endings. Instead of
converting 0x0D/0x0A to 0x0D/0x00/0x0A/0x00, it leaves it as 0x0D/
0x0A

I have tried various 2 byte unicode encoding but it doesn't seem to
make a difference. I have also tried modifying the code to read and
convert a line at a time, but that didn't make any difference either.

I have tried to understand the unicode docs but nothing seems to
indicate why an seemingly incorrect conversion is being done.
Obviously I am missing something blindingly obvious here, any help
much appreciated.

Consider this simple example:

>>import codecs
>>f = codecs.open('te st-newlines-file', 'w', 'utf16')
>>f.write('\r\n ')
>>f.close()
>>f = file('test-newlines-file')
>>f.read()

'\xff\xfe\r\x00 \n\x00'

>>>

And how it differs from your example. Are you sure you're examining
the resulting output properly?

By the way, "\r\0\n\0" isn't a "unicode line ending", it's just the UTF-16
encoding of "\r\n".

Jean-Paul

I am not sure what you are driving at here, since I started with an
ascii file, whereas you just write a unicode file to start with. I
guess the direct question is "is there a simple way to convert my
ascii file to a utf16 file?". I thought either string.encode() or
writing to a utf16 file would do the trick but it probably isn't that
simple!

I used a binary file editor I have used a great deal for all sorts of
things to get the hex values.

Dom

[Jerry Hill]

On 2 May 2007 09:19:25 -0700, fi***@clara.co. uk <fi***@clara.co .ukwrote:

The code:

import codecs

udlASCII = file("c:\\temp\ \CSVDB.udl",'r' )
udlUNI = codecs.open("c: \\temp\\CSVDB2. udl",'w',"utf_1 6")
udlUNI.write(ud lASCII.read())
udlUNI.close()
udlASCII.close( )

This doesn't seem to generate the correct line endings. Instead of
converting 0x0D/0x0A to 0x0D/0x00/0x0A/0x00, it leaves it as 0x0D/
0x0A

That code (using my own local files, of course) basically works for me.

If I open my input file with mode 'r', as you did above, my '\r\n'
pairs get transformed to '\n' when I read them in and are written to
my output file as 0x00 0x0A. If I open the input file in binary mode
'rb' then my output file shows the expected sequence of 0x00 0x0D 0x00
0x0A.

Perhaps there's a quirk of your version of python or your platform? I'm running
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit
(Intel)] on win32

--
Jerry

[fidtz]

On 3 May, 13:00, Jean-Paul Calderone <exar...@divmod .comwrote:

On 3 May 2007 04:30:37 -0700, [e-mail].u k wrote:

On 2 May, 17:29, Jean-Paul Calderone <exar...@divmod .comwrote:

On 2 May 2007 09:19:25 -0700, [e-mail].u k wrote:

The code:

import codecs

udlASCII = file("c:\\temp\ \CSVDB.udl",'r' )
udlUNI = codecs.open("c: \\temp\\CSVDB2. udl",'w',"utf_1 6")

udlUNI.write(ud lASCII.read())

udlUNI.close()
udlASCII.close( )

This doesn't seem to generate the correct line endings. Instead of
converting 0x0D/0x0A to 0x0D/0x00/0x0A/0x00, it leaves it as 0x0D/
0x0A

I have tried various 2 byte unicode encoding but it doesn't seem to
make a difference. I have also tried modifying the code to read and
convert a line at a time, but that didn't make any difference either.

I have tried to understand the unicode docs but nothing seems to
indicate why an seemingly incorrect conversion is being done.
Obviously I am missing something blindingly obvious here, any help
much appreciated.

Consider this simple example:

>>import codecs
>>f = codecs.open('te st-newlines-file', 'w', 'utf16')
>>f.write('\r\n ')
>>f.close()
>>f = file('test-newlines-file')
>>f.read()
'\xff\xfe\r\x00 \n\x00'

And how it differs from your example. Are you sure you're examining
the resulting output properly?

By the way, "\r\0\n\0" isn't a "unicode line ending", it's just the UTF-16
encoding of "\r\n".

Jean-Paul

I am not sure what you are driving at here, since I started with an
ascii file, whereas you just write a unicode file to start with. I
guess the direct question is "is there a simple way to convert my
ascii file to a utf16 file?". I thought either string.encode() or
writing to a utf16 file would do the trick but it probably isn't that
simple!

There's no such thing as a unicode file. The only difference between
the code you posted and the code I posted is that mine is self-contained
and demonstrates that the functionality works as you expected it to work,
whereas the code you posted is requires external resources which are not
available to run and produces external results which are not available to
be checked regarding their correctness.

So what I'm driving at is that both your example and mine are doing it
correctly (because they are doing the same thing), and mine demonstrates
that it is correct, but we have to take your word on the fact that yours
doesn't work. ;)

Jean-Paul

Thanks for the advice. I cannot prove what is going on. The following
code seems to work fine as far as console output goes, but the actual
bit patterns of the files on disk are not what I am expecting (or
expected as input by the ultimate user of the converted file). Which I
can't prove of course.

>>import codecs
testASCII = file("c:\\temp\ \test1.txt",'w' )
testASCII.wri te("\n")
testASCII.clo se()
testASCII = file("c:\\temp\ \test1.txt",'r' )
testASCII.rea d()

'\n'
Bit pattern on disk : \0x0D\0x0A

>>testASCII.see k(0)
testUNI = codecs.open("c: \\temp\\test2.t xt",'w','utf16' )
testUNI.write (testASCII.read ())
testUNI.close ()
testUNI = file("c:\\temp\ \test2.txt",'r' )
testUNI.read( )

'\xff\xfe\n\x00 '
Bit pattern on disk:\0xff\0xfe \0x0a\0x00
Bit pattern I was expecting:\0xff \0xfe\0x0d\0x00 \0x0a\0x00

>>testUNI.close ()

Dom

[fidtz]

On 3 May, 13:39, "Jerry Hill" <malaclyp...@gm ail.comwrote:

On 2 May 2007 09:19:25 -0700, [e-mail].u k <[e-mail]. ukwrote:

The code:

import codecs

udlASCII = file("c:\\temp\ \CSVDB.udl",'r' )
udlUNI = codecs.open("c: \\temp\\CSVDB2. udl",'w',"utf_1 6")
udlUNI.write(ud lASCII.read())
udlUNI.close()
udlASCII.close( )

This doesn't seem to generate the correct line endings. Instead of
converting 0x0D/0x0A to 0x0D/0x00/0x0A/0x00, it leaves it as 0x0D/
0x0A

That code (using my own local files, of course) basically works for me.

If I open my input file with mode 'r', as you did above, my '\r\n'
pairs get transformed to '\n' when I read them in and are written to
my output file as 0x00 0x0A. If I open the input file in binary mode
'rb' then my output file shows the expected sequence of 0x00 0x0D 0x00
0x0A.

Perhaps there's a quirk of your version of python or your platform? I'm running
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit
(Intel)] on win32

--
Jerry

Thanks very much! Not sure if you intended to fix my whole problem,
but changing the read mode to 'rb' has done the trick :)

Dom

[Marc 'BlackJack' Rintsch]

In <11************ **********@p77g 2000hsh.googleg roups.com>, fidtz wrote:

>>>import codecs
testASCII = file("c:\\temp\ \test1.txt",'w' )
testASCII.wr ite("\n")
testASCII.cl ose()
testASCII = file("c:\\temp\ \test1.txt",'r' )
testASCII.re ad()

'\n'
Bit pattern on disk : \0x0D\0x0A

>>>testASCII.se ek(0)
testUNI = codecs.open("c: \\temp\\test2.t xt",'w','utf16' )
testUNI.writ e(testASCII.rea d())
testUNI.clos e()
testUNI = file("c:\\temp\ \test2.txt",'r' )
testUNI.read ()

'\xff\xfe\n\x00 '
Bit pattern on disk:\0xff\0xfe \0x0a\0x00
Bit pattern I was expecting:\0xff \0xfe\0x0d\0x00 \0x0a\0x00

>>>testUNI.clos e()

Files opened with `codecs.open()` are always opened in binary mode. So if
you want '\n' to be translated into a platform specific character sequence
you have to do it yourself.

Ciao,
Marc 'BlackJack' Rintsch