Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Attempts to copy a file through ActiveSync that includes Vietnamese characters in its name from a Windows XP desktop computer to a Windows Mobile device will fail. The file will not be copied, nor will there be any errors indicating that a copy operation was ever attempted. The same problem also applies to files that include complex script characters (e.g., Arabic, Hebrew, Thai, etc) and all Indic language characters (south-east Asian scripts such as Devanagari, Tamil, Malayalam, etc).

Steps to reproduce the problem:

1. Create a document that includes Vietnamese characters in its name.

2. Use ActiveSync to connect the PC to a Windows Mobile 6.0 device.

3. Attempt to copy the file from the PC to the Windows Mobile 6.0 device using the ActiveSync Explorer utility.

When attempting to copy a file through ActiveSync, whose name includes Vietnamese characters, the file will not be transferred to the Windows Mobile 6.0 device. No error message will be displayed indicating that the file operation failed.

This is a known limitation of ActiveSync. ActiveSync is Code Page based and it needs to have matching System Locales (LNUP: Language for Non-Unicode Program) in both the destop and the device. ActiveSync does not support cross languages scenarios including file copies and sync operations and Office Mobile document fidelity.



For ActiveSync to work properly in the above scenarios the following must be true:

• The Windows Mobile device System Locale and desktop Windows LNUP must be matched. The language used on the desktop must match the language used in the Windows Mobile device.
• Characters used in files for desktop ActiveSync should be in the supported list of the System Locale code pages. See list below for Windows Mobile 6.0:

This is a current design limitation of ActiveSync.

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.