Re: Keywords in desktop files



Wouldn't both tasks - XML syntax check and keyword check in desktop
files - make a fine GnomeGoal?


Am Donnerstag, den 17.01.2013, 14:04 +0100 schrieb Daniel Mustieles
García:
> Another check that should be implemented is the XML syntax check done
> in gtxml [1]. It checks the documentation PO files syntax, and is
> really useful to avoid errors in malfomed or wrong tags in doc files.
> 
> [1] https://launchpad.net/pyg3t
> 
> 
> 
> 2013/1/17 Matthias Clasen <matthias clasen gmail com>
>         On Thu, Jan 17, 2013 at 3:55 AM, Olav Vitters
>         <olav vitters nl> wrote:
>         > On Wed, Jan 16, 2013 at 02:31:41PM -0500, Matthias Clasen
>         wrote:
>         >> In trying to build 3.7.4 in Fedora, I've come across a few
>         modules
>         >> where translations got this wrong. Here is an example:
>         >
>         > I usually just commit fixes for that, but Mageia is sticking
>         with 3.6
>         > for now.
>         >
>         > Any way to check this on the server? I know various po
>         checks are done,
>         > if possible, we should include the check for correct
>         Keywords
>         > translations as well.
>         
>         
>         Two good points. I would normally do that too, but I am
>         struggling to
>         even identify the word boundaries in some of the languages
>         that
>         desktop-file-validate complains about. Adding
>         desktop-file-validate to
>         make check is certainly a good idea.
>         _______________________________________________
>         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

-- 
Christian Kirbach <christian kirbach gmail com>
Christian Kirbach <christian kirbach gmail com>
Christian Kirbach <christian kirbach gmail com>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]