On Thu, Apr 16, 2020 at 10:41 AM Julien Nabet <firstname.lastname@example.org>
Building with all langs and helpcontent, I noticed this:
Entity: line 1: parser error : Opening and ending tag mismatch: root
line 0 and literal
iÅ¡ite parametre funkcije <literal>a</literal>,
Indeed sl/helpcontent2/source/text/scalc/guide.po contains:
However, I fixed this 11 days ago, see
Slovenian still is in my list of languages not using TDF's translation
tooling/was one of the languages that was updated independently via
Andras, so changes in weblate are not added automatically when I
update translations in the core repo.
Any idea what's wrong?
Well, nothing necessarily wrong - what counts for the build process is
what is committed to the translations repository.
For weblate I'm using an intermediate repository on github where
weblate automatically pushes to. But I don't want to have 14 weekly
commits to the translations repo, since that will also trigger commits
to core for moving the submodule tag and lots of small changes will
just have a higher noise ratio in the changes (change of last change
date to actual changes).
tldr: Slovenian translations have not been managed via pootle back in
the day and are pushed to the translations repo by Andras (last push
to 6-4 was in February, however last push to master is from last
November). There has been a langauge setup in pootle for it though, so
that's the reason why it also ended up in weblate, but still I/my
scripts still ignore it.
So question is for Slovenian translators (which I assume is just
Martin?) whether they want to use weblate instead (honestly don't know
the reason why pootle wasn't used - I mean you could still translate
offline and push the po files to pootle (and now weblate) to have them
part of the same update process)
If I should switch to using weblate as source, let me know.
Finally, any idea to know where is the pb when we got this:
[build HPX] ta/helpcontent2/source/text/smath/guide
Entity: line 1: parser error : Opening and ending tag mismatch: ahelp
line 0 and root
Indeed, with these characters, impossible to git grep or search in
You'll have an easier time with those using the tinderbox/jenkins logs
where the output is properly encoded:
PS: feel free to use the email@example.com mailinglist for
problems like this - that is bugs in translations affecting multiple