Great thanks!
I currently try to find somebody else who interesting in translation or at least just to review ready translation as I agree it should improve translation and will allow to agree on more stable terminology.
I created Github pull request “Add/Update initial Russian translation” for fortran-lang/webpage with added parts of translation and attached PDF files to preview the built version of translated pages.
Just got a request via Weblate for translating to Bengali (language code bn). I opened issues at the respective projects in case anyone wants to try adding those language files:
Also, I think the request is from outside our Fortran community, which is great, it shows that translators are interested in contributing to our effort even if they don’t use Fortran. Still, it raises the question, how we should handle such a case. Preferably we have a Bengali speaker from our community who can help reviewing and correcting translations especially for technical and Fortran related terminology.
What do you think?
And there has been a request for a Polish translation, thanks @msz59 for the suggestion. Again I opened issues for tracking the addition of the initial language files, contributions are welcome.
Thanks @henilp105 and @awvwgk for having ported the infrastructure to Sphinx and enabled the translations via Weblate, and managing the PRs! This is a great achievement. I think welcoming the newcomer in its mother tongue is very positive as it alleviates the learning effort.
Since the beginning of September, I am working on the French translation of the main pages of Le langage de programmation Fortran — Fortran Programming Language
I have recovered all the translations I made during Spring 2021 and imported them in Weblate. The homepage, the Learn, Compilers, and Community main pages are available in French. I am now in the translation of the sub-pages of Packages.
The French translation score is… 4%! I don’t think I will translate the News pages, as they contain a big part of commit messages. It’s not very useful to translate them. But translating some tutorials may be interesting. People wanting to help on the French translation are of course welcome! It can be translating items or verifying/improving existing translations, verifying that the hyperlinks in the pages are OK, etc.
That’s true, we should check whether there is a way to exclude those strings from the translation, they basically only take up place without offering any real advantage when translated. It looks like ablog has a language tag, not sure whether this will exclude strings.
A quick hack might be adding a tag when extracting the strings to ignore the news section when updating the translations. Opened a discussion for this in Should strings from news section be translated? · Issue #173 · fortran-lang/webpage · GitHub.
I am not sure we should exclude them technically. Except if there is a true advantage for the administration of the site.
Hum… but it’s true it would improve my score! 
Excluding them might give the advantage to include truly localized news, like events which are in the local language and probably not interesting for the whole community. In this case it might be useful to still have the English news available as well.
There are currently ~2.5k strings only in the news section, which are mainly commit messages. From an administrative point of view this is taking up 1/4 of our available source strings on Weblate.
Yes, in any case, we must keep the English news available even if they are not translated.
Oh yes, if we have a limited space on Weblate, it’s a good argument to exclude those strings, or to keep in mind that we could do it if necessary.
@everyone We have considered to show the languages in the actual language on the fortran-lang.org site, thus we would like to ask the respective language translators to verify is the translation is correct below, as it would have to be added manually into the site, without weblate. Please feel free to suggest the correct translation as this have been generated by google translate.
Below is the list of all the languages in which we have fortran-lang.org available and their respective translations in parent languages:
I have seen 中文 for simplified Chinese (zh-cn) elsewhere. Maybe @zoziha can help us here ;).
According to Wikipedia it is 日本語, @tomohirodegawa should be able to help us get this right.
Sorry for my missing knowledge on non-latin scripts.
Thanks, zh-CN stands for Simplified Chinese (简体中文) used in mainland China.
I have started editing the Polish translation but there are issues that I cannot solve by myself.
There is no real search in Weblate. You might be able to navigate the pages by using the uploaded screenshots.
Thanks for reporting, we will fix this with the next PR
@msz59 Sir , it seems may be you have missed the Polish banner, on Fortran programming language/Fortran webpage @ Hosted Weblate there is a section with name Polish MIT written that is intended for polish translations.
you may also directly go to Fortran programming language/Fortran webpage — Polish @ Hosted Weblate to contribute the polish translations.
Regarding to submit the page , In Weblate we can only submit Translations to respective strings by using Save and Continue button , we cannot translate entire page at once due to weblate.
For translating specifically or for easier searching you may also use VS Code and edit the index.po file of polish translation in locale folder and Open an PR to the Repo.
Thanks and Regards,
Henil
When I am working on the French translation of a project in Weblate, I am searching for a string which is characteristic of the page I want to work on. For example “High-performance parallel programming language” for the homepage of Fortran-lang.org. Then I click on the “Nearby Strings” tab below to see the strings that are around.
With the “Automatic Suggestions” tab, I can copy then improve an automatic translation. And by clicking on the right arrow “>” I then move to the next string to translate.
That’s exactly how I would like to go. My problem is how to search for such a string. Scrolling one string (not a page) at a time seems to be rather ineffective way of doing it when we have 5000+ strings.
Then you click on “Nearby strings”, and you see 15 strings before and 15 strings after what you searched for:
Now I got it, thank you. I did not notice that on the Languages page, the URLs linked to the language name and to small pen next to it (Translate) are different. Indeed, when I followed the “Polish” link, I got the screen as shown by @vmagnin, with Search button present.
It is still 404 
