Re: More on xml errors in documentation
This question has is being discused here:
https://bugs.launchpad.net/pyg3t/+bug/1052399
The main question we have is if all the tags are mandatory or not. If it's
mandatory to have the same tags in the msgstr and the msgid, we should do a
strict check to avoid missing tags in translations; if they aren't
mandatory, there is no need to do this kind of check, but then there are
other problems: unreviewd tags may become deprecated, so documentaion might
not been shown properly, these tags might neve be included in translated
strings, just bothering translators...
Both Ask and me have no much idea about Mallard, so any comment or
explanation about how it works will be welcome.
Thanks in advance!
2013/4/4 Ask Hjorth Larsen
> Hello
>
> Below are some error reports for GNOME docs which are considerably
> more strict than usual.
>
> I would like to know how useful this kind of report is. It complains,
> aside from the usual syntax errors, about tags it cannot find in the
> corresponding msgid. This will lead to false positives in cases where
> the translator chooses to add, say, ... to a programme name
> when the msgid didn't. I will appreciate any feedback ("this is
> ridiculous, everything was totally okay" or otherwise).
>
> Here are the reports. Only some languages with many doc translations
> have been included.
>
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
>
> Best regards
> Ask
> ___
> 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: More on xml errors in documentation
HI,
thanks, personally I find those very useful, as mistakes may happen very
easily in translations. Thanks for your work.
I just started fixing the de locale.
Actually I thought about implementing XML syntax check in gtranslator, a
PO file editor.
Am Donnerstag, den 04.04.2013, 16:31 +0200 schrieb Ask Hjorth Larsen:
> Hello
>
> Below are some error reports for GNOME docs which are considerably
> more strict than usual.
>
> I would like to know how useful this kind of report is. It complains,
> aside from the usual syntax errors, about tags it cannot find in the
> corresponding msgid. This will lead to false positives in cases where
> the translator chooses to add, say, ... to a programme name
> when the msgid didn't. I will appreciate any feedback ("this is
> ridiculous, everything was totally okay" or otherwise).
>
> Here are the reports. Only some languages with many doc translations
> have been included.
>
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
>
> Best regards
> Ask
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
--
Christian Kirbach
signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on xml errors in documentation
Hi Christian,
If you are planning to implement gtxml in Gtranslator, you might find
useful this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=672080
Ignacio was working on it, and there is a patch attatched, but it isn't
finished. Havind this kind of checks in GTR would be wonderful!
Thanks for taking care of this
2013/4/5 Christian Kirbach
> HI,
>
> thanks, personally I find those very useful, as mistakes may happen very
> easily in translations. Thanks for your work.
>
> I just started fixing the de locale.
>
> Actually I thought about implementing XML syntax check in gtranslator, a
> PO file editor.
>
>
> Am Donnerstag, den 04.04.2013, 16:31 +0200 schrieb Ask Hjorth Larsen:
> > Hello
> >
> > Below are some error reports for GNOME docs which are considerably
> > more strict than usual.
> >
> > I would like to know how useful this kind of report is. It complains,
> > aside from the usual syntax errors, about tags it cannot find in the
> > corresponding msgid. This will lead to false positives in cases where
> > the translator chooses to add, say, ... to a programme name
> > when the msgid didn't. I will appreciate any feedback ("this is
> > ridiculous, everything was totally okay" or otherwise).
> >
> > Here are the reports. Only some languages with many doc translations
> > have been included.
> >
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.de.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.el.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.es.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.fr.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.gl.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.hu.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.pt_BR.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.ru.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.sl.txt
> > http://www.student.dtu.dk/~ashj/opendir/gtxml.strict.zh_CN.txt
> >
> > Best regards
> > Ask
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
> --
> Christian Kirbach
>
> ___
> 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: Merging wip/clutter-1.99 in master
hi all; a bit later than I expected, but I merged the wip/clutter-1.99 branch into master — master is now open for the 1.99 development cycle, which will lead to Clutter 2.0. I also pushed the clutter-1.16 branch, which I expect is what will be used for GNOME 3.10. have fun! On 30 March 2013 12:51, Emmanuele Bassi wrote: > hi all; > > executive summary: last night I finally rebased the preliminary 1.99 > branch on top of current master, and I'm planning to switch master to > it on Monday, barring unforeseen complications. > > the wip/clutter-1.99 branch contains the initial work needed to move > towards Clutter 2.0; it removes all deprecated symbols (for a net > worth of 40 thousand lines of code removed from the repository), and > handles the fallout in the various pieces of the code base. as to > avoid breaking bisection, the commits should build separately — at > least, if you disable the test suite at configure time, since it's > mostly a mechanical job. > > after the merge, master will be open to large refactorings which will > hopefully lead to 2.0. at the same time, I'll open another branch, > called clutter-1.16, for a transitional release cycle in case more > stuff has to be removed from master (and thus has to be deprecated on > the 1.x API line). this is, in essence, the same plan I had for 1.14, > only delayed by a cycle. > > if you are using Clutter right now, I suggest you stick to the stable > clutter-1.14 branch, and eventually switch to clutter-1.16 if you want > to port to 2.0. > > the plans for Clutter 2.0 are on the roadmap[0], but I expect that to > be edited/changed a bit after the GTK+ hackfest at the end of > April[1], considering that we want to move Clutter closer to GTK in > the future. > > ciao, > Emmanuele. > > [0] https://live.gnome.org/Clutter/Roadmap > [1] https://live.gnome.org/Hackfests/GTK2013 > > -- > W: http://www.emmanuelebassi.name > B: http://blogs.gnome.org/ebassi/ -- W: http://www.emmanuelebassi.name B: http://blogs.gnome.org/ebassi/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'yelp.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'yelp.master': + "Don't steal focus" Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/yelp/log/?h=master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
