Closed milotype closed 1 year ago
Hi @milotype - I took some time today to start making other pieces of the website translatable. I also addressed some unintended language switches on the site notice and privacy policy pages.
Unfortunately weblate is not an option currently, due to technical restrictions. I will give it a try in the future, but time is limited...
@RaphaelLaurent giving you a ping, just in case you want to help translating the features to French 😄
General translations can always be changed at:
I started with the "features" section of the homepage, which was rather easy to do. You can add your translations here:
The original content can be found here: https://github.com/kimai/www.kimai.org/tree/master/_includes/features
Two things you can do:
{% include features/active-entries.md %}
with the actual translated contentStarting with an easy task regarding the documentation, I added language keys for the sections and their description. The section names are also used in the documentation menu (but currently only on the index page). Translating the documentation is a huge topic and will probably only happen for the structure (menu and recurring labels), especially to prevent accidental language switches.
The biggest changes are definitely the store pages, which can now be fully translated.
All store pages exist now in all languages and can be adapted one by one:
If you want, you can translate the names and descriptions. The page content is to much to translate for the first step. I started with the titles of some of my own plugins in german.
There are some untranslated strings in the store detail pages, which I will work on the next days.
Hi Kevin,
Thanks for the message, I will start translating the features in the next few days (I just created a fork).
Hey you two 😄
I had an inspiration today and found a way to add the main translations to weblate: https://hosted.weblate.org/projects/kimai/website/
I will have to do more refactorings to allow translating other components/store pages/menu ... but the first step is always the most complicated one and that was likely a success today.
There are some new translations in the main files, so you could give it a try at any time. I am really curious if it works as well as with Kimai itself.
@kevinpapst GREAT! I've just translated the Croatian part at https://hosted.weblate.org/projects/kimai/website/hr/. Good luck and I hope everything works fine.
@milotype here is the first weblate PR: https://github.com/kimai/www.kimai.org/pull/155/files
Thanks to your continuous feedback, I refactored the website again and moved more translations to the Weblate component: you can now edit the entire features list there and all menu names and titles.
Plus the "Demo will be reinstalled" string, which is currently untranslated
Croatian: https://hosted.weblate.org/translate/kimai/website/hr/?q=has:check French: https://hosted.weblate.org/translate/kimai/website/fr/?q=has:check
I already received translations for other languages, but I cannot add them yet, because of all the other (page, store) files which are missing. I have to find a way to move those to Weblate as well, so we can edit at least all titles in there. Thanks to you I see a big SEO potential lying around here... will push that topic further as soon as I find more time.
For now I will ignore all the other strings which are on pages, that only exist in english (documentation, news, v1 pages), but concentrate on the main pages.
@kevinpapst OK, Croatian is translated. Please also check my comment at: https://hosted.weblate.org/translate/kimai/invoice-templates/hr/?q=has:comment#comments
Done @milotype ... I have still a lot to learn about weblate 😳
French is also translated
Today I merged a lot of changes. Just in case you have received too many Weblate emails today, you soon know why 😁
While I was working on integrating Chinese translations, I found several places which were still untranslatable.
The files in this repo are more and more only empty placeholders to trigger the Jekyll build for this language, but are not meant for the actual translations any more. Also: applying changes to four (or more) languages started to be annoying, so I worked on more translatable elements. And as of today a lot of new elements are translatable through Weblate, e.g. shop title/intro/featured text
What is missing from the initial post are the translatable news categories. But news are english only, so I would ignore that point for now and simply close here!?!
Problem Where/how to translate currently untranslated contents for localized web pages?
<div class="card">
in the localized page DemoAnnouncement
,Apps & Plugins
etc.plugin
,development
, etc.Solution If possible, add a component or components to the project Kimai - Time tracking for the website contents.