Re: PO files headers and DL

[Kenneth Nielsen <k nielsen81 gmail com>]

Den 10-12-2011 20:37, Daniel Mustieles García skrev:
> Hi all,
>
> I've been developing a small bash script to help me with some git tasks,
> such as updating all my downloaded git clones, deleting all branches
> and, the most important, commiting automatically PO files from the GUI
> (not documentation).
>
> Well, at this momment, I'm working with the PO filenames to know where I
> have to copy the PO file (i.e., anjuta.master.es.po must be copied in
> anjuta/po/es.po). This is relatively easy, since GUI files are always
> (unless a ver few exceptions) in the module/po folder, but this rule
> can't be applied with documentation PO files (in the case of Anjuta, PO
> file is located in anjuta/manuals/anjuta-manual).
>
> I've been talking with with Claude about the possibility to add a header
> (maybe «X-Location»?) to PO files (both GUI and doc ones) containing the
> folder in which the PO file is located, so I can easily parse it with my
> script, simplifying it and ensuring I'm copying the PO file in the
> properly location. This header could be added automatically by DL to PO
> files, and as a PO file header, should not affect translations nor
> translators.
>
> We wolud like to ask teams coordinators If you agree adding this header
> to PO files. Note that this header can be used out of the script, for
> example, if you don't remember where libgda or anjuta's documentations
> are located.
>
> Of course, If anybody wants to take a look into (or use) the script,
> just tell me and I'll send you a copy of it. I'm using it and works
> properly (I still have not broken git with it ;-) )
>
> Many thanks to all
>
>
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n

Provided this can be done with _a small amount_ of work on the damned 
lies-end I think this is a good idea.

About some of the concerns that have been voiced here. I think that it 
is of course a better solution to make the location uniform, but it is 
also utopia to think that we can make such a change.

With regards to translator programs stripping headers, I inclined to say 
that they are broken if do so and bug reports should be made. In any 
case, if the information is there it will help the commiter, if it is 
not he will have to do it manually. That situation is still better than 
the way it is now.

I welcome the change if it can be implemented without a huge effort. 
Then I can also make my commit script better (seems like every language 
coordinator has his own, talk about wasted work).

On another subject remember that it is also the plan to at some point 
make it possible to commit translations directly from damned lies, in 
which case this problem will become a lot smaller, so that probably 
makes it even less likely that we should solve it by imposing location 
rules on a lot of projects.

Regards Kenneth