Brian Dessent wrote:
Yuck. Why don't you just use iconv instead?
Cuz, I thought it was only a library? :-?
Cuz I already know windows starts in UCS-2 and know the codepage
for UTF-8 (65001). With iconv, I don't know off the top of my head
where to look for what document that specifies the
On Tue, Nov 14, 2006 at 02:58:15PM -0800, Brian Dessent wrote:
>Linda Walsh wrote:
>>Right now, to convert an NT text file in UCS-2 format, in bash, I use:
>>
>>mode.com codepage select=65001 reg export hklm\\software hklm-sw.reg5
>>cmd /c type hklm-sw.reg5 > hklm-sw-utf8.txt
>
>Yuck. Why don't yo
Linda Walsh wrote:
> Right now, to convert an NT text file in UCS-2 format, in bash,
> I use:
>
> mode.com codepage select=65001
> reg export hklm\\software hklm-sw.reg5
> cmd /c type hklm-sw.reg5 > hklm-sw-utf8.txt
Yuck. Why don't you just use iconv instead?
> What ever happened to the UTF-8
Right now, to convert an NT text file in UCS-2 format, in bash,
I use:
mode.com codepage select=65001
reg export hklm\\software hklm-sw.reg5
cmd /c type hklm-sw.reg5 > hklm-sw-utf8.txt
It isn't perfect -- any UCS-2 entries that are not valid UTF-16
won't get converted properly (since they don't
4 matches
Mail list logo