From: Jérôme <rom...@ya...> - 2009-10-27 17:02:35
|
>> 2) How do plugins in other projects handle translations? Is there an >> easy manner for shipping additional translation files with a plugin, >> and installing them? If not, I was thinking of an API for us to allow >> plugins to augment our current setup. > > This is a problem. The nicest would be to have translation inside of > the gramps.pot, but not possible with another repository. So the > solution would be to use for plugins a translation domain > grampsplugins, and have contributed plugins use _() function binded to > the domain grampsplugins. > For translators this should not be an issue, on translating > grampsplugins.pot, they can first use gramps.pot to translate > everything that is already present in the gramps module, then > translate only the missing strings. Tools like kbabel can work with > dictionaries making it even more simple. I used a dirty (but working) method for generating and merging translation strings into gramps.pot ! #! /bin/sh # .gramps/plugins directory ./get_strings *.py *.glade # there is a copy of current template on .gramps/plugins/po/gramps.pot cat messages.pot >> po/gramps.pot msguniq po/gramps.pot -o new.pot http://www.gramps-project.org/bugs/view.php?id=2771 http://www.gramps-project.org/wiki/index.php?title=Translating_GRAMPS#GNU_.60gettext.27_utilities http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps20/gramps2/src/get_strings Benny Malengier a écrit : > 2009/10/27 Doug Blank <dou...@gm...>: >> Developers, >> >> A few ideas I'd like to bounce off of you: >> >> 1) There are developers that work in gramps SVN, but that also have >> third-party contributions. I think many of those contributions live >> outside of our SVN, but there isn't really a reason why they must >> (right?). What if we had a src/plugins/contrib subdirectory in SVN >> where that code could be worked on in subdirs. It could also be >> packaged there (zipped file of .gpr.py and all necessary files). Then >> the plugin page could just point to the SVN repository. > > I think a separate repository should be made, so that users who have > access to that one, do not need access to the GRAMPS repo. > >> 2) How do plugins in other projects handle translations? Is there an >> easy manner for shipping additional translation files with a plugin, >> and installing them? If not, I was thinking of an API for us to allow >> plugins to augment our current setup. > > This is a problem. The nicest would be to have translation inside of > the gramps.pot, but not possible with another repository. So the > solution would be to use for plugins a translation domain > grampsplugins, and have contributed plugins use _() function binded to > the domain grampsplugins. > For translators this should not be an issue, on translating > grampsplugins.pot, they can first use gramps.pot to translate > everything that is already present in the gramps module, then > translate only the missing strings. Tools like kbabel can work with > dictionaries making it even more simple. > >> 3) What about creating a new extension for our plugins (perhaps >> .gplug) and a mime-type, so that we could load them, and humans would >> recognize what they are? > > You mean for the tar file with plugin in it? Yes, that is an option. > See http://live.gnome.org/Gedit/PythonPluginHowTo , so perhaps > gramps-plugin as extension. > > Benny > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |