From "air" to "ina"
@!
Hubzilla Support Forum Mario,Max, thanks for setting up the framagit branch "air". So far I haven't installed version 5.4.1 for mysef up to now (but will happen in the next few days). Then I will incorporate the wanted changes and send the MR. However, in the 2 past weeks I was not lazy and have now almost finished of something that I had programmed more than 10 years ago. That I would also like to see in Hubzilla.
"Ina"
This part has the nickname "Ina" and I want to introduce it thematically also as a thank you for Hubzilla 5.4.1 with a screen:
Mario recently pointed out still missing translations in Hubzilla. Also my code part "air" is not translated yet. My idea is to wait a short time until "Ina" will be generally available this month.
I am not an opponent of the current workflows via Transifex, but also not a friend. These workflows, certainly proven, I find a little bulky. Therefore "Ina":
All text phrases used in Hubzilla for translations are stored in a DB with cross references. This already offers the possibility to increase in quality by cleaning up the English source texts, which up to now have been partially provided with syntactic text fragments (such as Html tags). Such things are quickly coded:
...t('please regard <strong>this</strong> and ...') ...which works, but does not please every translator. Better would certainly be
...t('please regard') . '<strong>' . t('this') . '</strong>' ...or to keep the context together, to work with %s placeholders. What way this is improved, examples like this I mean with quality improvement of the English source texts. How something like this can be done in a simple way shall show another screen:
Both on module and on text level there are filter/search functions in "Ina", which show very fast, in which paths with which scripts in which lines an improvement is conceivable. And if the realization is there that some places can be improved, it makes sense to do this before the translations to avoid a double translation work.
But there is a lot more that should be considered: Both in the support forum and on other channels, there are occasional discussions around the terms used in Hubzilla. This concerns both English source words and then also their translations. Hubzilla with its more than 3500 php scripts is a very powerful and therefore also very complex tool, so it can make it much easier for beginners in this environment, if the terms are clearly and unambiguously named. Conversely, it can also cause extreme incomprehensibility, which the project does not deserve. Some things are simply characterized by carelessness. In many places in Hubzilla the term "site" is used. In English, the term is unspectacular. The used German translation with "Seite" is not completely wrong, but unfortunately rather misinterpretable. "Site" or "Server" or "Instanz" would be a better translation (whereas "server" is not a translation at all :-)). The Transifex Dictionary function was recently suggested in the Zap Forum. But Transifex is not the only one that can do this. Conceivable would be also a Hubzilla Wiki for these purposes. By the way, in "Ina" I enter the terms "site" and "page" in the search field and in the next 2 seconds I see where these terms are used everywhere (with currently 30000 sentences in 13 languages). So if it were clear to me which term is best, the improvement can be implemented fairly quickly.
Besides that, there are other aspects worth discussing because of translations. So there will be more posts to this in the coming time. Technical implementations of clear organizational boundary conditions are often easier to master than paving the way to the goals. "Ina" should help with this on the technical side and ideally some participants here in the support forum will go along on this journey.
