Language menu for Ajapaik

Language menu for Ajapaik

Hello Sabelöga,

Thank you for you time translating for the Ajapaik project. I'm currently taking part in localization of Ajapaik's website. I noticed you've changed name of the Latvian language from endonym into Swedish. Would it be possible for you to use endonyms for the language menu as it is the developers stance?


Yulia

YuliaVo (talk)16:52, 17 June 2022

What do you mean? If the endonyms should always be used then the translation units are unused and superfluous. So why even make them translatable? Am I missing something here or is this really necessary?

Sabelöga (talk)01:05, 18 June 2022

Yes, you're right. The endonyms should be hard coded. But they are not now.

The Ajapaik project is a non-profit and things are not fast. Maybe they hard code them in nearest future. Maybe it's not a priority right now.

The thing is that developer has a vision of how it would be suitable for them. I like the idea behind this project and devote some of my time to its localization. I would like to help Ajapaik be fully localized and do what I can with the tools that I have.

I'm just translating developers' stance and it's up to the translator to follow this stance or to do things in a way they think it's better.

YuliaVo (talk)18:56, 26 August 2022
 

Also I disagree here, because Ajapaik has been translated in many language to translate language names, and this has been done in almost all target translation languages by not using the endonym/autonym (note that Ajapaik is not using the Medawiki parser for its messages, so it does not have the support of Mediawiki's #language; it may have. It may eventually have support for CLDR, but if its requires translaing these language names, it is because it does not feature any other i18n support library for these names, just for a few messages.

If you think that some messages should always use the autonym/endonym, and this is not documented like this, these should be translated and not left as endonyms/autonyms; but you can still send a support request (on the contact support link) to ask to its developers if that message is really needed to be translated. But endonyms should not be used if the language name is not used in isolation (e.g. as items in an unordered list of languages) but part of translated sentence containing some other words. Whever a translated message will be used or not in the target application is not something that we can decide here, it's up to the application developper to manage their list of useful messages to be translated.

Verdy p (talk)04:41, 18 June 2022