Mod Loader

Both Fabric and Forge (I confirm that I have tested both loaders and will specify both loader versions below)

Minecraft Version

1.20.1

Botania version

1.20.1-440

Modloader version

(any)

Modpack info

No response

The latest.log file

(n/a)

Issue description

The translation file zh_tw.json is very outdated.

Community help to update it would be appreciated.

Steps to reproduce

No response

Other information

No response

Additionally, the Chinese language files both seems to not link a lot of the entry references that are linked in the English language file. I've seen various instances where only $(item)…$(0) is used for the color formatting, but the actual $(l:…)…$(/l) notation for the link itself is missing.

Sure, fine by me.

I mean, using an automated converter is a good first step for "good enough" traditional translations. I'm happy to review the output of that and make adjustments if someone runs it for me.

Okay, in fact, MS Office can solve this issue. if @TheRealWormbo agrees, I'll try to get it done in a week.

I understand what you are saying about this situation, because some complicated Chinese characters were indeed discarded in the simplification process. But it doesn't matter, every Chinese user will be able to get the meaning of a sentence based on the characters of the whole sentence. Even if the order of the characters in a whole sentence is completely messed up. Amazing, isn't it?

The only meme you need to be aware of is that many of the memes inside the language files are Japanese. A lot of Japanese characters evolved from the Chinese language of the Tang Dynasty, and there are quite a lot of Chinese characters preserved there (even if they don't mean what they used to mean nowadays).Don't change the Chinese characters in the Japanese text, the rest just need to be converted for each character.

That sounds like running the entire file through an "uninformed" converter might break things. So whatever I end up doing with this, it'll have to involve verifying the source language of each entry.

emmmmm，The expressions don't really make any difference. As I said above, Simplified Chinese and Traditional Chinese are just simplified font structures, there is no modification to the structure of the Chinese language. zh_cn is the official Chinese standardized characters. zh_tw is Standard Form of National Characters, Chinese: 國字標準字體. As for the others, they are just characters used by various Chinese immigrants or special settlements, which have very few users compared to the first two. Here are some ....historical reasons.

Relevant Literature:
https://en.wikipedia.org/wiki/Debate_on_traditional_and_simplified_Chinese_characters
https://en.wikipedia.org/wiki/Chinese_language
https://en.wikipedia.org/wiki/Standard_Form_of_National_Characters
https://en.wikipedia.org/wiki/Traditional_Chinese_characters

Huh?In fact, the point I want to make is that the difference between Traditional Chinese and Simplified Chinese is not that great. The former is used in ancient China, parts of Guangdong, and Hong Kong and Taiwan. The latter is mainly used in mainland China for the standardized script of modern Chinese. Therefore the vast majority of Simplified Chinese users can read Traditional Chinese, and most Traditional Chinese users can read Simplified Chinese. The relationship between the two is not as you might think ....(What's the best analogy I can use?)It's not as if the difference between Shakespeare's Middle English and modern English is as great as you might think.

The solution to this problem you mentioned is also very simple. Look for a Simplified Chinese to Traditional Chinese converter. Convert all the Simplified Chinese characters inside zh_cn.json to Traditional Chinese characters, copy them to zh_tw.json, and then everything is done.

According to (English) Wikipedia (https://en.wikipedia.org/wiki/Ambiguities_in_Chinese_character_simplification), conversion from traditional to simplified is (almost) unambiguous, but the other way around might not be. That and us simply having no idea about the Chinese language and its writing systems means we have no way to verify the result.

I'll take your word for automatic conversion being good enough, but having someone verify the result (if we want to keep supporting the language at all) would be nice.

Additionally, the Chinese language files both seems to not link a lot of the entry references that are linked in the English language file. I've seen various instances where only $(item)…$(0) is used for the color formatting, but the actual $(l:…)…$(/l) notation for the link itself is missing.

This is something I've been thinking about, but ultimately manpower is limited. It doesn't matter though, in the Chinese mod community(https://www.mcmod.cn/class/332.html), I've gone over the detailed usage and description of each item according to the update history. As for the Chinese file, in the previous update I just strictly translated it against the en_us.json file so that the lines corresponded to each other. But rechecking these (what I consider unimportant) links would be a very laborious and time-consuming task.
My point is that for old entry references, I wouldn't bother checking and updating them. If there are updated language file entries, I then update the corresponding entries within zh_cn.json.

According to (English) Wikipedia (https://en.wikipedia.org/wiki/Ambiguities_in_Chinese_character_simplification), conversion from traditional to simplified is (almost) unambiguous, but the other way around might not be. That and us simply having no idea about the Chinese language and its writing systems means we have no way to verify the result.

I'll take your word for automatic conversion being good enough, but having someone verify the result (if we want to keep supporting the language at all) would be nice.

When Traditional Chinese is converted to Simplified Chinese, only the structure of individual characters is changed, without any adjustment to the language rules.

So you can convert and verify with confidence.

Understandable about the links, I updated the German translation from an ancient state. It was… a process.

As far as conversion is concerned, I'll have to do some research, since most sites seem to be very limited. Even the one I found that allows file upload has a limitation on file size that zh_cn.json exceeds by a reasonable amount. I've also seen comments that it's a bit like British and American English, in that there are somewhat different expressions. That appears to be the reason for people to maintain four different Chinese variants of Wikipedia, two for each character set.

I do want to eventually generate an upside-down English language file, so maybe looking into automating the process of character conversion in the form of a script might be a good idea.

That sounds like running the entire file through an "uninformed" converter might break things. So whatever I end up doing with this, it'll have to involve verifying the source language of each entry.

Here's the thing, the accurate proofreading of translated documents is a top priority, and it's a step that can't be bypassed in any way. No matter what method you use, even if it's a manual line-by-line, word-by-word translation, it's imperative that someone else proofreads your translated documents.
But using the approach I described above can be extremely efficient. If you find a person who understands Chinese, such as @williewillus , I believe he will agree with me.

#4828

Closed via merge of #4828.