On Wed, 2007-12-26 at 09:12 +0100, Werner Hoch wrote: > Hi Kai-Martin, > > On Mittwoch, 26. Dezember 2007, Kai-Martin Knaak wrote: > > What to do for the German version?
IMPORTANT: Checkout the git master branch from git.gpleda.org before translating, not the peter-b version. There have been string changes since that work (which has now been merged). > Here are the steps required to create the translation: > * add de_DE to the LINGUAS file > * create a copy of libgeda30.pot --> de_DE.po (You might need to "make libgeda30.pot" in the libgeda/po directory first of all). > * translate the strings in de_DE.po (I've used kbabel for that) > * run "make install" in libgeda/po directory again. > > > Looks like gschem itself is perfectly in shape with po files > > contributed by Werner Hoch. It was libgeda which has new I18N support. gschem has had it for some time now, although there are updates needed (for the .desktop file describing the menu entry, and any strings which have changed since the last release.) Is "make update-po" something which is useful to run before you start translating? > > The po dir in gattrib seems to lack configuration. POTFILES.in > > contains just one line with "data/geda-gattrib.desktop.in". I'm am > > not familiar with the internationalization process. I guessed, > > POTFILES.in should contain all *.c files and LINGUS should specify > > "de_DE". Still, something seems to be missing. LINGUAS is empty because there aren't any translations yet. As people send translations, I'll add the relevant entry to the LINGUAS file. POTFILES.in is pretty bare, as only the menu entry .desktop is listed for translation. gattrib never supported translation, and work to add that support has not been done yet. I'm open to arguments for whether this should / should not be attempted. Ivan S. is working on gattrib, so it will clash with his work.. BUT, that said - this problem could / SHOULD be solved by Ivan making a repository available, and pushing code changes incrementally as the work is done. It would be a shame to halt all progress whilst waiting for something better. > > If I call make in /peter-b/gattrib/po I get: > > > > /------------ > > [EMAIL PROTECTED]:/usr/local/geda-src/peter-b/gattrib/po$ make > > cd .. \ > > && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ > > /bin/sh ./config.status > > config.status: creating po/Makefile.in > > config.status: executing depfiles commands > > config.status: executing intltool commands > > config.status: executing po-directories commands > > config.status: creating po/POTFILES > > config.status: creating po/Makefile > > config.status: executing po/stamp-it commands > > make: *** No rule to make target `de_DE.gmo', needed by `all-yes'. > > Stop. \----------------- Did you add de_DE to the LINGUAS file? If so, you need to provide a de_DE.po file, or there will be no rule to make de_DE.gmo For starting out run: make geda-gattrib.pot in the gattrib/po directory. Then copy geda-gattrib.pot to de_DE.po as usual. Hopefully this will satisfy the build process. > If it does not work for you I can push the initial translation files to > the git repo either this evening or tomorrow. I've left them out of libgeda (at lest) for a reason: libgeda30.pot is the wrong file-name to check in. The name will be right once the so version has been bumped. (Probably 32:0:0 for the next development release, 1.3.0). It is a shame the build tools won't let me call it libgeda.pot in the repository, and install the translations to libgedaXX.mo etc.., however the same GETTEXT_PACKAGE string is used for the .pot file, the final installed .mo file names and the translation domain to bind to at run-time. It seems the easiest thing will be to rename the pot file (if checked into the repository) with each SO version bump, so this is my plan so far. Best wishes, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
