Hello @
Mario Vavti I've been asked if it would be possible to add OWA to self-hostable translation platform Weblate; with the goal to be able to translate UI, templates and Webpage on our own platform and using our own tech. And I wanted to give it a try.
Now I have a development and 'production' Weblate instance equipped with OWA. I'm experimenting with the Hubzilla translations, but I'm not quite sure I'm going the correct way.
What did I do:
- configure to use the Hubzilla 'messages.po' and 'hmessages.po' via git repo
The outcome in the Weblate interface in my dev environment looks like this:
So that is something, but there are alerts because many words are duplicated in the .po files, example:
pascal@hzsandbox2:/srv/hubzilla/view/pt-br$ grep "General Features" hmessages.po
msgid "General Features"
msgid "General Features"
pascal@hzsandbox2:/srv/hubzilla/view/pt-br$ grep "Content Expiration" hmessages.po
msgid "Content Expiration"
msgid "Content Expiration"
pascal@hzsandbox2:/srv/hubzilla/view/pt-br$ grep "Private Notes" hmessages.po
msgid "Private Notes"
msgid "Private Notes"
This causes these alerts so there's possibly something not in line there.
- I also tried to configure Weblate to translate directly using the 'PHP strings' file format in Weblate, but that failed as no strings could be parsed from the strings.php / hstrings.php files.
What could you advise as the best way to interact with the Hubzilla translations from Weblate?
- continue with the .po files but try to find how to eliminate the duplicates?
- try to parse the (h)strings.php file? (In case we don't really need the .po files)
- other?
Hints are welcome.
fyi, I have a 'production' weblate instance running at
#^https://weblate.eenoog.org/ which allows OWA login, e.g. "https://weblate.eenoog.org/?zid=<your handle>" - in case you want to try the login for yourself (remember to login in in the same browser session to your Hubzilla site first...).
