Codeberg/Community
54
325
Fork
You've already forked Community
12

Weblate: Add the Taiwanese language variant #2137

Closed
opened 2025年09月16日 19:17:51 +02:00 by juliancoffee · 8 comments

Describe the problem

Ok, so I couldn't figure out where to put it, so I figured out I can put it here. (moved from Weblate Infrastructure repo)

The problem is that Weblate treats all Traditional Chinese as one language by default. This feels a bit limiting when some contributors from other countries, like Taiwan, want to translate on their own.

We added both of them without really knowing what we're getting ourselves into, and now we frequently can't touch component configuration, because Weblate sees two components made for one language, which is a validation error.

Solution brainstorm

зображення
Press this button to add a new language

зображення
And fill the form like that

Describe alternatives you have considered

Well, there are a few "solutions".

First one is to maintain the "status quo" and just say that the Taiwanese Chinese language variant doesn't exist.
The second one is what we currently use, which is to use a language filter and filter out Taiwanese, but I couldn't figure out how to do that, so right now we're filtering out regular Traditional Chinese instead.

I get that the first option is seductive and maybe even more "rational", but I think it should be up to translators and project maintainers, not up to the Codeberg org, with all respect.

Screenshots

зображення
Example of an alert, which then causes an error, if we want to modify the component in any way

Additional context

No response

### Describe the problem Ok, so I couldn't figure out where to put it, so I figured out I can put it here. (moved from Weblate Infrastructure repo) The problem is that Weblate treats all Traditional Chinese as one language by default. This feels a bit limiting when some contributors from other countries, like Taiwan, want to translate on their own. We added both of them without really knowing what we're getting ourselves into, and now we frequently can't touch component configuration, because Weblate sees two components made for one language, which is a validation error. ### Solution brainstorm ![зображення](/attachments/f173e0ef-5feb-4583-bcdd-44d716ce7979) Press this button to add a new language ![зображення](/attachments/92f28720-fff4-4bcc-82ea-3ededf90f880) And fill the form like that ### Describe alternatives you have considered Well, there are a few "solutions". First one is to maintain the "status quo" and just say that the Taiwanese Chinese language variant doesn't exist. The second one is what we currently use, which is to use a language filter and filter out Taiwanese, but I couldn't figure out how to do that, so right now we're filtering out regular Traditional Chinese instead. I get that the first option is seductive and maybe even more "rational", but I think it should be up to translators and project maintainers, not up to the Codeberg org, with all respect. ### Screenshots ![зображення](/attachments/b4d96155-ba85-49f6-a560-c56a9df729d8) Example of an alert, which then causes an error, if we want to modify the component in any way ### Additional context _No response_

I think that this may not be intentional. Thanks for letting us know.

I think that this may not be intentional. Thanks for letting us know.

I found a highly relevant discussion from weblate about this: https://github.com/orgs/WeblateOrg/discussions/15097 and it does suggest to create a zh-Hant-TW language. CC @Bubu do you have a opinion on this? Otherwise I think we could add this language in https://translate.codeberg.org/languages/

I found a highly relevant discussion from weblate about this: https://github.com/orgs/WeblateOrg/discussions/15097 and it does suggest to create a `zh-Hant-TW` language. CC @Bubu do you have a opinion on this? Otherwise I think we could add this language in https://translate.codeberg.org/languages/

highly relevant

Seems like it's so relevant, it could've been authored by the same person as OP! :D

> highly relevant Seems like it's so relevant, it could've been authored by the same person as OP! :D

Oh I didn't even notice.

Oh I didn't even notice.
Member
Copy link

@Gusted mh, not sure. nijel's answer in the weblate discussion implies that this is probably not what most projects want (i.e. they want this to be the same language) but I'm not sure if adding/changing this globally in the weblate instance has any detrimental influence? Probably not, so we could add this?

@Gusted mh, not sure. nijel's answer in the weblate discussion implies that this is probably not what most projects want (i.e. they want this to be the same language) but I'm not sure if adding/changing this globally in the weblate instance has any detrimental influence? Probably not, so we could add this?

@Bubu wrote in #2137 (comment):

Probably not, so we could add this?

Yeah, afaik if a project wants to do 'zh-Hant-TW == zh-Hant' they could just block the creation of a component for that language? It does seem zh_Hant has language aliases to Taiwanese:
image

Not sure what they do or imply.

@Bubu wrote in https://codeberg.org/Codeberg/Community/issues/2137#issuecomment-7216504: > Probably not, so we could add this? Yeah, afaik if a project wants to do 'zh-Hant-TW == zh-Hant' they could just block the creation of a component for that language? It does seem `zh_Hant` has language aliases to Taiwanese: ![image](/attachments/84b96cd4-d746-4176-89da-b8046f230c48) Not sure what they do or imply.
Member
Copy link

I've created https://translate.codeberg.org/languages/zh_Hant_TW/ now. That is hopefullu correct/enough?

I've created https://translate.codeberg.org/languages/zh_Hant_TW/ now. That is hopefullu correct/enough?

зображення
That seems to be working, thanks!

I'll open a new issue if there are any problems; this one is solved :)

![зображення](/attachments/8e642a41-c84c-41bd-8a94-50315cf156f8) That seems to be working, thanks! I'll open a new issue if there are any problems; this one is solved :)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2137
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?