Hi all, the gnome-devel-docs module is now shown in
developer.gnome.org live from git, not from release tarballs. This
means that if the XML validation is broken in any of the files or a
translation, a few hours after the commit, it will be broken on the
website.
I would appreciate it if anyone wo
Ekaterina,
Rather than rely on the carefulness of the translators (which will possibly
fail at some point and a few times), isn't it possible to implement some
kind of verification before pushing from the module to the website? My idea
would be something like: schedule the pushes to website and be
Hi,
Could we implement a pre-commit hook to check XML syntax with gtxml [1]?
This is the tool I use to periodically check XML syntax from PO files, to
detecttypos in tags or not properly closed tags in PO files, so running it
before pushing changes into Git could help us to avoid this kind of
pro
On Fri, May 9, 2014 at 5:14 PM, Daniel Mustieles García
wrote:
> Hi,
Hi,
> Could we implement a pre-commit hook to check XML syntax with gtxml [1]?
Are there any false positives?
--
Alexandre Franke
___
gnome-i18n mailing list
gnome-i18n@gnome.org
h
No AFAIK, but I'm not 100% about it.
Cc'ing Ask, maintainer of pyg3t, to hear his oppinion about this question.
El 09/05/2014 17:37, "Alexandre Franke"
escribió:
> On Fri, May 9, 2014 at 5:14 PM, Daniel Mustieles García
> wrote:
> > Hi,
>
> Hi,
>
> > Could we implement a pre-commit hook to chec
The only false positive I know of gtxml is the 'translator-credits' string,
returning exit code 1. For instance:
$ gtxml platform-demos.master.pt_BR.po
At line 23: not well-formed (invalid token)
---
#. Put one translator per line, in the form NAME , YEAR1,
Maybe it is because of the newline character? Translator credits should be
in one line per credit
El 09/05/2014 18:01, "Rafael Ferreira" escribió:
> The only false positive I know of gtxml is the 'translator-credits'
> string, returning exit code 1. For instance:
>
> $ gtxml platform-demos.master
No, it is a false positive. My example had only one translator. But here is
another example, now with two translators in translator-credits:
$ gtxml ~/Downloads//optimization-guide.master.pt_BR.po
At line 24: not well-formed (invalid token)
---
#. Put one tr
Pyg3t's maintainer is in Cc (Ask) so maybe he is the best option to fix it
;-)
El 09/05/2014 18:51, "Rafael Ferreira" escribió:
> No, it is a false positive. My example had only one translator. But here
> is another example, now with two translators in translator-credits:
>
> $ gtxml ~/Downloads/
Pk, 2014.05.09. 16:51 +, Rafael Ferreira rakstīja:
> If someone that knows python3 could patch pyg3t to fix this, I think
> it would be a great tool for this XML validation... Someone?
specifically in "translator-credits" strings, the e-mail is often put in
angle brackets, which is not a valid
Hello everyone
First of all I am very willing to implement a mode in gtxml
specifically for this.
Fixing the translator-credits issue is obviously very easy.
I can make it so that gtxml will only complain about syntax errors,
i.e. strings that are not accepted by the xml parser. This requires
t
11 matches
Mail list logo
