Want to bump this message now that we are testing 2.22-RC release; it would be good to have translations for the welcome page messages prior to release.
On the translation side, I hesitate between two options:
Reopen the translation on Transifex after updating it
Pros : all is in place, all translators have an account and know how to use Transifex
Cons : during the last sync, I got a lot of stuff introduced by the automatic mechanisms of Transifex which I had to remove manually, so I fear the work to do to sync from Transifex to GitHub- Use the OSGeo weblate instance for this translation
Pros : no more relying on Transifex, use a OSGeo managed tool, no automatic mechanisms you can’t disable
Cons : have to remove the duplicate languages (chinese in two encoding styles), all translators must request an account to OSGeo, new tool to discover, configuration to complete (I have done the configuration with my fork for all the core modules but not for the extensions)
Are you fine with (sparse) usage of … tags? In English you can emphasize a word using capitalization. Since in German nouns always start with a capital letter, stronger emphasizing techniques are required sometimes.
Not using any tool. An editor and Git is sufficient for me Shall translation PRs (as all others) primarily target the main branch?
Cheers
Carsten
···
Am 08.11.2022 um 07:46 schrieb Jody Garnett:
Want to bump this message now that we are testing 2.22-RC release; it would be good to have translations for the welcome page messages prior to release.
I’ve translated the new welcome page messages (e. g. GeoServerHomePage.description[…]) into German. Like these as a separate commit/PR? Or…
I could also translate some more of the commented out messages in the German locale files.
Furthermore, I think about editing some of the existing German messages… However, I don’t want to tread on some other dev’s/translator’s toes by blaming his/her work… Any best practices known concerning such a situation?
Cheers
Carsten
···
Am 08.11.2022 um 07:46 schrieb Jody Garnett:
Want to bump this message now that we are testing 2.22-RC release; it would be good to have translations for the welcome page messages prior to release.
We have our video meeting in 20 mins perhaps discuss there? I think weblate would be a good way to go; but I am really not invested in the outcome (only wish to assist folks in translating our software).
For the short term we have a release coming out with some strings that really need translating - where can we change this?
GeoServerHomePage.belongsTo = For more information visit ${organization}.
GeoServerHomePage.footer = This GeoServer instance is running version ${version}.
GeoServerHomePage.footerContact = Contact administrator.
GeoServerHomePage.serviceCapabilities = Service Capabilities
GeoServerHomePage.title = Welcome
GeoServerHomePage.descriptionGlobal = GeoServer Web Service, ${user} access to ${workspaceCount} workspaces, with ${layerCount} layers.
GeoServerHomePage.descriptionGlobalOff = GeoServer, ${user} access. Select a workspace or layer, above, to change to a virtual web service.
GeoServerHomePage.descriptionWorkspace = GeoServer Virtual Web Service, ${user} access to ${workspaceName} workspace, with ${layerCount} layers.
GeoServerHomePage.descriptionLayer = GeoServer Virtual Web Service, ${user} access to ${layerName} layer.
GeoServerHomePage.descriptionLayerGroup = GeoServer Virtual Web Service, ${user} access to ${layerName} layer group.
I am waiting to hear back from Alexandre; although if you have any experience with weblate or transifx we welcome your input.
Anything you can do to make the translations consistent and clear is appreciated. As the application changes over time you maybe able to spot places that can be improved that were not obvious to the original author. My guidance would be to look at the resulting user interface page and focus on making that clear; if you need to update some prior translations it is to be expected.
You are also welcome to start an email thread on a specific translation challenge (making layer group consistent for example; or shortening label to fit UI). Even if folks do not respond today; they can find the topic later.
I will split this into two parts. First part is translating missing/not yet translated messages, including those for the welcome page you need for the 2.22.0 release. When is that release planned (aka, when do you need the messages ultimately?). Likely I’m not getting done with part #1 completely when you release 2.22.0 so, part #1 may be split into several PRs.
Only after part #1 is done, I will start with revising already translated messages, which is part #2. Part #2 is about consistency, style and common IT wording. At least for my mind, some of the texts actually use quite uncommon IT wording… However, I will make a draft/proposal PR for part #2 and then, explicitly ask other German translators, what they think about it.
Cheers
Carsten
···
Am 08.11.2022 um 17:12 schrieb Jody Garnett:
Thanks Klein:
I am waiting to hear back from Alexandre; although if you have any experience with weblate or transifx we welcome your input.
Anything you can do to make the translations consistent and clear is appreciated. As the application changes over time you maybe able to spot places that can be improved that were not obvious to the original author. My guidance would be to look at the resulting user interface page and focus on making that clear; if you need to update some prior translations it is to be expected.
You are also welcome to start an email thread on a specific translation challenge (making layer group consistent for example; or shortening label to fit UI). Even if folks do not respond today; they can find the topic later.
I’ve translated the new welcome page messages (e. g. GeoServerHomePage.description[…]) into German. Like these as a separate commit/PR? Or…
I could also translate some more of the commented out messages in the German locale files.
Furthermore, I think about editing some of the existing German messages… However, I don’t want to tread on some other dev’s/translator’s toes by blaming his/her work… Any best practices known concerning such a situation?
Cheers
Carsten
Am 08.11.2022 um 07:46 schrieb Jody Garnett:
Want to bump this message now that we are testing 2.22-RC release; it would be good to have translations for the welcome page messages prior to release.
I have tested again Transifex to check if the problems I observed last time have been solved: apparently it is the case. As a consequence I have updated the source on Transifex and push back a first batch of translations, including the ones for French for the new welcome page.
If the PR succeeds, I will post a message on the Transifex group and on the user mailing list to ask for translation updates.
For the moment I didn’t add the resources for the new extensions of this release : I will try to add them this weekend.
I still would like to move to weblate, at least to longer rely on a local computer to do the sync, but I have to find enough time to work on it.
Shall translation PRs (as all others) primarily target the main branch?