@msz59 Sir , for the Weblate Polish language goes by pol_PL and pl_CARES But We have Used the worldwide accepted code of Polish (pl) Thus this 404 is encountered, we would like to request you to please use the menu for Generalisation of language codes.
I know where it can be edited/translated. I have already done a few strings there. What I am trying to understand is how those translations enter the fortran-lang page “pl” version. When I choose other languages (e.g. Spanish, German or Czech), I get the main page with different percentages of translated content, the rest being still in English. But when I choose “pl”, I get 404.
Indeed, I have found it, thank you all. There are, however, no translations that I made, neither before fixing the problem nor those made after. I should wait for another PR, I guess.
We got another request for a new language from an external translator, this time for Esperanto, which is an artificial language. After we added Bengali the translator did not contribute any translations, so the question is whether we should require translators to be active either in the discourse or active at the repositories to make requests for new languages.
While I would like to support more languages, I don’t want to add a bunch of empty translations to the webpage which are not actively worked on and leave new users disappointed when checking out the localized versions in their language.
Although it could seem advantageous to see people external to our community expand or improve the translations of the Fortran-lang sites, my humble opinion is: yes we should require that translators actively participate in the Discourse and/or the repositories. I see two reasons:
these sites belong to the community and should be improved by the community,
a good translation needs a good understanding of Fortran. How to be sure that people external to our community have sufficient knowledge about the language?
It does not mean we exclude anybody. Our community is inclusive: everybody is free to join us at any moment (they will be warmly welcomed), and progressively take part in the works of the community.
I changed the settings for requesting new translations from Contact maintainers to Point to translation instructions URL. The contact feature in weblate unfortunately does not allow maintainers to respond to the request, but apparently it is easy for translators to just make those requests by selecting a language code.
Please post in this thread if you want a new language or checkout the PRs for other languages above to see how it can be done for the respective projects.
Just a third thought: another reason to require active participation in the community before translating, is that we need to trust translators. If nobody here speak (or read) their languages, we can not verify the content. We could imagine people or bots trying to diffuse some ideologies via our sites.
I’m willing to help on the translation of the website to Portuguese in brazilian dialect, which as I’ve seen, it looks like that is the standard. I’ve already submitted some suggestions at the weblate. Still, I have some questions: What are the procedures to have the translation proposals accepted and uploaded to the site?
You could automatically translate the text back to English using Google Translate, ChatGPT etc., to check that it is about Fortran and is not inappropriate.
Welcome @ntimesgurgel to the Fortran Discourse and thanks for getting involved in the translation work.
Weblate will make a Pull Request to the Fortran-lang repository once a day when there are new strings translated. Then you will have to wait for a Fortran-lang administrator to merge the PR. It can take a few days, a week, depending on their availability.
I also know that teams were created for translations, but for the moment there is only one member per language. This is the Pt team: Sign in to GitHub · GitHub
