企评社

Interface labels are shown in English. Company reviews, forum posts and tool descriptions are currently available in Chinese only.

Simplified / Traditional Chinese

Simplified and traditional both ways · mainland, Taiwan standard and Hong Kong · word-level conversion · custom word lists

OpenCC 词典在你的浏览器里运行,文本不上传、刷新即清空

转换方向

词典:尚未加载(首次转换时自动加载约 1.1MB 的 OpenCC 词典,之后走浏览器缓存)

自定义词表(可选,用来强制指定术语)

写法:原词=替换词(=、→、-> 或制表符分隔都行),# 开头的行会被忽略。 生效顺序:先按你的词表替换 → 再按所选方向转换 → 最后再套一次你的词表,所以原词写成简体或繁体都能命中;同一个原词写多次时以最后一行为准。

输入文本(本地转换,不上传)

转换结果(实时)

四种繁体口径的差别(都有实测例子)

方向 口径 例子(简体 → 结果)
简体 → 繁体(通用) 传统字形,不换用词 软件 → 軟件 · 鼠标 → 鼠標 · 里面 → 裏面 · 面条 → 麪條
简体 → 台湾正体 台湾字形,不换用词 软件 → 軟件 · 鼠标 → 鼠標 · 里面 → 裡面 · 面条 → 麵條
简体 → 台湾正体 + 用词 字形与词汇都按台湾说法 软件 → 軟體 · 鼠标 → 滑鼠 · 打印机 → 印表機 · 内存 → 記憶體
简体 → 香港繁体 香港字形习惯 里面 → 裏面 · 台灯 → 枱燈
繁体 → 简体(4 个方向) 合并回简体,字形不再区分地区 裏面 / 裡面 → 里面 · 麪條 / 麵條 → 面条 · 枱燈 / 檯燈 → 台灯
往返不可逆是正常现象:繁体转简体是「多对一」,同一个简体字可能对应多个繁体写法。例如把香港的「裏面」转成简体得到「里面」,再转回台湾正体就变成「裡面」——原文的「裏」回不来了;「麪條 / 麵條」「枱燈 / 檯燈」同理。需要严格往返对照时,请以简体文本作为中间基准,并保留原始文件。
词典的边界:OpenCC 是词典加规则,按词表逐条匹配、不理解上下文,人名、公司名、地名、网络新词与生僻术语都可能不合预期。关键的专有名词请写进上面的「自定义词表」强制指定,转换后再人工过一遍。

FAQ

There are several simplified-to-traditional modes - what is the difference between cn→tw and cn→twp?

The difference is whether only the glyph changes or the vocabulary too. In 'Simplified → Taiwan Traditional (glyph only)' only the character forms follow Taiwan conventions and the wording stays: 软件 → 軟件, 鼠标 → 鼠標, 打印机 → 打印機. In 'Simplified → Taiwan Traditional + Taiwan terms' the words are localised as well: 软件 → 軟體, 鼠标 → 滑鼠, 打印机 → 印表機, 内存 → 記憶體, 视频 → 影片. Hong Kong and general Traditional also differ subtly: 'inside' is 裏面 in general Traditional and Hong Kong but 裡面 in Taiwan Traditional; 'desk lamp' is 檯燈 in general Traditional but 枱燈 in Hong Kong. For copy aimed at Taiwan readers choose Traditional plus Taiwan terms; for pure glyph unification (e.g. re-encoding old material) general Traditional or Taiwan Traditional alone is enough.

Is the conversion guaranteed correct? Could names and technical terms be broken?

Not 100% guaranteed. The tool uses OpenCC's dictionaries plus rules (loaded locally); it matches word lists item by item without understanding context, so the same character may convert differently in different sentences, and personal, company and place names, new internet slang and industry jargon may not turn out as expected. Observed cases: 干杯 correctly becomes 乾杯, and 树干/干活 becoming 樹幹/幹活 are right too, but 干涉 alone stays 干涉 while inside 继续干涉 it becomes 繼續幹涉; the idiom 一干二净 is in the dictionary and becomes 一乾二淨. Recommended workflow: convert everything first, then proofread key nouns; for fixed terminology, put it in the 'custom dictionary' to force the mapping so the built-in dictionary cannot alter it.

Why is the round trip not identical to the original?

Because traditional-to-simplified is many-to-one, and the reverse direction cannot tell which original form was used. For example Hong Kong's 裏面 converts to 里面, and converting back with the Taiwan profile yields 裡面 - the original 裏 is gone; 麪條 vs 麵條, and Hong Kong's 枱燈 vs general Traditional's 檯燈 behave the same way. For round-trip comparisons, keep simplified text as the pivot and preserve the source files.

Is my text uploaded? How long can it be? How do I write a custom dictionary?

No upload. The dictionary and conversion all run in your browser: the text never leaves your machine, refreshing clears it, and the page makes no network requests (the first use loads a dictionary of about 1.1MB once, afterwards the browser cache serves it). Up to 1,000,000 characters per run; measured, 1,000,000 characters simplified→traditional take about 0.1 seconds (traditional→simplified is faster, about 20 milliseconds). The custom dictionary is one entry per line as source=target (separated by an equals sign, arrow or tab; lines starting with # are ignored), and parse failures report which line and where. Entries apply in three passes: first your dictionary rewrites the input, then the chosen direction converts, then your dictionary applies once more - so a source term written in either script takes effect; if a source term repeats, the last line wins.

Related tools