From: jerome <rom...@ya...> - 2011-07-14 18:42:04
|
Hi Keiichiro, Since there was some changes on locales management I could be wrong, but the last time I needed to test an other localized relationship handler, it seems to me that I forced the LANGUAGE variable! http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable You are running sources with some modifications, maybe some settings will be naturally set with a standard installation ? > If there's another proper way (without making relationship > calculator, or > how to properly create rel calculator), please guide me, > thanks. For now, you have french strings and relations ! If you understand french and japanese calculation is the same, you can translate the hard coded strings into your new rel_ja.py. But --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> a écrit : > De: yanmar <k.y...@gm...> > Objet: Re: Let me join Gramps project (Japanese) > À: "jerome" <rom...@ya...> > Cc: "Brian Matherly" <br...@gr...> > Date: Jeudi 14 juillet 2011, 0h22 > Hi Jerome, > > Thanks for your advise, I can reflect my translation. > The point was relationship calculator. I've tried to add > Japanese one. > > 1. LOCALEDIR is set on /usr/local/share/locale and there's > gramps.mo file > under ja/LC_MESSAGES. > > 2. But the message was not vanished: > "No translation available for language 'ja'. Using > 'english' instead." > > 3. I've greped the error on code, and fount the part on > Relationship.py, > get_relationship_calculator method. there's if-else > checking of > relationship calculator > as the translation exists or not. > > 4. so, I've quickly added the ja module for recognition. > # cd /usr/local/share/gramps/plugins/rel > # cp rel_fr.py rel_ja.py # just copied, no editing > # vi relplugins.gpr.py # and added below: > --- > # ja > plg = newplugin() > plg.id = 'relcalc_ja' > plg.name = _("Japanese Relationship Calculator") > plg.description = _("Calculates relationships between > people") > plg.version = '1.0' > plg.gramps_target_version = '3.3' > plg.status = STABLE > plg.fname = 'rel_ja.py' > plg.ptype = RELCALC > plg.relcalcclass = 'RelationshipCalculator' > plg.lang_list = ["ja", "JA", "ja_JP", "日本語", > "Japanese", "ja_JP.UTF8", > > "ja_JP.UTF-8", "ja_JP.utf-8", > "ja_JP.utf8"] > --- > > If there's another proper way (without making relationship > calculator, or > how to properly create rel calculator), please guide me, > thanks. > > Regards > Keiichiro Yamamoto > |
From: Benny M. <ben...@gm...> - 2011-07-15 07:19:54
|
Use the test to check your translation, see bottom of eg rel_fr.py: export PYTHONPATH=/path/to/gramps/src python src/plugins/rel/rel_ja.py which will show you if you make errors or not. As base of your japanese relationship calculation, use a language that already is close to the japanese way of relationships. 2011/7/14 jerome <rom...@ya...> > Hi Keiichiro, > > > Since there was some changes on locales management I could be wrong, but > the last time I needed to test an other localized relationship handler, it > seems to me that I forced the LANGUAGE variable! > > > http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html > > http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable > > You are running sources with some modifications, maybe some settings will > be naturally set with a standard installation ? > > > If there's another proper way (without making relationship > > calculator, or > > how to properly create rel calculator), please guide me, > > thanks. > > For now, you have french strings and relations ! > If you understand french and japanese calculation is the same, you can > translate the hard coded strings into your new rel_ja.py. > > But > > --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> a écrit : > > > De: yanmar <k.y...@gm...> > > Objet: Re: Let me join Gramps project (Japanese) > > À: "jerome" <rom...@ya...> > > Cc: "Brian Matherly" <br...@gr...> > > Date: Jeudi 14 juillet 2011, 0h22 > > Hi Jerome, > > > > Thanks for your advise, I can reflect my translation. > > The point was relationship calculator. I've tried to add > > Japanese one. > > > > 1. LOCALEDIR is set on /usr/local/share/locale and there's > > gramps.mo file > > under ja/LC_MESSAGES. > > > > 2. But the message was not vanished: > > "No translation available for language 'ja'. Using > > 'english' instead." > > > > 3. I've greped the error on code, and fount the part on > > Relationship.py, > > get_relationship_calculator method. there's if-else > > checking of > > relationship calculator > > as the translation exists or not. > > > > 4. so, I've quickly added the ja module for recognition. > > # cd /usr/local/share/gramps/plugins/rel > > # cp rel_fr.py rel_ja.py # just copied, no editing > > # vi relplugins.gpr.py # and added below: > > --- > > # ja > > plg = newplugin() > > plg.id = 'relcalc_ja' > > plg.name = _("Japanese Relationship Calculator") > > plg.description = _("Calculates relationships between > > people") > > plg.version = '1.0' > > plg.gramps_target_version = '3.3' > > plg.status = STABLE > > plg.fname = 'rel_ja.py' > > plg.ptype = RELCALC > > plg.relcalcclass = 'RelationshipCalculator' > > plg.lang_list = ["ja", "JA", "ja_JP", "日本語", > > "Japanese", "ja_JP.UTF8", > > > > "ja_JP.UTF-8", "ja_JP.utf-8", > > "ja_JP.utf8"] > > --- > > > > If there's another proper way (without making relationship > > calculator, or > > how to properly create rel calculator), please guide me, > > thanks. > > > > Regards > > Keiichiro Yamamoto > > > > > > > ------------------------------------------------------------------------------ > AppSumo Presents a FREE Video for the SourceForge Community by Eric > Ries, the creator of the Lean Startup Methodology on "Lean Startup > Secrets Revealed." This video shows you how to validate your ideas, > optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: yanmar <k.y...@gm...> - 2011-07-30 13:44:21
|
Hello Benny, > Use the test to check your translation, see bottom of eg rel_fr.py: > export PYTHONPATH=/path/to/gramps/src python src/plugins/rel/rel_ja.py > which will show you if you make errors or not. I've tried your test script on rel_fr.py Not yet translated any string for rel_ja.py, but I've understood how to use it. > As base of your japanese relationship calculation, use a language that > already is close to the japanese way of relationships. When starting rel_ja.py, I'll do as your advice, Thanks! --- Regards Keiichiro Yamamoto 2011/7/15 Benny Malengier <ben...@gm...>: > Use the test to check your translation, see bottom of eg rel_fr.py: > > export PYTHONPATH=/path/to/gramps/src python src/plugins/rel/rel_ja.py > > which will show you if you make errors or not. > > As base of your japanese relationship calculation, use a language that > already is close to the japanese way of relationships. > > 2011/7/14 jerome <rom...@ya...> >> >> Hi Keiichiro, >> >> >> Since there was some changes on locales management I could be wrong, but >> the last time I needed to test an other localized relationship handler, it >> seems to me that I forced the LANGUAGE variable! >> >> >> http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html >> >> http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable >> >> You are running sources with some modifications, maybe some settings will >> be naturally set with a standard installation ? >> >> > If there's another proper way (without making relationship >> > calculator, or >> > how to properly create rel calculator), please guide me, >> > thanks. >> >> For now, you have french strings and relations ! >> If you understand french and japanese calculation is the same, you can >> translate the hard coded strings into your new rel_ja.py. >> >> But >> >> --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> a écrit : >> >> > De: yanmar <k.y...@gm...> >> > Objet: Re: Let me join Gramps project (Japanese) >> > À: "jerome" <rom...@ya...> >> > Cc: "Brian Matherly" <br...@gr...> >> > Date: Jeudi 14 juillet 2011, 0h22 >> > Hi Jerome, >> > >> > Thanks for your advise, I can reflect my translation. >> > The point was relationship calculator. I've tried to add >> > Japanese one. >> > >> > 1. LOCALEDIR is set on /usr/local/share/locale and there's >> > gramps.mo file >> > under ja/LC_MESSAGES. >> > >> > 2. But the message was not vanished: >> > "No translation available for language 'ja'. Using >> > 'english' instead." >> > >> > 3. I've greped the error on code, and fount the part on >> > Relationship.py, >> > get_relationship_calculator method. there's if-else >> > checking of >> > relationship calculator >> > as the translation exists or not. >> > >> > 4. so, I've quickly added the ja module for recognition. >> > # cd /usr/local/share/gramps/plugins/rel >> > # cp rel_fr.py rel_ja.py # just copied, no editing >> > # vi relplugins.gpr.py # and added below: >> > --- >> > # ja >> > plg = newplugin() >> > plg.id = 'relcalc_ja' >> > plg.name = _("Japanese Relationship Calculator") >> > plg.description = _("Calculates relationships between >> > people") >> > plg.version = '1.0' >> > plg.gramps_target_version = '3.3' >> > plg.status = STABLE >> > plg.fname = 'rel_ja.py' >> > plg.ptype = RELCALC >> > plg.relcalcclass = 'RelationshipCalculator' >> > plg.lang_list = ["ja", "JA", "ja_JP", "日本語", >> > "Japanese", "ja_JP.UTF8", >> > >> > "ja_JP.UTF-8", "ja_JP.utf-8", >> > "ja_JP.utf8"] >> > --- >> > >> > If there's another proper way (without making relationship >> > calculator, or >> > how to properly create rel calculator), please guide me, >> > thanks. >> > >> > Regards >> > Keiichiro Yamamoto >> > >> >> >> >> >> ------------------------------------------------------------------------------ >> AppSumo Presents a FREE Video for the SourceForge Community by Eric >> Ries, the creator of the Lean Startup Methodology on "Lean Startup >> Secrets Revealed." This video shows you how to validate your ideas, >> optimize your ideas and identify your business strategy. >> http://p.sf.net/sfu/appsumosfdev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > -- 山本慶一郎 k.y...@gm... |
From: jerome <rom...@ya...> - 2011-07-14 19:00:28
|
> For now, you have french strings and relations ! > If you understand french and japanese calculation is the > same, you can translate the hard coded strings into your new > rel_ja.py. But most localized relationships handler are different. The common code/classes are on Relationship.py module As you can see only the content of few classes is different. Here are the cultural issues, which need to be coded/handled. rel_fr.py uses simple code but I guess that relationship calculation is different for Japanese and french ? You can also look at other relationship handlers. Benny made some useful testing for translators (who do not often write python code ...), see the end of rel_ja.py: # Test function. Call it as follows from the command line (so as to find # imported modules): # export PYTHONPATH=/path/to/gramps/src # python src/plugins/rel/rel_ja.py # (Above not needed here) For you, under a console, this could be something like: $ export PYTHONPATH=/usr/local/share/gramps $ python /usr/local/share/gramps/rel/rel_ja.py then follow the instructions and try to modify your file. Regards, Jérôme --- En date de : Jeu 14.7.11, jerome <rom...@ya...> a écrit : > De: jerome <rom...@ya...> > Objet: Re: [Gramps-devel] Let me join Gramps project (Japanese) > À: "yanmar" <k.y...@gm...>, gra...@li... > Date: Jeudi 14 juillet 2011, 20h41 > Hi Keiichiro, > > > Since there was some changes on locales management I could > be wrong, but the last time I needed to test an other > localized relationship handler, it seems to me that I forced > the LANGUAGE variable! > > http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html > http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable > > You are running sources with some modifications, maybe some > settings will be naturally set with a standard installation > ? > > > If there's another proper way (without making > relationship > > calculator, or > > how to properly create rel calculator), please guide > me, > > thanks. > > For now, you have french strings and relations ! > If you understand french and japanese calculation is the > same, you can translate the hard coded strings into your new > rel_ja.py. > > But > > --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> > a écrit : > > > De: yanmar <k.y...@gm...> > > Objet: Re: Let me join Gramps project (Japanese) > > À: "jerome" <rom...@ya...> > > Cc: "Brian Matherly" <br...@gr...> > > Date: Jeudi 14 juillet 2011, 0h22 > > Hi Jerome, > > > > Thanks for your advise, I can reflect my translation. > > The point was relationship calculator. I've tried to > add > > Japanese one. > > > > 1. LOCALEDIR is set on /usr/local/share/locale and > there's > > gramps.mo file > > under ja/LC_MESSAGES. > > > > 2. But the message was not vanished: > > "No translation available for language 'ja'. Using > > 'english' instead." > > > > 3. I've greped the error on code, and fount the part > on > > Relationship.py, > > get_relationship_calculator method. there's if-else > > checking of > > relationship calculator > > as the translation exists or not. > > > > 4. so, I've quickly added the ja module for > recognition. > > # cd /usr/local/share/gramps/plugins/rel > > # cp rel_fr.py rel_ja.py # just copied, no editing > > # vi relplugins.gpr.py # and added below: > > --- > > # ja > > plg = newplugin() > > plg.id = 'relcalc_ja' > > plg.name = _("Japanese Relationship Calculator") > > plg.description = _("Calculates relationships > between > > people") > > plg.version = '1.0' > > plg.gramps_target_version = '3.3' > > plg.status = STABLE > > plg.fname = 'rel_ja.py' > > plg.ptype = RELCALC > > plg.relcalcclass = 'RelationshipCalculator' > > plg.lang_list = ["ja", "JA", "ja_JP", "日本語", > > "Japanese", "ja_JP.UTF8", > > > > "ja_JP.UTF-8", "ja_JP.utf-8", > > "ja_JP.utf8"] > > --- > > > > If there's another proper way (without making > relationship > > calculator, or > > how to properly create rel calculator), please guide > me, > > thanks. > > > > Regards > > Keiichiro Yamamoto > > > > > > ------------------------------------------------------------------------------ > AppSumo Presents a FREE Video for the SourceForge Community > by Eric > Ries, the creator of the Lean Startup Methodology on "Lean > Startup > Secrets Revealed." This video shows you how to validate > your ideas, > optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: yanmar <k.y...@gm...> - 2011-07-30 13:27:16
|
Hi Jerome, I've checked the minimum condition for reflecting my PO translation, under branches/maintenance/gramps33. Don't need to create rel_ja.py, edit relplugins.gpr.py just for this purpose. All I have to do is below: --- 1. Add "ja" string to ALL_LINGUAS variable on configure.in: ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR pt_PT ru sv fi lt sk bg hr sl ca sq he uk ja" 2. Put po/ja.po (partly translated, and not all string is "fuzzy") 3. Execute ./autogen.sh, make, make install (as root depends on prefix) --- This makes ${prefix}/share/locale/ja/LC_MESSAGES/gramps.mo correctly. And, my Japanese translation is applied expectedly ; ) > Since there was some changes on locales management I could be wrong, but the last time I needed to test an other localized relationship handler, it seems to me that I forced the LANGUAGE variable! I've checked $LANGUAGE variable, but It was set "ja:en" - appears no influence. Regards, Keiichiro Yamamoto 2011/7/15 jerome <rom...@ya...>: > Hi Keiichiro, > > > Since there was some changes on locales management I could be wrong, but the last time I needed to test an other localized relationship handler, it seems to me that I forced the LANGUAGE variable! > > http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html > http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable > > You are running sources with some modifications, maybe some settings will be naturally set with a standard installation ? > >> If there's another proper way (without making relationship >> calculator, or >> how to properly create rel calculator), please guide me, >> thanks. > > For now, you have french strings and relations ! > If you understand french and japanese calculation is the same, you can translate the hard coded strings into your new rel_ja.py. > > But > > --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> a écrit : > >> De: yanmar <k.y...@gm...> >> Objet: Re: Let me join Gramps project (Japanese) >> À: "jerome" <rom...@ya...> >> Cc: "Brian Matherly" <br...@gr...> >> Date: Jeudi 14 juillet 2011, 0h22 >> Hi Jerome, >> >> Thanks for your advise, I can reflect my translation. >> The point was relationship calculator. I've tried to add >> Japanese one. >> >> 1. LOCALEDIR is set on /usr/local/share/locale and there's >> gramps.mo file >> under ja/LC_MESSAGES. >> >> 2. But the message was not vanished: >> "No translation available for language 'ja'. Using >> 'english' instead." >> >> 3. I've greped the error on code, and fount the part on >> Relationship.py, >> get_relationship_calculator method. there's if-else >> checking of >> relationship calculator >> as the translation exists or not. >> >> 4. so, I've quickly added the ja module for recognition. >> # cd /usr/local/share/gramps/plugins/rel >> # cp rel_fr.py rel_ja.py # just copied, no editing >> # vi relplugins.gpr.py # and added below: >> --- >> # ja >> plg = newplugin() >> plg.id = 'relcalc_ja' >> plg.name = _("Japanese Relationship Calculator") >> plg.description = _("Calculates relationships between >> people") >> plg.version = '1.0' >> plg.gramps_target_version = '3.3' >> plg.status = STABLE >> plg.fname = 'rel_ja.py' >> plg.ptype = RELCALC >> plg.relcalcclass = 'RelationshipCalculator' >> plg.lang_list = ["ja", "JA", "ja_JP", "日本語", >> "Japanese", "ja_JP.UTF8", >> >> "ja_JP.UTF-8", "ja_JP.utf-8", >> "ja_JP.utf8"] >> --- >> >> If there's another proper way (without making relationship >> calculator, or >> how to properly create rel calculator), please guide me, >> thanks. >> >> Regards >> Keiichiro Yamamoto >> > > > |
From: yanmar <k.y...@gm...> - 2011-07-31 02:02:09
|
Hi Jerome, > I wondering why you need to edit relplugins.gpr.py for having Japanese translation ! Yes, No need as you say. So I wrote like below, and also tested by myself too. > Don't need to create rel_ja.py, edit relplugins.gpr.py My ja.po can be applied without editing/creating any relationship codes. that's right ; ) # also no need for any DateDisplay files. sorry for making you debug... And, thanks for adding my file, and try to increase more translated phrases. > Note, I added your first version on SVN (3.3.x, trunk): > http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po I've also created my github repository for personal work. You can check the progress here: https://github.com/yanmar/gramps-translation-ja/ Regards, Keiichiro Yamamoto 2011/7/31 jerome <rom...@ya...> > > Hi Keiichiro, > > I wondering why you need to edit relplugins.gpr.py for having Japanese translation ! > > There is maybe one possible issue with Date Display (see DateHandler/_DateHandler.py): >re > LANG_TO_DISPLAY = { > 'C' : DateDisplayEn, > 'en' : DateDisplayEn, > 'English_United States' : DateDisplayEn, > 'zh_CN' : DateDisplay, > 'zh_TW' : DateDisplay, > 'zh_SG' : DateDisplay, > 'zh_HK' : DateDisplay, > 'ja_JP' : DateDisplay, > 'ko_KR' : DateDisplay, > 'nb_NO' : DateDisplay, > } > > but localized Relationships handlers are plugins, which are based on the main class: class RelationshipCalculator(Relationship.RelationshipCalculator) > > If they don't exist, Gramps uses main class (same as english). > > Anyway, these localized modules are using hardcoded translated strings/methods, so as you want, you can also try to translate them with addition of the "simple/common" ja.po for gramps interface (labels, menu, tooltips, tips, entries on lists, etc ...). > > > Note, I added your first version on SVN (3.3.x, trunk): > http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po > > Currently, it is disable (ignored by configure.in) and with all "fuzzy" strings. If you have a better version, I can update the current one. > > > Regards, > Jérôme > > > --- En date de : Sam 30.7.11, yanmar <k.y...@gm...> a écrit : > > > De: yanmar <k.y...@gm...> > > Objet: Re: Let me join Gramps project (Japanese) > > À: gra...@li... > > Cc: "jerome" <rom...@ya...> > > Date: Samedi 30 juillet 2011, 15h27 > > Hi Jerome, > > > > I've checked the minimum condition for reflecting my PO > > translation, > > under branches/maintenance/gramps33. > > Don't need to create rel_ja.py, edit relplugins.gpr.py just > > for this purpose. > > > > All I have to do is below: > > --- > > 1. Add "ja" string to ALL_LINGUAS variable on > > configure.in: > > ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR > > pt_PT ru sv > > fi lt sk bg hr sl ca sq he uk ja" > > 2. Put po/ja.po (partly translated, and not all string is > > "fuzzy") > > 3. Execute ./autogen.sh, make, make install (as root > > depends on prefix) > > --- > > > > This makes ${prefix}/share/locale/ja/LC_MESSAGES/gramps.mo > > correctly. > > And, my Japanese translation is applied expectedly ; ) > > > > > Since there was some changes on locales management I > > could be wrong, but the last time I needed to test an other > > localized relationship handler, it seems to me that I forced > > the LANGUAGE variable! > > > > I've checked $LANGUAGE variable, but It was set "ja:en" - > > appears no influence. > > > > > > Regards, > > Keiichiro Yamamoto > > > > > > 2011/7/15 jerome <rom...@ya...>: > > > Hi Keiichiro, > > > > > > > > > Since there was some changes on locales management I > > could be wrong, but the last time I needed to test an other > > localized relationship handler, it seems to me that I forced > > the LANGUAGE variable! > > > > > > http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html > > > http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable > > > > > > You are running sources with some modifications, maybe > > some settings will be naturally set with a standard > > installation ? > > > > > >> If there's another proper way (without making > > relationship > > >> calculator, or > > >> how to properly create rel calculator), please > > guide me, > > >> thanks. > > > > > > For now, you have french strings and relations ! > > > If you understand french and japanese calculation is > > the same, you can translate the hard coded strings into your > > new rel_ja.py. > > > > > > But > > > > > > --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> > > a écrit : > > > > > >> De: yanmar <k.y...@gm...> > > >> Objet: Re: Let me join Gramps project (Japanese) > > >> À: "jerome" <rom...@ya...> > > >> Cc: "Brian Matherly" <br...@gr...> > > >> Date: Jeudi 14 juillet 2011, 0h22 > > >> Hi Jerome, > > >> > > >> Thanks for your advise, I can reflect my > > translation. > > >> The point was relationship calculator. I've tried > > to add > > >> Japanese one. > > >> > > >> 1. LOCALEDIR is set on /usr/local/share/locale and > > there's > > >> gramps.mo file > > >> under ja/LC_MESSAGES. > > >> > > >> 2. But the message was not vanished: > > >> "No translation available for language 'ja'. > > Using > > >> 'english' instead." > > >> > > >> 3. I've greped the error on code, and fount the > > part on > > >> Relationship.py, > > >> get_relationship_calculator method. there's > > if-else > > >> checking of > > >> relationship calculator > > >> as the translation exists or not. > > >> > > >> 4. so, I've quickly added the ja module for > > recognition. > > >> # cd /usr/local/share/gramps/plugins/rel > > >> # cp rel_fr.py rel_ja.py # just copied, no > > editing > > >> # vi relplugins.gpr.py # and added below: > > >> --- > > >> # ja > > >> plg = newplugin() > > >> plg.id = 'relcalc_ja' > > >> plg.name = _("Japanese Relationship > > Calculator") > > >> plg.description = _("Calculates relationships > > between > > >> people") > > >> plg.version = '1.0' > > >> plg.gramps_target_version = '3.3' > > >> plg.status = STABLE > > >> plg.fname = 'rel_ja.py' > > >> plg.ptype = RELCALC > > >> plg.relcalcclass = 'RelationshipCalculator' > > >> plg.lang_list = ["ja", "JA", "ja_JP", > > "日本語", > > >> "Japanese", "ja_JP.UTF8", > > >> > > >> "ja_JP.UTF-8", "ja_JP.utf-8", > > >> "ja_JP.utf8"] > > >> --- > > >> > > >> If there's another proper way (without making > > relationship > > >> calculator, or > > >> how to properly create rel calculator), please > > guide me, > > >> thanks. > > >> > > >> Regards > > >> Keiichiro Yamamoto > > >> > > > > > > > > > > > -- 山本慶一郎 k.y...@gm... |
From: Jérôme <rom...@ya...> - 2011-07-31 09:50:22
|
> I've also created my github repository for personal work. You can > check the progress here: > https://github.com/yanmar/gramps-translation-ja/ Ah, great ! I should be able to merge it with current SVN version. As you noted gramps' repositories for code use SVN hosted by sourceforge. This means that we need to take care of multiple changes by different persons for the same file at the same time... Mainly for translations, which could have differents template references (gramps.pot) and contributors. Patching a po gettext often means merging plain text with specific syntax! The second limitation is the commit rights, translators also have access to the complete code, also to split translations and code could be a nightmare for maintenance - like launchpad translations - which need to be linked with a program version (sometimes need to translate and mix some *.po for devel versions under Ubuntu...). I suppose it should be possible that you only commit ja.po under gramps' svn because ja.po is currently only hosted and not enabled, but as contributions should not break the code, this makes sense that commit rights cannot be given too fast... Note, current po directory under SVN also provides some scripts for testing our translation file and it is integrated with installation environment (make, database for addons, maintenance, log, etc ...) Regards, Jérôme yanmar a écrit : > Hi Jerome, > >> I wondering why you need to edit relplugins.gpr.py for having Japanese translation ! > > Yes, No need as you say. So I wrote like below, and also tested by myself too. >> Don't need to create rel_ja.py, edit relplugins.gpr.py > My ja.po can be applied without editing/creating any relationship > codes. that's right ; ) > # also no need for any DateDisplay files. sorry for making you debug... > > And, thanks for adding my file, and try to increase more translated phrases. >> Note, I added your first version on SVN (3.3.x, trunk): >> http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po > > I've also created my github repository for personal work. You can > check the progress here: > https://github.com/yanmar/gramps-translation-ja/ > > Regards, > Keiichiro Yamamoto > > > 2011/7/31 jerome <rom...@ya...> >> Hi Keiichiro, >> >> I wondering why you need to edit relplugins.gpr.py for having Japanese translation ! >> >> There is maybe one possible issue with Date Display (see DateHandler/_DateHandler.py): >> re >> LANG_TO_DISPLAY = { >> 'C' : DateDisplayEn, >> 'en' : DateDisplayEn, >> 'English_United States' : DateDisplayEn, >> 'zh_CN' : DateDisplay, >> 'zh_TW' : DateDisplay, >> 'zh_SG' : DateDisplay, >> 'zh_HK' : DateDisplay, >> 'ja_JP' : DateDisplay, >> 'ko_KR' : DateDisplay, >> 'nb_NO' : DateDisplay, >> } >> >> but localized Relationships handlers are plugins, which are based on the main class: class RelationshipCalculator(Relationship.RelationshipCalculator) >> >> If they don't exist, Gramps uses main class (same as english). >> >> Anyway, these localized modules are using hardcoded translated strings/methods, so as you want, you can also try to translate them with addition of the "simple/common" ja.po for gramps interface (labels, menu, tooltips, tips, entries on lists, etc ...). >> >> >> Note, I added your first version on SVN (3.3.x, trunk): >> http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po >> >> Currently, it is disable (ignored by configure.in) and with all "fuzzy" strings. If you have a better version, I can update the current one. >> >> >> Regards, >> Jérôme >> >> >> --- En date de : Sam 30.7.11, yanmar <k.y...@gm...> a écrit : >> >>> De: yanmar <k.y...@gm...> >>> Objet: Re: Let me join Gramps project (Japanese) >>> À: gra...@li... >>> Cc: "jerome" <rom...@ya...> >>> Date: Samedi 30 juillet 2011, 15h27 >>> Hi Jerome, >>> >>> I've checked the minimum condition for reflecting my PO >>> translation, >>> under branches/maintenance/gramps33. >>> Don't need to create rel_ja.py, edit relplugins.gpr.py just >>> for this purpose. >>> >>> All I have to do is below: >>> --- >>> 1. Add "ja" string to ALL_LINGUAS variable on >>> configure.in: >>> ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR >>> pt_PT ru sv >>> fi lt sk bg hr sl ca sq he uk ja" >>> 2. Put po/ja.po (partly translated, and not all string is >>> "fuzzy") >>> 3. Execute ./autogen.sh, make, make install (as root >>> depends on prefix) >>> --- >>> >>> This makes ${prefix}/share/locale/ja/LC_MESSAGES/gramps.mo >>> correctly. >>> And, my Japanese translation is applied expectedly ; ) >>> >>>> Since there was some changes on locales management I >>> could be wrong, but the last time I needed to test an other >>> localized relationship handler, it seems to me that I forced >>> the LANGUAGE variable! >>> >>> I've checked $LANGUAGE variable, but It was set "ja:en" - >>> appears no influence. >>> >>> >>> Regards, >>> Keiichiro Yamamoto >>> >>> >>> 2011/7/15 jerome <rom...@ya...>: >>>> Hi Keiichiro, >>>> >>>> >>>> Since there was some changes on locales management I >>> could be wrong, but the last time I needed to test an other >>> localized relationship handler, it seems to me that I forced >>> the LANGUAGE variable! >>>> http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html >>>> http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable >>>> >>>> You are running sources with some modifications, maybe >>> some settings will be naturally set with a standard >>> installation ? >>>>> If there's another proper way (without making >>> relationship >>>>> calculator, or >>>>> how to properly create rel calculator), please >>> guide me, >>>>> thanks. >>>> For now, you have french strings and relations ! >>>> If you understand french and japanese calculation is >>> the same, you can translate the hard coded strings into your >>> new rel_ja.py. >>>> But >>>> >>>> --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> >>> a écrit : >>>>> De: yanmar <k.y...@gm...> >>>>> Objet: Re: Let me join Gramps project (Japanese) >>>>> À: "jerome" <rom...@ya...> >>>>> Cc: "Brian Matherly" <br...@gr...> >>>>> Date: Jeudi 14 juillet 2011, 0h22 >>>>> Hi Jerome, >>>>> >>>>> Thanks for your advise, I can reflect my >>> translation. >>>>> The point was relationship calculator. I've tried >>> to add >>>>> Japanese one. >>>>> >>>>> 1. LOCALEDIR is set on /usr/local/share/locale and >>> there's >>>>> gramps.mo file >>>>> under ja/LC_MESSAGES. >>>>> >>>>> 2. But the message was not vanished: >>>>> "No translation available for language 'ja'. >>> Using >>>>> 'english' instead." >>>>> >>>>> 3. I've greped the error on code, and fount the >>> part on >>>>> Relationship.py, >>>>> get_relationship_calculator method. there's >>> if-else >>>>> checking of >>>>> relationship calculator >>>>> as the translation exists or not. >>>>> >>>>> 4. so, I've quickly added the ja module for >>> recognition. >>>>> # cd /usr/local/share/gramps/plugins/rel >>>>> # cp rel_fr.py rel_ja.py # just copied, no >>> editing >>>>> # vi relplugins.gpr.py # and added below: >>>>> --- >>>>> # ja >>>>> plg = newplugin() >>>>> plg.id = 'relcalc_ja' >>>>> plg.name = _("Japanese Relationship >>> Calculator") >>>>> plg.description = _("Calculates relationships >>> between >>>>> people") >>>>> plg.version = '1.0' >>>>> plg.gramps_target_version = '3.3' >>>>> plg.status = STABLE >>>>> plg.fname = 'rel_ja.py' >>>>> plg.ptype = RELCALC >>>>> plg.relcalcclass = 'RelationshipCalculator' >>>>> plg.lang_list = ["ja", "JA", "ja_JP", >>> "日本語", >>>>> "Japanese", "ja_JP.UTF8", >>>>> >>>>> "ja_JP.UTF-8", "ja_JP.utf-8", >>>>> "ja_JP.utf8"] >>>>> --- >>>>> >>>>> If there's another proper way (without making >>> relationship >>>>> calculator, or >>>>> how to properly create rel calculator), please >>> guide me, >>>>> thanks. >>>>> >>>>> Regards >>>>> Keiichiro Yamamoto >>>>> >>>> >>>> > > > > -- > 山本慶一郎 > k.y...@gm... > |
From: yanmar <k.y...@gm...> - 2011-07-31 12:49:19
|
Hi Jerome, > Ah, great ! > I should be able to merge it with current SVN version. Yes, please do as you like ; ) # but I'll inform you everytime the project goes some extent. > I suppose it should be possible that you only commit ja.po under gramps' svn > because ja.po is currently only hosted and not enabled, but as contributions > should not break the code, this makes sense that commit rights cannot be > given too fast... It's okay. I also think it's better way for management. When I want to hack gramps, I'll clone it on my local repo, using Git :P > Note, current po directory under SVN also provides some scripts for testing > our translation file and it is integrated with installation environment > (make, database for addons, maintenance, log, etc ...) Okay, I recognized. Maybe when I need testing or these kind of functionarities, It's enough for me just to override my po on gramps33 directory, for some time. Regards Keiichiro Yamamoto 2011/7/31 Jérôme <rom...@ya...>: >> I've also created my github repository for personal work. You can >> check the progress here: >> https://github.com/yanmar/gramps-translation-ja/ > > Ah, great ! > I should be able to merge it with current SVN version. > > As you noted gramps' repositories for code use SVN hosted by sourceforge. > This means that we need to take care of multiple changes by different > persons for the same file at the same time... > Mainly for translations, which could have differents template references > (gramps.pot) and contributors. Patching a po gettext often means merging > plain text with specific syntax! > > The second limitation is the commit rights, translators also have access to > the complete code, also to split translations and code could be a nightmare > for maintenance - like launchpad translations - which need to be linked with > a program version (sometimes need to translate and mix some *.po for devel > versions under Ubuntu...). > > I suppose it should be possible that you only commit ja.po under gramps' svn > because ja.po is currently only hosted and not enabled, but as contributions > should not break the code, this makes sense that commit rights cannot be > given too fast... > > Note, current po directory under SVN also provides some scripts for testing > our translation file and it is integrated with installation environment > (make, database for addons, maintenance, log, etc ...) > > > Regards, > Jérôme > > > yanmar a écrit : >> >> Hi Jerome, >> >>> I wondering why you need to edit relplugins.gpr.py for having Japanese >>> translation ! >> >> Yes, No need as you say. So I wrote like below, and also tested by myself >> too. >>> >>> Don't need to create rel_ja.py, edit relplugins.gpr.py >> >> My ja.po can be applied without editing/creating any relationship >> codes. that's right ; ) >> # also no need for any DateDisplay files. sorry for making you debug... >> >> And, thanks for adding my file, and try to increase more translated >> phrases. >>> >>> Note, I added your first version on SVN (3.3.x, trunk): >>> >>> http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po >> >> I've also created my github repository for personal work. You can >> check the progress here: >> https://github.com/yanmar/gramps-translation-ja/ >> >> Regards, >> Keiichiro Yamamoto >> >> >> 2011/7/31 jerome <rom...@ya...> >>> >>> Hi Keiichiro, >>> >>> I wondering why you need to edit relplugins.gpr.py for having Japanese >>> translation ! >>> >>> There is maybe one possible issue with Date Display (see >>> DateHandler/_DateHandler.py): >>> re >>> LANG_TO_DISPLAY = { >>> 'C' : DateDisplayEn, >>> 'en' : DateDisplayEn, >>> 'English_United States' : DateDisplayEn, >>> 'zh_CN' : DateDisplay, >>> 'zh_TW' : DateDisplay, >>> 'zh_SG' : DateDisplay, >>> 'zh_HK' : DateDisplay, >>> 'ja_JP' : DateDisplay, >>> 'ko_KR' : DateDisplay, >>> 'nb_NO' : DateDisplay, >>> } >>> >>> but localized Relationships handlers are plugins, which are based on the >>> main class: class >>> RelationshipCalculator(Relationship.RelationshipCalculator) >>> >>> If they don't exist, Gramps uses main class (same as english). >>> >>> Anyway, these localized modules are using hardcoded translated >>> strings/methods, so as you want, you can also try to translate them with >>> addition of the "simple/common" ja.po for gramps interface (labels, menu, >>> tooltips, tips, entries on lists, etc ...). >>> >>> >>> Note, I added your first version on SVN (3.3.x, trunk): >>> >>> http://gramps.svn.sourceforge.net/viewvc/gramps/branches/maintenance/gramps33/po/ja.po >>> >>> Currently, it is disable (ignored by configure.in) and with all "fuzzy" >>> strings. If you have a better version, I can update the current one. >>> >>> >>> Regards, >>> Jérôme >>> >>> >>> --- En date de : Sam 30.7.11, yanmar <k.y...@gm...> a écrit : >>> >>>> De: yanmar <k.y...@gm...> >>>> Objet: Re: Let me join Gramps project (Japanese) >>>> À: gra...@li... >>>> Cc: "jerome" <rom...@ya...> >>>> Date: Samedi 30 juillet 2011, 15h27 >>>> Hi Jerome, >>>> >>>> I've checked the minimum condition for reflecting my PO >>>> translation, >>>> under branches/maintenance/gramps33. >>>> Don't need to create rel_ja.py, edit relplugins.gpr.py just >>>> for this purpose. >>>> >>>> All I have to do is below: >>>> --- >>>> 1. Add "ja" string to ALL_LINGUAS variable on >>>> configure.in: >>>> ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR >>>> pt_PT ru sv >>>> fi lt sk bg hr sl ca sq he uk ja" >>>> 2. Put po/ja.po (partly translated, and not all string is >>>> "fuzzy") >>>> 3. Execute ./autogen.sh, make, make install (as root >>>> depends on prefix) >>>> --- >>>> >>>> This makes ${prefix}/share/locale/ja/LC_MESSAGES/gramps.mo >>>> correctly. >>>> And, my Japanese translation is applied expectedly ; ) >>>> >>>>> Since there was some changes on locales management I >>>> >>>> could be wrong, but the last time I needed to test an other >>>> localized relationship handler, it seems to me that I forced >>>> the LANGUAGE variable! >>>> >>>> I've checked $LANGUAGE variable, but It was set "ja:en" - >>>> appears no influence. >>>> >>>> >>>> Regards, >>>> Keiichiro Yamamoto >>>> >>>> >>>> 2011/7/15 jerome <rom...@ya...>: >>>>> >>>>> Hi Keiichiro, >>>>> >>>>> >>>>> Since there was some changes on locales management I >>>> >>>> could be wrong, but the last time I needed to test an other >>>> localized relationship handler, it seems to me that I forced >>>> the LANGUAGE variable! >>>>> >>>>> >>>>> http://www.gnu.org/software/hello/manual/gettext/Locale-Environment-Variables.html >>>>> >>>>> http://www.gnu.org/software/hello/manual/gettext/The-LANGUAGE-variable.html#The-LANGUAGE-variable >>>>> >>>>> You are running sources with some modifications, maybe >>>> >>>> some settings will be naturally set with a standard >>>> installation ? >>>>>> >>>>>> If there's another proper way (without making >>>> >>>> relationship >>>>>> >>>>>> calculator, or >>>>>> how to properly create rel calculator), please >>>> >>>> guide me, >>>>>> >>>>>> thanks. >>>>> >>>>> For now, you have french strings and relations ! >>>>> If you understand french and japanese calculation is >>>> >>>> the same, you can translate the hard coded strings into your >>>> new rel_ja.py. >>>>> >>>>> But >>>>> >>>>> --- En date de : Jeu 14.7.11, yanmar <k.y...@gm...> >>>> >>>> a écrit : >>>>>> >>>>>> De: yanmar <k.y...@gm...> >>>>>> Objet: Re: Let me join Gramps project (Japanese) >>>>>> À: "jerome" <rom...@ya...> >>>>>> Cc: "Brian Matherly" <br...@gr...> >>>>>> Date: Jeudi 14 juillet 2011, 0h22 >>>>>> Hi Jerome, >>>>>> >>>>>> Thanks for your advise, I can reflect my >>>> >>>> translation. >>>>>> >>>>>> The point was relationship calculator. I've tried >>>> >>>> to add >>>>>> >>>>>> Japanese one. >>>>>> >>>>>> 1. LOCALEDIR is set on /usr/local/share/locale and >>>> >>>> there's >>>>>> >>>>>> gramps.mo file >>>>>> under ja/LC_MESSAGES. >>>>>> >>>>>> 2. But the message was not vanished: >>>>>> "No translation available for language 'ja'. >>>> >>>> Using >>>>>> >>>>>> 'english' instead." >>>>>> >>>>>> 3. I've greped the error on code, and fount the >>>> >>>> part on >>>>>> >>>>>> Relationship.py, >>>>>> get_relationship_calculator method. there's >>>> >>>> if-else >>>>>> >>>>>> checking of >>>>>> relationship calculator >>>>>> as the translation exists or not. >>>>>> >>>>>> 4. so, I've quickly added the ja module for >>>> >>>> recognition. >>>>>> >>>>>> # cd /usr/local/share/gramps/plugins/rel >>>>>> # cp rel_fr.py rel_ja.py # just copied, no >>>> >>>> editing >>>>>> >>>>>> # vi relplugins.gpr.py # and added below: >>>>>> --- >>>>>> # ja >>>>>> plg = newplugin() >>>>>> plg.id = 'relcalc_ja' >>>>>> plg.name = _("Japanese Relationship >>>> >>>> Calculator") >>>>>> >>>>>> plg.description = _("Calculates relationships >>>> >>>> between >>>>>> >>>>>> people") >>>>>> plg.version = '1.0' >>>>>> plg.gramps_target_version = '3.3' >>>>>> plg.status = STABLE >>>>>> plg.fname = 'rel_ja.py' >>>>>> plg.ptype = RELCALC >>>>>> plg.relcalcclass = 'RelationshipCalculator' >>>>>> plg.lang_list = ["ja", "JA", "ja_JP", >>>> >>>> "日本語", >>>>>> >>>>>> "Japanese", "ja_JP.UTF8", >>>>>> >>>>>> "ja_JP.UTF-8", "ja_JP.utf-8", >>>>>> "ja_JP.utf8"] >>>>>> --- >>>>>> >>>>>> If there's another proper way (without making >>>> >>>> relationship >>>>>> >>>>>> calculator, or >>>>>> how to properly create rel calculator), please >>>> >>>> guide me, >>>>>> >>>>>> thanks. >>>>>> >>>>>> Regards >>>>>> Keiichiro Yamamoto >>>>>> >>>>> >>>>> >> >> >> >> -- >> 山本慶一郎 >> k.y...@gm... >> > > |