On Jan 25, 10:30 am, [EMAIL PROTECTED] (Chas. Owens) wrote:
> On Jan 25, 2008 10:06 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> snip> Great! both worked. The thing I still don't understand is that in the
> > file the BOM is FFFE not FEFF
>
> snip
>
> This is because it is little endian, if
On Jan 25, 2008 10:06 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
snip
> Great! both worked. The thing I still don't understand is that in the
> file the BOM is FFFE not FEFF
snip
This is because it is little endian, if it were a big endian file it
would be FEFF. The character is the same,
On Jan 24, 7:35 pm, [EMAIL PROTECTED] (Dr.Ruud) wrote:
> [EMAIL PROTECTED] schreef:
>
> > [...] I'm reading an unicode utf-16le file and have successfully
> > done so but with one issue. When I print the first line of input the
> > BOM is still there...
>
> By specifying the "le", you express that
[EMAIL PROTECTED] schreef:
> [...] I'm reading an unicode utf-16le file and have successfully
> done so but with one issue. When I print the first line of input the
> BOM is still there...
By specifying the "le", you express that you already know the byte
order.
The U+FEFF is then read as the "
I'm at a lost... I still need to do some learning about unicode but
basically I'm reading an unicode utf-16le file and have successfully
done so but with one issue. When I print the first line of input the
BOM is still there... I was thinking that the BOM would be striped off
during the open then
