if all it is doing is converting unicode to ascii, you can do the same
from the pc's dos prompt using the command;
TYPE filename.ext > asciifilename.ext
Beverly Howard [MS MVP-Mobile Devices]
...should point out that the command line utility is a "pure ascii"
generator... not sure how a word doc would process, but have used the
command for converting XP registry files from unicode to ascii so that
the keys are usable in win9x registries.
Would be interested in knowing how a unicode doc file fares using this
approach.
Beverly Howard [MS MVP-Mobile Devices]
Rafael Humpert - 26 Feb 2005 19:31 GMT
That's a different problem. I'm talking about copying a file with a filename
using a broad spectrum of the Unicode caracters residing on the PC over to a
PPC.
The point here is to NOT convert Unicode to ANSI, because that will possibly
lead to loss of information and thus mangle the filename. That happens with
ActiveSync: Any characters not in the system default codepage are converted
to ?'s and this translated filename is sent to the PC or PPC respectively.
Of course such an operation fails.
For example you may have such a filename on the PC:
Testname??????????.txt
If you try to copy this to the PPC using ActiveSync and if your PC system
default locale is Western European, ActiveSync will convert this to
Testname??????????.txt
If your system default locale is Japanese it will be converted to something
like this:
Testname??????????.txt
So, such a filename can't be copied or synchronized with ActiveSync since
version 3.
Thus the need for sth like PocketPaste.
(I encode this post in UTF8, hopefully your reader can display it correctly)
> command for converting XP registry files from unicode to ascii so that the
> keys are usable in win9x registries.
Rafael Humpert - 26 Feb 2005 19:41 GMT
Ok I tried to post this but it seems that Outlook Express mangles Unicode as well despite being set to UTF encoding. I try again, this time as HTML format. Hopefully it works. Anyway, it just illustrates the point...
---
That's a different problem. I'm talking about copying a file with a filename
using a broad spectrum of the Unicode caracters residing on the PC over to a
PPC.
The point here is to NOT convert Unicode to ANSI, because that will possibly
lead to loss of information and thus mangle the filename. That happens with
ActiveSync: Any characters not in the system default codepage are converted
to ?'s and this translated filename is sent to the PC or PPC respectively.
Of course such an operation fails.
For example you may have such a filename on the PC:
=8F=E8=98=8C=A4.text
If you try to copy this to the PPC using ActiveSync and if your PC system
default locale is Western European, ActiveSync will convert this to
=8F=E8=98????.text
If your system default locale is Japanese it will be converted to something
like this:
??????=A4.text
So, such a filename can't be copied or synchronized with ActiveSync since
version 3.
Thus the need for sth like PocketPaste.
(I encode this post in UTF8, hopefully your reader can display it correctly)
> command for converting XP registry files from unicode to ascii so that the
> keys are usable in win9x registries.
Rafael Humpert - 26 Feb 2005 19:47 GMT
I mixed up the Western European and the Japanese example. Sorry. This is for Western locale ??????=B6=A1.text and this for Japanese =84=A1=8F=E8=98????.text