jamulussoftware
Translations update from Hosted Weblate
Translations update from Hosted Weblate for Jamulus/Startpage.
It also includes the following components:
Current translation status:
Somehow the iOS changes didn't show up on Weblate. I needed to reload the po files. Hopefully nothing is lost.
No, they're there. It was because of entering the lang code as sv_SE instead of sv-SE. The build is going to keep failing until all the languages that have had their underscores changed to dashes are corrected - now it's because of pt_PT.
Edit: fixed all the offending lang codes. There are still tons that translators have left as en. A "search & replace" within individual languages instead of project-wide would come in handy...
Edit2: Ah, there is!
Translate text after
#in link. Don't translatebranch1-url=\"Running-a-Server\"
Is there any way these rules can be automated (i.e. based on the generated target links)? It feels a bit awkward that the id used isn't an absolute value in the source, even if it's translated in the output. I think both the generated page and id names pretty much have to be guessed at anyway, which is cumbersome. (Not something for solving here, of course...)
@pljones I think we could introduce something in the CI. I don't know if weblate is that feature rich.
@ignotus666 I'll look through the content and then - if you think it's good enough for a beta state, we should merge this. I believe we'll see look for and see broken links again after the merge. Is that ok?
Please re-review your translations for obvious mistakes. I've very high level scanned over some translations, but will continue tomorrow.
I'm away until Monday so can't give it another review, but beyond the stuff already highlighted I think it's ok.
Do we have enough context just to go in and fix on Weblate the outstanding issues above?
Not on every comment. Especially the # issues must happen locally on a personal pc anyway
Not on every comment. Especially the
#issues must happen locally on a personal pc anyway
Can the _site tarball just be run and switched to the language with the problem and the target id identified that way?
Yes. I'd just use the linkchecker we link to find issues
http://jamuluswebsite.drealm.info/wiki/Software-Manual has this build.
I never managed to get the po4a tools running...
I think we should merge this. It's a pain fixing all this on weblate. -> open manual PR for the changes by @pljones
http://jamuluswebsite.drealm.info/wiki/Software-Manual updated with the merge.
@genesisproject2020 could you please check for the wrong link targets in your translation of the website as shown above?