Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New political language #4205

Open
raoulkramer opened this issue Oct 21, 2020 · 4 comments
Open

New political language #4205

raoulkramer opened this issue Oct 21, 2020 · 4 comments

Comments

@raoulkramer
Copy link
Contributor

Hello I would like to have a separate language added to crowdin for political jargon/ terminology in English, Dutch and Georgian added to CONSUL. Thanks!

@javierm
Copy link
Member

javierm commented Oct 21, 2020

Hi, @raoulkramer 😄.

I'm not sure I understand the issue 🤔. Could you provide some examples showing when this feature would be useful?

Thanks!

@raoulkramer
Copy link
Contributor Author

Hi @javierm 👍 ,
We have been implementing Consul for political organisations for a while now. I think this year we will get to about 11 political organisations (time to get certified 😁 ).

The terminology used in political language is different, like proposal = motion , annotation = amendment ect. Normally we do this in the custom language files but that is risky and cumbersome. It would be great we could develop a language set for political use and that will lead to more Consul users.

example-political

Thanks 🥇

@javierm
Copy link
Member

javierm commented Oct 24, 2020

I see 🤔.

I'm afraid enabling new languages in crowdin for these cases would be really hard to maintain. We're not talking about different languages here but about different terminology.

Besides, so far CONSUL is mainly used by political entities, so political language should be the default language 😄. In the case of Dutch and Georgian, feel free to coordinate with other translators and update the translations through Crowdin so we use the terms that most entities/governments from the Netherlands or Georgia consider appropriate. English is a bit trickier, since it's used by entities from many different countries, so we can't change anything unless there's proper community support. In this case, using custom translations is still the way to go; suggetions to make using custom translations less cumbersome are welcome 😉.

@raoulkramer
Copy link
Contributor Author

Ah I understand,

We testing now, if structured translation will work, with our local weblate environment for this specific type of language terminology. When is useful and manageable, I will let you know so we can see if it is interesting to migrate to Crowdin on a later point. Thanks again 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants