ASS (Advanced SubStation Alpha) and its predecessor SSA are the styled subtitle formats fansub groups favour. A file is split into sections. [Script Info] holds the title and resolution, [V4+ Styles] defines styles with their font, size and colours, and in [Events] each Dialogue line is one subtitle. Override tags such as {\pos(320,50)} or {\fn黑体} can sit in the middle of the text.
What is converted
- The dialogue text of Dialogue lines in
[Events]. Phrases split by override tags are still converted as phrases, so in the karaoke line{\k25}台{\k25}风(typhoon) the 台 becomes 颱, not 臺 or 台:{\k25}颱{\k25}風. - Comment lines (optional, on by default).
- The Title in
[Script Info].
What stays the same
- Style names and font names. Dialogue lines refer to styles by name, so a renamed style would no longer be found.
- Override tags
{…}, including the font name after\fn, the line break\Nand the hard space\h. - Embedded data in
[Fonts]and[Graphics]. - The Encoding field of each style, unless you turn on the switch between 134 (GB2312) and 136 (Big5) under Advanced options by format.
Garbled subtitles and player support
Older subtitles often use GBK or Big5. The converter detects the encoding and writes UTF-8, which mpv, VLC, PotPlayer and IINA all read correctly. Because the font names are untouched, players still find the fonts the subtitles ask for, and embedded fonts stay in the file. In the examples below, 微软雅黑 after \fn stays in Simplified while the dialogue around it becomes Traditional.
Conversion examples
| Original | Result |
|---|---|
| 我们的软件更新了。 | 我們的軟件更新了。 |
| {\fn微软雅黑\b1}头发{\b0}很长 | {\fn微软雅黑\b1}頭髮{\b0}很長 |
| 第一行\N第二行的发展 | 第一行\N第二行的發展 |
| {\k25}台{\k25}风{\k25}过{\k25}后 | {\k25}颱{\k25}風{\k25}過{\k25}後 |
| {\pos(320,50)}画面上方的说明 | {\pos(320,50)}畫面上方的說明 |
Real output from OpenCC (s2t).
How to use
- Drop .ass or .ssa files onto the page, or click Choose files. Several files can go in at once.
- Choose the direction and standard, for example S→T and Taiwan to turn Simplified subtitles into Taiwan Traditional.
- If needed, open Advanced options by format and decide whether to convert Comment lines and whether to switch the style Encoding.
- Check the preview, download, and play the subtitles once to make sure the styling is intact.
Things to check
- Comment lines are converted by default. If you keep the original text or notes in Comment lines and want them untouched, turn off “ASS/SSA: also convert Comment lines”. Karaoke Templater lines (Comment lines whose Effect starts with template, code or mixin) are code and are never converted.
- Translator notes written inside curly braces count as override tags and are not converted. Change them by hand if you need to.
- Even a phrase match can pick the wrong form. 头发还没干 (my hair isn't dry yet) becomes 頭髮還沒幹: 頭髮 is right, but 幹 should be 乾. Converted files show no highlights, so watch the whole episode through before you release it.
FAQ
Why were the font names not converted?
Players look fonts up by name. If 微软雅黑 became 微軟雅黑, it would no longer match the font installed on the computer, so font names in styles and after \fn in override tags are kept as they are.
Can I convert subtitles with embedded fonts?
Yes. The embedded data in the [Fonts] and [Graphics] sections is kept as it is, and only the dialogue is converted.
Will karaoke effects break?
No. The syllable timing tags stay the same, and characters separated by those tags are still converted as one phrase.
Should I change the Encoding field of the styles?
It is left alone by default. If your subtitles need it to match the script, turn on the switch under Advanced options by format. 134 (GB2312) then becomes 136 (Big5) when converting to Traditional, and the other way round when converting to Simplified.
Are both ASS and SSA supported?
Yes. .ass and .ssa files follow the same rules.