coderanger
02-17-2007, 10:02 PM
Hi All,
I hope you don't mind me asking for help on this subject here, as it really
doesn't have anything to do with AMS, other than the converter will be
used with AMS and will be given to this community for free when finished.
The reason I'm asking this here, is because I know we have a couple of
pretty smart programmers in here, and you guys may have the answer I'm
looking for.
OK, so as I mentioned the other day, I'm having a programmer friend of mine
create a utility app for me that can convert Unicode text to ANSI and back,
so I can work with these file types in my AMS program I'm creating.
BUT, we have discovered something that MS has done, and we are getting
lost as to what the answer might be.
OK, so first, my buddy creates an app that will convert Unicode text files into
ANSI text files, so I can read them into my AMS app. All seems to work fine
until I export the text to his app, and it converts it to Unicode.
Now, the Unicode is right in one sense, but if I try to open the file that was
once readable in Windows WordPad, it is now not readable in WordPad.
It's readable in the new NotePad that comes with XP, but no longer readable
in Windows WordPad.
So, we mess around and find out that there is an invisible character that
needs to be the first character of the file for Windows WordPad to read it
correctly.
OK so now, we add this extra hidden character, and sure enough, WordPad
can again read the file, and the file is readable by human eyes.
..BUT, it is no longer readable in Windows NotePad. Now, if I hit "Save" in
Windows WordPad, I can then read it in Windows NotePad.
What in the world is going on here?
Does anyone have any insight on this matter?
I would really appreciate any help you might be able to give.
Thanks,
Patrick
I hope you don't mind me asking for help on this subject here, as it really
doesn't have anything to do with AMS, other than the converter will be
used with AMS and will be given to this community for free when finished.
The reason I'm asking this here, is because I know we have a couple of
pretty smart programmers in here, and you guys may have the answer I'm
looking for.
OK, so as I mentioned the other day, I'm having a programmer friend of mine
create a utility app for me that can convert Unicode text to ANSI and back,
so I can work with these file types in my AMS program I'm creating.
BUT, we have discovered something that MS has done, and we are getting
lost as to what the answer might be.
OK, so first, my buddy creates an app that will convert Unicode text files into
ANSI text files, so I can read them into my AMS app. All seems to work fine
until I export the text to his app, and it converts it to Unicode.
Now, the Unicode is right in one sense, but if I try to open the file that was
once readable in Windows WordPad, it is now not readable in WordPad.
It's readable in the new NotePad that comes with XP, but no longer readable
in Windows WordPad.
So, we mess around and find out that there is an invisible character that
needs to be the first character of the file for Windows WordPad to read it
correctly.
OK so now, we add this extra hidden character, and sure enough, WordPad
can again read the file, and the file is readable by human eyes.
..BUT, it is no longer readable in Windows NotePad. Now, if I hit "Save" in
Windows WordPad, I can then read it in Windows NotePad.
What in the world is going on here?
Does anyone have any insight on this matter?
I would really appreciate any help you might be able to give.
Thanks,
Patrick