Hello, I complained about this some time ago, but I can not find the thread. :)
I too wrote myself a basic script to do exactly what you described, but shortly I found that was not enough. I had to change if frequently until I ended up with the script that worked for UI translations that keep translations in package/po/ and help files in package/help/. Since many, many project like to use different paths (why?) like doc, docs, lalala, I had do add those. Then I had to add translators to credit their work ... I ended with the script based on the file name (packagename.type.branch.translator.language.po) that worked great until I stumbled upon projects that have some bizarre paths (why?) ... and yes, I had to add a "locator" to those po files header. I used firstline #' path/path since it was the only way I figured how to parse the filecontents in bash (I'm not really a bash programmer but it seems I managed so far). To end and follow this rant, I think adding locator seems wrong until projects have no " defined structure". I think in the first place all project should use /po for UI and /help for help ... there is no need for more complications. In case a "Locator" is added, I'd ask a bash guru to also include some info about getting the "path" out of the file. M! 2011/12/10 Daniel Mustieles García <daniel.mustie...@gmail.com> > 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 > >
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
