[devhelp] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 5191b34... SearchBar: use GtkBox, not GtkGrid, when using GTK_STYLE_CL ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[gnome-software] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: f0bfd56... Update Finnish translation ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
Never mind ;-) My proposal is to include gtxml as part of the checks DL (or git, in a pre-commit hook) does, like it's currently done with msgfmt, to avoid this issues when committing help files (maybe a pre-commit hook is the best option, to also detect possible issues out of DL workflow). As a pre-commit hook it should be easy to implement (maybe Andrea Veri could help us with this). In DL I don't know how much difficult it is. About the issue with the <_:link> tag, I'm sure Ask will be able to know why it happened and fix it :-) El vie., 3 abr. 2020 a las 11:47, Andre Klapper () escribió: > On Fri, 2020-04-03 at 11:26 +0200, Daniel Mustieles García wrote: > > Yes, id hast not detected that one (and I'm Cc'ed Ask, gtxml's > > developer to review it) but id detects many others. Are we dropping a > > good tool because of an isolated bug? ;-) > > Ah, sorry, I thought you had meant that gtxml (which I also love to use > locally) could have caught this issue. Looks like I misunderstood you! > > andre > > > El vie., 3 abr. 2020 a las 11:08, Andre Klapper () > > escribió: > > > [No need to CC me as I am a mailing list member] > > > > > > On Fri, 2020-04-03 at 10:19 +0200, Daniel Mustieles García wrote: > > > > I don't know about Gitlab, buy PyG3t tools (gtxml especifically) > > > > checks XML syntax to detect this cases. > > > > > > No, as you wrote yourself that it does NOT detect these cases in > > > https://gitlab.gnome.org/GNOME/zenity/-/issues/17#note_758794 : "It > > > was > > > a wrong <_:link> tag in license string, but gtxml didn't detect > > > it." :) > > > > > > andre > > > -- > > > Andre Klapper | ak...@gmx.net > > > https://blogs.gnome.org/aklapper/ > > > > > > > > > ___ > > > gnome-i18n mailing list > > > gnome-i18n@gnome.org > > > https://mail.gnome.org/mailman/listinfo/gnome-i18n > > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > https://mail.gnome.org/mailman/listinfo/gnome-i18n > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
On Fri, 2020-04-03 at 11:26 +0200, Daniel Mustieles García wrote: > Yes, id hast not detected that one (and I'm Cc'ed Ask, gtxml's > developer to review it) but id detects many others. Are we dropping a > good tool because of an isolated bug? ;-) Ah, sorry, I thought you had meant that gtxml (which I also love to use locally) could have caught this issue. Looks like I misunderstood you! andre > El vie., 3 abr. 2020 a las 11:08, Andre Klapper () > escribió: > > [No need to CC me as I am a mailing list member] > > > > On Fri, 2020-04-03 at 10:19 +0200, Daniel Mustieles García wrote: > > > I don't know about Gitlab, buy PyG3t tools (gtxml especifically) > > > checks XML syntax to detect this cases. > > > > No, as you wrote yourself that it does NOT detect these cases in > > https://gitlab.gnome.org/GNOME/zenity/-/issues/17#note_758794 : "It > > was > > a wrong <_:link> tag in license string, but gtxml didn't detect > > it." :) > > > > andre > > -- > > Andre Klapper | ak...@gmx.net > > https://blogs.gnome.org/aklapper/ > > > > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > https://mail.gnome.org/mailman/listinfo/gnome-i18n > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
Le 03.04.20 à 11:08, Andre Klapper a écrit : > [No need to CC me as I am a mailing list member] > > On Fri, 2020-04-03 at 10:19 +0200, Daniel Mustieles García wrote: >> I don't know about Gitlab, buy PyG3t tools (gtxml especifically) >> checks XML syntax to detect this cases. > > No, as you wrote yourself that it does NOT detect these cases in > https://gitlab.gnome.org/GNOME/zenity/-/issues/17#note_758794 : "It was > a wrong <_:link> tag in license string, but gtxml didn't detect it." :) There is from some time the ability to build documentations on D-L. It is not enforced before committing, but would have it catched that issue? Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
Yes, id hast not detected that one (and I'm Cc'ed Ask, gtxml's developer to review it) but id detects many others. Are we dropping a good tool because of an isolated bug? ;-) El vie., 3 abr. 2020 a las 11:08, Andre Klapper () escribió: > [No need to CC me as I am a mailing list member] > > On Fri, 2020-04-03 at 10:19 +0200, Daniel Mustieles García wrote: > > I don't know about Gitlab, buy PyG3t tools (gtxml especifically) > > checks XML syntax to detect this cases. > > No, as you wrote yourself that it does NOT detect these cases in > https://gitlab.gnome.org/GNOME/zenity/-/issues/17#note_758794 : "It was > a wrong <_:link> tag in license string, but gtxml didn't detect it." :) > > andre > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
[No need to CC me as I am a mailing list member] On Fri, 2020-04-03 at 10:19 +0200, Daniel Mustieles García wrote: > I don't know about Gitlab, buy PyG3t tools (gtxml especifically) > checks XML syntax to detect this cases. No, as you wrote yourself that it does NOT detect these cases in https://gitlab.gnome.org/GNOME/zenity/-/issues/17#note_758794 : "It was a wrong <_:link> tag in license string, but gtxml didn't detect it." :) andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken markup in [es, hu, sv] zenity user doc translations
Hi Andre, Spanish should be fixed, many thanks for reporting it. I don't know about Gitlab, buy PyG3t tools (gtxml especifically) checks XML syntax to detect this cases. I've put this on the table several times, asking to integrate it in DL like msgfmt is. This would help us avoid this situations, maybe now we can talk about it again ;-) Regards El vie., 3 abr. 2020 a las 9:51, Andre Klapper () escribió: > There is a contributed patch by Christian in > https://gitlab.gnome.org/GNOME/zenity/-/merge_requests/4/ > which fixes broken markup in the es, hu, sv user help translations. > > I'd like to merge this patch (and hence bypass our l10n.gnome.org > process) as the situation breaks compiling. > https://l10n.gnome.org/module/zenity/ shows none of these languages > have any translations in progress, so I think this is acceptable. > > I also already boldly fixed > https://gitlab.gnome.org/Teams/Translation/el/issues/6 > as I have received no feedback for months from Greek translators and > https://l10n.gnome.org/vertimus/zenity/master/help/el/ is inactive. > > I'm generally wondering how much teams follow 'their' issue tracker. > > And Christian's question: > Does anyone know if/how this could have been caught by GitLab CI? > > Cheers, > andre > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Broken markup in [es, hu, sv] zenity user doc translations
There is a contributed patch by Christian in https://gitlab.gnome.org/GNOME/zenity/-/merge_requests/4/ which fixes broken markup in the es, hu, sv user help translations. I'd like to merge this patch (and hence bypass our l10n.gnome.org process) as the situation breaks compiling. https://l10n.gnome.org/module/zenity/ shows none of these languages have any translations in progress, so I think this is acceptable. I also already boldly fixed https://gitlab.gnome.org/Teams/Translation/el/issues/6 as I have received no feedback for months from Greek translators and https://l10n.gnome.org/vertimus/zenity/master/help/el/ is inactive. I'm generally wondering how much teams follow 'their' issue tracker. And Christian's question: Does anyone know if/how this could have been caught by GitLab CI? Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
