Add zh_TW Traditional Chinese locale

[PeterDaveHello]

🎉

[mitchellh]

Do you accept being on the zh_TW localization team @PeterDaveHello for future review?

[PeterDaveHello]

Do you accept being on the zh_TW localization team @PeterDaveHello for future review?

Sure!

[pluiedev]

Don't really have further comments as a dumb mainlander — ideally we should have one more person willing to step up as a maintainer before we'd accept these

[PeterDaveHello]

@pluiedev I can help maintain it ;)

[pluiedev]

Yeah, what I mean is that we should ideally have one other person to serve as a co-translator or a proofreader to ensure the quality of translations.

[PeterDaveHello]

Ideally, every role should have at least one backup. However, I'm unsure if this should be a strict requirement in practice. As you know, this is an open-source project supported by volunteers. Therefore, perhaps we can consider it as an additional, non-mandatory task.

[PeterDaveHello]

Another thought that may be helpful: as an open source projects maintainer who doesn't understand more than two languages, those frontier LLMs are my friends to help proofread. They may not be able to translate perfectly, but they're very helpful in checking whether the translations are understandable, reasonable, and improved.

[mitchellh]

Another thought that may be helpful: as an open source projects maintainer who doesn't understand more than two languages, those frontier LLMs are my friends to help proofread. They may not be able to translate perfectly, but they're very helpful in checking whether the translations are understandable, reasonable, and improved.

Yeah absolutely. I'd love to see a GH bot or something (maybe it exists) that does this specifically for PO files since they're an all known format. I do it manually right now (I've run a handful of our PRs through an LLM) and its helpful but having something more automated and in the loop would be a great help.

[PeterDaveHello]

Yeah absolutely. I'd love to see a GH bot or something (maybe it exists) that does this specifically for PO files since they're an all known format. I do it manually right now (I've run a handful of our PRs through an LLM) and its helpful but having something more automated and in the loop would be a great help.

Maybe take a look at https://www.qodo.ai/ and https://coderabbit.ai/, though they aren't designed for the po files, they absolutely can and will help review translation, additionally, also for the other changes in the project.

[PeterDaveHello]

@mitchellh @pluiedev, with respect, is there any chance we can move on? As there seemed to be merge conflict now, I'm not sure if it should be resolved ;)

[pan93412]

Awesome translation! There are just a few points to discuss :)

Regarding the merge conflict issues, I suggest discarding the file i18n.zig, rebasing to the main branch, and then reapplying this patch. After that, this PR will be mergeable, and the maintainer won't need to rebase it manually.

git am 0001-l10n-add-zh-TW-entry.patch

0001-l10n-add-zh-TW-entry.patch

[pan93412]

I propose 分割窗格, where 窗格 is pane:

A pane is a (usually) independently scrollable subsection of a window.

[pan93412]

"Change Title…" might open a new popup that allows users to change the title. In this case, I suggest using three dots for a shorter menu label.

[pan93412]

According to the behavior of this button, I propose 切出 <direction> 窗格 so users understand its function. For example, 切出左窗格. "向上分割" often does not convey its meaning clearly.