On Thu, Dec 29, 2011 at 1:18 PM, Frank Swarbrick <[email protected]> wrote: > I agree, it looks like the original file is encoded in small-endian UTF-16. > If the file is generated on a Windows system and there's no way to change the > creating software to use UTF-8 or an ASCII code page (I'm betting there is, > if one looks hard enough) you can probably use Windows Notepad to convert > it. Just open it in Notepad, so a "Save As" and change the Encoding from > Unicode (which is UTF-16) to ANSI. > > But in the end, it really should be up to the system that creates the file to > have an ANSI/ASCII option...
I've seen this a lot from Microsoft stuff -- export a Registry key, for example, and look at it on Windows and you'll see this. I suspect the encoding is the right answer. -- zMan -- "I've got a mainframe and I'm not afraid to use it" ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
