Re: Package synopses and blurbs translation

[John Darrington]

Packages which have a GUI, also need a .desktop file, which contains
two translatable strings:  "GenericName", and "Comment".  For example,
here is the .desktop file from pspp:

[Desktop Entry]
Name=GNU PSPP
GenericName=Statistical Software
GenericName[ca]=Programari estad??stic
GenericName[cs]=Statistick?? program
GenericName[de]=Statistiksoftware
GenericName[es]=Programario Estad??stico
GenericName[ja]=????????????????????????
GenericName[lt]=Statistin?? programin?? ??ranga
GenericName[nl]=Statistische software
GenericName[uk]=?????????????????????? ?????????????????? 
????????????????????????
Comment=Analyze statistical data with a free alternative to SPSS
Comment[ca]= Analitza dades estad??stiques amb una alternativa lliure a SPSS
Comment[cs]= Analyzuj statistick?? data se svobodnou variantou SPSS
Comment[de]= Statistische Daten mit einer freien Alternative zu SPSS analysieren
Comment[en_GB]= Analyse statistical data with a free alternative to SPSS
Comment[es]= Analiza datos estad??sticos con una alternativa libre a SPSS
Comment[ja]= 
????????????SPSS??????????????????????????????????????????????????????
Comment[lt]= Statistini?? duomen?? analizavimas su nemokama SPSS alternatyva
Comment[nl]= Analyseer statistische data met een vrij alternatief van SPSS
Comment[uk]= ???????????? ???????????????????????? ?????????? ?? ?????????????? 
???????????????????????? SPSS
Exec=psppire %F
Icon=pspp
Terminal=false
Type=Application
Categories=GTK;Education;Science;Math;
MimeType=application/x-spss-sav;application/x-spss-por;

The "Comment" string seems to serve the same purpose as Guix's "Synopsis" 
string. So I suggest that whatever method is used, we try to re-use one for the 
other.

I think the most desirable approach is to encourage package maintainers, to 
append the "Synopsis", "Description", "GenericName" etc strings to the .pot
files for their projects.  This saves having a team of translators dedicated
to translating names/descriptions of packages and the translators who are 
already familiar with a package are in the best position to make a translation.

However, not all package maintainers will comply.  So systems like Guix which
want to use Name/Description should look for the translation provided by the
package, and only if absent take one from a different source.

Just my $0.02

J'


On Mon, Jan 06, 2014 at 06:41:39PM +0100, Ludovic Court??s wrote:
     Hello, and best wishes!
     
     As discussed before [0], Guix needs to provide users with translated
     package synopses and descriptions.  It gets its synopses and
     descriptions for GNU packages from the Womb [1,2] (so does GSRC, IIRC),
     and has its own for non-GNU packages.
     
     There???s gettext infrastructure ready for that in Guix, but we need to
     coordinate so that the result is usable the all the possible users (web
     translators, GSRC, and Guix.)
     
     One possibility would be to use a specific text domain for package
     descriptions/synopses in Guix, and then submit that to the Translation
     Project.
     
     Another option is to let the web translators in charge of that (with
     GNUN), and then let Guix and GSRC synchronize periodically.  Guix would
     still have to use the TP for non-GNU packages, though I???m not sure how
     to handle that (different domain?).
     
     WDYT?
     
     Thanks,
     Ludo???.
     
     [0] https://lists.gnu.org/archive/html/guix-devel/2013-10/msg00090.html
     [1] 
http://cvs.savannah.gnu.org/viewvc/*checkout*/gnumaint/gnupackages.txt?root=womb
     [2] 
http://cvs.savannah.gnu.org/viewvc/*checkout*/gnumaint/pkgblurbs.txt?root=womb
     

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

signature.asc
Description: Digital signature