Microsoft Custom Translator：简体中文TMX文件上传失败问题

Since you’ve already nailed the EN-Spanish workflow successfully, let’s focus on the specific quirks that might be tripping up your EN-Simplified Chinese upload. Here’s a step-by-step breakdown of things to check:

• Validate language code consistency in filenames and TMX content
  Microsoft Custom Translator can be picky about language code formatting, especially for Chinese variants. Double-check:

  • Filename language suffixes: Stick to the platform’s preferred codes—for Simplified Chinese, it’s usually zh-Hans or zh-CN (avoid plain zh if possible). Compare this to your working EN-Spanish filenames (you likely used en and es which are straightforward for that pair).
  • TMX internal language tags: Open your .tmx file in a text editor and verify the <tuv xml:lang="..."> attributes. For EN-SC, they should match something like <tuv xml:lang="en-US"> and <tuv xml:lang="zh-Hans">. Mismatched codes here (even if your filename is correct) will cause upload failures.

• Check TMX file structure and validity
  Even if the file looks intact, subtle XML errors can break uploads for non-Latin language pairs:

  • Use a TMX validator (many free offline/online tools exist) to confirm your file adheres to TMX 1.4b or 2.0 standards (Custom Translator supports both). Look for unclosed tags, invalid characters, or malformed <tu> entries.
  • Ensure your Chinese content doesn’t contain hidden control characters or encoding artifacts—these are easy to miss but can crash the parser.

• Verify file encoding and size

  • Encoding: TMX files must be UTF-8 encoded (preferably without BOM). If your Chinese TMX was saved in GBK or another regional encoding, re-save it as UTF-8 using a tool like Notepad++ or VS Code.
  • Size precision: Some OSes display file sizes in decimal MB (1000^3 bytes), but Custom Translator uses binary MiB (1024^3 bytes). A file showing 49.9MB in your file explorer might actually exceed the 50MiB (52,428,800 bytes) limit. Right-click the file to check its exact byte count and trim content if needed.

• Rule out browser/environment issues

  • Try uploading in an incognito/private browser window to eliminate cached data or extension conflicts. Sometimes leftover session data from your EN-Spanish project can interfere with new language pair uploads.
  • Switch to a different browser (Chrome, Edge, Firefox) to rule out browser-specific bugs in the new Custom Translator interface.

• Cross-reference with your working EN-Spanish setup
  Compare the exact structure of your successful EN-Spanish TMX files with the failing EN-SC ones:

  • Are the filename patterns identical (e.g., MasterX_source_target.tmx)?
  • Do the TMX headers and language tags follow the same format?
  • Did you use the same text editor/tool to generate both sets of files? A small difference in how you saved the Chinese files could be the culprit.

内容的提问来源于stack exchange，提问作者maria c laguardia