On Mon, 11 Oct 2010 19:39:56 +0400 batden <[email protected]> said: that contains translations for specific applications and toolsets etc. not 1 mo per app at all (no way to know how the .desktop file maps to some specific .mo to open). what mo file contains the translations? if what you say is true - the .mo translations are used to GENERATe the.desktop files - then the .desktop files should have all the translations in them. they don't.
so where is the magic .mo or set of .mo's that need to be loaded and used? and don't tell me "every .mo in the langpack local dir needs to be loaded" as thats just not going to happen :) > Le lundi 11 octobre 2010 à 18:17 +0900, Carsten Haitzler a écrit : > > On Mon, 11 Oct 2010 12:40:17 +0400 batden <[email protected]> said: > > > > > Le lundi 11 octobre 2010 à 07:17 +0900, Carsten Haitzler a écrit : > > > > On Sun, 10 Oct 2010 11:31:21 +0200 Massimo Maiurana <[email protected]> > > > > said: > > > > > > > > > > > check the .desktop files. - i looked. MOST don't contain translations. > > > > where gnome gets its translations beats me. might be some newer fdo > > > > standard that splits them out - dunno. > > > > > > > > > > In GNOME, Xfce... the desktop files are translated directly in the po > > > files. > > > > > > http://live.gnome.org/TranslationProject/DevGuidelines/Localize%20using% > > > 20gettext%20and%20intltool > > > > > > http://live.gnome.org/GnomeGoals/CorrectDesktopFiles > > > > > > http://www.redhat.com/magazine/013nov05/features/freedesktop/ > > > (cf. "Easy translations") > > > > > > In E, we're doing it the (very) old-fashioned way... ;) > > > > beats me which po files they are :) > > > > As you well know, .po files are compiled to produce binary .mo files. > On Ubuntu, these .mo files are installed in (the non-standard > location) /usr/share/locale-langpack/<langcode>/LC_MESSAGES; > they are used to generate the .desktop files... > > Details: > https://wiki.ubuntu.com/Translations/Upstream/KDE/KubuntuTranslationsLifecycle > https://wiki.ubuntu.com/Translations/TranslationLifecycle > > > > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
