gryf/wmaker
1
0
Fork 0
mirror of https://github.com/gryf/wmaker.git synced 2026-01-03 20:34:14 +01:00
Code Issues Projects Releases Wiki Activity

make: new target 'update-lang' to update the PO files for a languages against latest sources

Browse Source 
With the new target, it is now easy to update all translations in the
project for a language against latest code with the simple command, run
from the top directory:

  make update-lang PO=<lang>

Signed-off-by: Christophe CURIS <christophe.curis@free.fr>
This commit is contained in:
Christophe CURIS
2015-01-20 22:04:10 +01:00
committed by Carlos R. Mafra
parent 2429d5e196
commit a9a0d2ac85
7 changed files with 218 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/build/Translations.texi vendored
View File

@@ -348,6 +348,9 @@ value. If you don't know what is the correct value, unset it.
You may have noticed that many translations are not up to date, because the code has evolved but the
persons who initially contributed may not have had the time to continue, so any help is welcome.
Since @sc{Window Maker} 0.95.7 there are some targets to @command{make} that can help you in that
task.
@c ------------------------------------------------------------------ Install the latest sources ---
@section Install the latest sources
@@ -425,7 +428,16 @@ In @sc{Window Maker}, you have actually 4 @code{po} files to take care of:
@item @file{util/po/@emph{<lang>}.po}: for the command-line tools of @sc{Window Maker}
@end itemize
As stated previously, there is a @command{make} target that can help you to automatically generate
the POT and update the PO for these 4 cases:
@example
make update-lang PO=<lang>
@end example
Once run, it will have updated as needed the 4 @code{po} files against the latest source code.
You may wish to use the command @command{git gui} to view the changes;
you can now edit the files to complete the translation, correct them, remove deprecated stuff, ...
Please note that the encoding should be set to @emph{UTF-8} as this is now the standard.
If you think an error message is too obscure, just ask on the developer mailing list