Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
End Users
Pocket PCActiveSyncMultimediaEBooksWirelessSmartPhones
Developers
Windows MobileSmartPhonesWinCE ProgrammingVB for WinCEVC++ for WinCEPlatform BuilderTest Tools
PocketPC DirectoryFree SoftwareWeb Resources
Related Topics
PalmMobile PhonesMore Topics ...

Pocket PC Forum / End Users / ActiveSync / February 2005

Tip: Looking for answers? Try searching our database.

utility to copy Unicode files to PPC

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rafael Humpert - 26 Feb 2005 13:45 GMT
As is well known, ActiveSync since version 3.0 is unable to copy files with
Unicode filenames to/from a Windows CE device.

Dave Johnston made a very promising free little utility that can copy a file
with a Unicode filename to the PocketPC. It's still in beta but for this
purpose it works well:

pocketpaste
http://www.johnsto.co.uk/pocketpc.php

The utility also can copy the clipboard content to a new file on the PPC
preserving Unicode date. Unfortunately PocketWord doesn't play along. As of
the 0.27 beta version the format of the newly created file is UTF-8, and
this is not understood by PocketWord.

PocketWord of Windows Mobile can only correctly open UCS encoded Unicode
text files. Likewise the PHM Notepad.
Beverly Howard [Ms-MVP/MobileDev] - 26 Feb 2005 18:06 GMT
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]
Beverly Howard [Ms-MVP/MobileDev] - 26 Feb 2005 18:10 GMT
...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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.