From: Peter L. <pet...@te...> - 2010-10-31 13:29:55
|
Hi, I would like to test a suggestion in order to improve translation into Swedish and/or some more languages. There is a problem translating strings like: "He was born in %(birth_place)s." In English the preposition "in" is used, but in Swedish and maybe some in other languages, the preposition is different for different type of places. Example in Swedish: Han föddes i Stockholm. (He was born in Stockholm) Han föddes på Storgatan 32. (He was born in 32 Main Street) Using the wrong preposition gives a bad impression. So if we change the translation string to something like: "He was born %(prepo)s %(birth_place)s." and add a field to the place database/editor where the user can select correct preposition. So, the questions are: 1. Can this be done? 2. Is this a Swedish only problem? 3 Is it worth the effort? /Peter |
From: Peter L. <pet...@te...> - 2011-01-22 18:01:08
|
Hi! I have generated a new gramps-pot in order to check my translation of new filter. In the sv.po file I fhabe fund a singel "t" that waist to translated. It comed from: src:/../src/gui/viewmanager.py:463 which is: category = "%s %s" % (_(status), ngettext(plugin_dict["t"], How can this "t" show up in the gramps.pot/sv.po file? /Peter |
From: Josip <jo...@pi...> - 2011-01-22 20:29:07
|
On 22.01.2011 19:03, Peter Landgren wrote: > > I have generated a new gramps-pot in order to check my translation of new filter. > > In the sv.po file I fhabe fund a singel "t" that waist to translated. cd po make gramps.pot then: grep -e '\"t\"' gramps.pot found nothing (no single t) -- Josip |
From: Jérôme <rom...@ya...> - 2011-01-23 09:16:38
|
Hi Peter, > How can this "t" show up in the gramps.pot/sv.po file We can retrieve comment for the template (translators) by adding a comment on python code on the line before the translation string. # status and plugin count (t) category = "%s %s" % (_(status) + ngettext(plugin_dict["t"], Else I suppose there is still something like that: # status and plugin count (t) _('status') + ngettext("%(dict)d, "%(dict)d + "s", plugin_dict["t"]) % { 'dict' : plugin_dict["t"]} or from gen.ggettext import sngettext /not available/ # status and plugin count (t) _('status') + sngettext("%(t|dict)d, "%(t|dict)d + "s", plugin_dict["t"]) % {'dict' : plugin_dict["t"]} Agreed, the last are strange and untested. :-\ The comment before the translation string should work, but need to know what the "t" is ... Jérôme Peter Landgren a écrit : > Hi! > > I have generated a new gramps-pot in order to check my translation of new filter. > > In the sv.po file I fhabe fund a singel "t" that waist to translated. > It comed from: > src:/../src/gui/viewmanager.py:463 > which is: > category = "%s %s" % (_(status), ngettext(plugin_dict["t"], > > How can this "t" show up in the gramps.pot/sv.po file? > > /Peter > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2011-01-23 10:42:15
|
If I use make update-po or make gramps.pot I get this #: ../src/gui/viewmanager.py:463 msgid "t" msgid_plural "t" msgstr[0] "" msgstr[1] "" in gramps.pot /Peter > On 22.01.2011 19:03, Peter Landgren wrote: > > I have generated a new gramps-pot in order to check my translation of > > new filter. > > > > In the sv.po file I fhabe fund a singel "t" that waist to translated. > > cd po > make gramps.pot > > then: > grep -e '\"t\"' gramps.pot > found nothing (no single t) |
From: Josip <jo...@pi...> - 2011-01-23 16:48:00
|
On 23.01.2011 11:44, Peter Landgren wrote: > If I use > > make update-po > or > make gramps.pot > > I get this > #: ../src/gui/viewmanager.py:463 > msgid "t" > msgid_plural "t" > msgstr[0] "" > msgstr[1] "" > > in gramps.pot > $ make gramps.pot $ grep -He '\"t\"' *.po* sv.po:msgid "t" sv.po:msgid_plural "t" No 't' in gramps.pot and in any po files except sv.po Try removing it from your files and update again. -- Josip |
From: Peter L. <pet...@te...> - 2011-01-23 18:08:40
|
Den Sunday 23 January 2011 17.46.40 skrev Josip: > On 23.01.2011 11:44, Peter Landgren wrote: > > If I use > > > > make update-po > > or > > make gramps.pot > > > > I get this > > > > #: ../src/gui/viewmanager.py:463 > > > > msgid "t" > > msgid_plural "t" > > msgstr[0] "" > > msgstr[1] "" > > > > in gramps.pot > > $ make gramps.pot > $ grep -He '\"t\"' *.po* > sv.po:msgid "t" > sv.po:msgid_plural "t" > > No 't' in gramps.pot and in any po files except sv.po > Try removing it from your files and update again. make update-po and grep -He '\"t\"' *.po* gives bg.po:msgid "t" bg.po:msgid_plural "t" ca.po:msgid "t" ca.po:msgid_plural "t" cs.po:msgid "t" cs.po:msgid_plural "t" da.po:msgid "t" da.po:msgid_plural "t" de.po:msgid "t" de.po:msgid_plural "t" es.po:msgid "t" es.po:msgid_plural "t" fi.po:msgid "t" fi.po:msgid_plural "t" fr.po:msgid "t" fr.po:msgid_plural "t" gramps.pot:msgid "t" gramps.pot:msgid_plural "t" he.po:msgid "t" he.po:msgid_plural "t" hr.po:msgid "t" hr.po:msgid_plural "t" hu.po:msgid "t" hu.po:msgid_plural "t" it.po:msgid "t" it.po:msgid_plural "t" lt.po:msgid "t" lt.po:msgid_plural "t" nb.po:msgid "t" nb.po:msgid_plural "t" nl.po:msgid "t" nl.po:msgid_plural "t" nn.po:msgid "t" nn.po:msgid_plural "t" pl.po:msgid "t" pl.po:msgid_plural "t" pt_BR.po:msgid "t" pt_BR.po:msgid_plural "t" pt_PT.po:msgid "t" pt_PT.po:msgid_plural "t" ru.po:msgid "t" ru.po:msgid_plural "t" sk.po:msgid "t" sk.po:msgid_plural "t" sl.po:msgid "t" sl.po:msgid_plural "t" sq.po:msgid "t" sq.po:msgid_plural "t" sv.po:msgid "t" sv.po:msgid_plural "t" uk.po:msgid "t" uk.po:msgid_plural "t" zh_CN.po:msgid "t" zh_CN.po:msgid_plural "t" Note this is with trunk rev 16445. /Peter |
From: Josip <jo...@pi...> - 2011-01-23 18:42:47
|
On 23.01.2011 19:11, Peter Landgren wrote: >> >> $ make gramps.pot >> $ grep -He '\"t\"' *.po* >> sv.po:msgid "t" >> sv.po:msgid_plural "t" >> >> No 't' in gramps.pot and in any po files except sv.po >> Try removing it from your files and update again. > > make update-po > and > grep -He '\"t\"' *.po* > gives > bg.po:msgid "t" > bg.po:msgid_plural "t" > ca.po:msgid "t" > ca.po:msgid_plural "t" > cs.po:msgid "t" > cs.po:msgid_plural "t" > da.po:msgid "t" > da.po:msgid_plural "t" > de.po:msgid "t" > de.po:msgid_plural "t" > es.po:msgid "t" > es.po:msgid_plural "t" > fi.po:msgid "t" > fi.po:msgid_plural "t" > fr.po:msgid "t" > fr.po:msgid_plural "t" > gramps.pot:msgid "t" > gramps.pot:msgid_plural "t" > he.po:msgid "t" > he.po:msgid_plural "t" > hr.po:msgid "t" > hr.po:msgid_plural "t" > hu.po:msgid "t" > hu.po:msgid_plural "t" > it.po:msgid "t" > it.po:msgid_plural "t" > lt.po:msgid "t" > lt.po:msgid_plural "t" > nb.po:msgid "t" > nb.po:msgid_plural "t" > nl.po:msgid "t" > nl.po:msgid_plural "t" > nn.po:msgid "t" > nn.po:msgid_plural "t" > pl.po:msgid "t" > pl.po:msgid_plural "t" > pt_BR.po:msgid "t" > pt_BR.po:msgid_plural "t" > pt_PT.po:msgid "t" > pt_PT.po:msgid_plural "t" > ru.po:msgid "t" > ru.po:msgid_plural "t" > sk.po:msgid "t" > sk.po:msgid_plural "t" > sl.po:msgid "t" > sl.po:msgid_plural "t" > sq.po:msgid "t" > sq.po:msgid_plural "t" > sv.po:msgid "t" > sv.po:msgid_plural "t" > uk.po:msgid "t" > uk.po:msgid_plural "t" > zh_CN.po:msgid "t" > zh_CN.po:msgid_plural "t" > > Note this is with trunk rev 16445. > If i do make update-po 't' is cleared even form sv.po and grep don't return anything. r16445 is broken but do you try on clean and reconfigured before? -- Josip |
From: jerome <rom...@ya...> - 2011-01-23 19:27:08
|
'make update-po' will merge all gettext files with your created template (gramps.pot). The "t" should be present on your gramps.pot. Just try 'intltool-update -p' or 'make gramps.pot' on your po directory. Jérôme --- En date de : Dim 23.1.11, Peter Landgren <pet...@te...> a écrit : > De: Peter Landgren <pet...@te...> > Objet: Re: [Gramps-devel] Translation question > À: "Josip" <jo...@pi...> > Cc: gra...@li... > Date: Dimanche 23 janvier 2011, 19h11 > Den Sunday 23 January 2011 17.46.40 > skrev Josip: > > On 23.01.2011 11:44, Peter Landgren wrote: > > > If I use > > > > > > make update-po > > > or > > > make gramps.pot > > > > > > I get this > > > > > > #: > ../src/gui/viewmanager.py:463 > > > > > > msgid "t" > > > msgid_plural "t" > > > msgstr[0] "" > > > msgstr[1] "" > > > > > > in gramps.pot > > > > $ make gramps.pot > > $ grep -He '\"t\"' *.po* > > sv.po:msgid "t" > > sv.po:msgid_plural "t" > > > > No 't' in gramps.pot and in any po files except sv.po > > Try removing it from your files and update again. > > make update-po > and > grep -He '\"t\"' *.po* > gives > bg.po:msgid "t" > bg.po:msgid_plural "t" > ca.po:msgid "t" > ca.po:msgid_plural "t" > cs.po:msgid "t" > cs.po:msgid_plural "t" > da.po:msgid "t" > da.po:msgid_plural "t" > de.po:msgid "t" > de.po:msgid_plural "t" > es.po:msgid "t" > es.po:msgid_plural "t" > fi.po:msgid "t" > fi.po:msgid_plural "t" > fr.po:msgid "t" > fr.po:msgid_plural "t" > gramps.pot:msgid "t" > gramps.pot:msgid_plural "t" > he.po:msgid "t" > he.po:msgid_plural "t" > hr.po:msgid "t" > hr.po:msgid_plural "t" > hu.po:msgid "t" > hu.po:msgid_plural "t" > it.po:msgid "t" > it.po:msgid_plural "t" > lt.po:msgid "t" > lt.po:msgid_plural "t" > nb.po:msgid "t" > nb.po:msgid_plural "t" > nl.po:msgid "t" > nl.po:msgid_plural "t" > nn.po:msgid "t" > nn.po:msgid_plural "t" > pl.po:msgid "t" > pl.po:msgid_plural "t" > pt_BR.po:msgid "t" > pt_BR.po:msgid_plural "t" > pt_PT.po:msgid "t" > pt_PT.po:msgid_plural "t" > ru.po:msgid "t" > ru.po:msgid_plural "t" > sk.po:msgid "t" > sk.po:msgid_plural "t" > sl.po:msgid "t" > sl.po:msgid_plural "t" > sq.po:msgid "t" > sq.po:msgid_plural "t" > sv.po:msgid "t" > sv.po:msgid_plural "t" > uk.po:msgid "t" > uk.po:msgid_plural "t" > zh_CN.po:msgid "t" > zh_CN.po:msgid_plural "t" > > Note this is with trunk rev 16445. > > /Peter > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 > USD value)! > Finally, a world-class log management solution at an even > better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer > expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Jérôme <rom...@ya...> - 2010-10-31 13:47:51
|
Hi, > 1. Can this be done? To replace all "in" on translation strings, like: "He was born in %(birth_place)s." => "He was born %(prepo)s %(birth_place)s." Should be not so hard: plugins/lib/libnarrate.py Only on place or also on month ? "in month", "in place" ? > 2. Is this a Swedish only problem? French = English > 3 Is it worth the effort? Did you plan to write a finnish parser like for %(prepo)s ? Or it is only a substitution variable ? Note, this also means all these translation strings will be fuzzy. Peter Landgren a écrit : > Hi, > > I would like to test a suggestion in order to improve translation into Swedish and/or some more > languages. > > There is a problem translating strings like: > "He was born in %(birth_place)s." > > In English the preposition "in" is used, but in Swedish and maybe some in other languages, the > preposition is different for different type of places. > Example in Swedish: > Han föddes i Stockholm. (He was born in Stockholm) > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > Using the wrong preposition gives a bad impression. > > So if we change the translation string to something like: > "He was born %(prepo)s %(birth_place)s." > and add a field to the place database/editor where the user can select correct preposition. > > So, the questions are: > 1. Can this be done? > > 2. Is this a Swedish only problem? > > 3 Is it worth the effort? > > /Peter > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2010-10-31 14:03:54
|
> Hi, > > > 1. Can this be done? > > To replace all "in" on translation strings, like: > "He was born in %(birth_place)s." => "He was born %(prepo)s > %(birth_place)s." > > Should be not so hard: > plugins/lib/libnarrate.py > > Only on place or also on month ? > "in month", "in place" ? Month has always the same preposition "i": "Han föddes i april på Gotland" But if there is a complete date: "Han föddes 1999-09-09 i Stockholm". No preposition and that works now. > > 2. Is this a Swedish only problem? > > French = English OK. > > 3 Is it worth the effort? > > Did you plan to write a finnish parser like for %(prepo)s ? > Or it is only a substitution variable ? I think I leave Finnish out of my competence, even if I have Finnish ancestors 200 years ago. I imagine a substitution variable. > Note, this also means all these translation strings will be fuzzy. Yes, i know. /Peter > Peter Landgren a écrit : > > Hi, > > > > I would like to test a suggestion in order to improve translation into > > Swedish and/or some more languages. > > > > There is a problem translating strings like: > > "He was born in %(birth_place)s." > > > > In English the preposition "in" is used, but in Swedish and maybe some in > > other languages, the preposition is different for different type of > > places. > > Example in Swedish: > > Han föddes i Stockholm. (He was born in Stockholm) > > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > > > Using the wrong preposition gives a bad impression. > > > > So if we change the translation string to something like: > > "He was born %(prepo)s %(birth_place)s." > > and add a field to the place database/editor where the user can select > > correct preposition. > > > > So, the questions are: > > 1. Can this be done? > > > > 2. Is this a Swedish only problem? > > > > 3 Is it worth the effort? > > > > /Peter |
From: Stein E. B. <gr...@be...> - 2010-11-01 09:06:00
|
On Sun, 31 Oct 2010 15:05:28 +0100, Peter Landgren <pet...@te...> wrote: <snip /> > Month has always the same preposition "i": "Han föddes i april på > Gotland" > But if there is a complete date: "Han föddes 1999-09-09 i Stockholm". > No preposition and that works now. > >> > 2. Is this a Swedish only problem? >> >> French = English > OK. Norwegian and Danish have the same issue as found in Swedish. That's one of the inventions we have got in place to make sure that we can distinguish people who are not native speakers of our tongue, as I keep telling my girlfriend. :-) <snip /> Keep up the good work guys! -- Stein Erik Berget |
From: Nick H. <nic...@ho...> - 2010-10-31 20:06:28
|
Peter, I think we have the same problem with English: He was born in Stockholm He was born at 32 Main Street and a similar problem with dates: He was born in October 2010 He was born on 31st October 2010 For places we just use the place title for reports so we don't know the context. We could possibly use the street field in addition to the title to improve this. For dates we don't do the processing at the moment. Nick. Peter Landgren wrote: > Hi, > > I would like to test a suggestion in order to improve translation into Swedish and/or some more > languages. > > There is a problem translating strings like: > "He was born in %(birth_place)s." > > In English the preposition "in" is used, but in Swedish and maybe some in other languages, the > preposition is different for different type of places. > Example in Swedish: > Han föddes i Stockholm. (He was born in Stockholm) > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > Using the wrong preposition gives a bad impression. > > So if we change the translation string to something like: > "He was born %(prepo)s %(birth_place)s." > and add a field to the place database/editor where the user can select correct preposition. > > So, the questions are: > 1. Can this be done? > > 2. Is this a Swedish only problem? > > 3 Is it worth the effort? > > /Peter > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |
From: Benny M. <ben...@gm...> - 2010-10-31 23:06:37
|
2010/10/31 Nick Hall <nic...@ho...> > Peter, > > I think we have the same problem with English: > > He was born in Stockholm > He was born at 32 Main Street > > and a similar problem with dates: > > He was born in October 2010 > He was born on 31st October 2010 > > For places we just use the place title for reports so we don't know the > context. We could possibly use the street field in addition to the > title to improve this. > I believe this is all far too complicated. A project like Gramps should only go this way if we have examples in OSS how to do it (preferably by linguistics :-), or a base library we can call. You need to analyze the part after the prepo to know what it has to be. Gramps is not the kind of project that has people with the expertise to know how to do that. It is better to consider our reports a first draft that the user must improve for a final version, or to word things differently so the problem does not pose itself (eg "Birthplace: ...., Date: ...). If we write handlers for it, it must be done in utility code reports can reuse, and be very readable. I don't have high hopes however on readable code if we want to support several languages.. For dates we don't do the processing at the moment. > I believe some reports have a string for dates which only have months, and dates that have a day and a month. We should pull that in a utility function somehow, but the point is that a report is perfectly capable of making as many distinguishes for translation as deemed useful. Benny > > Nick. > > > Peter Landgren wrote: > > Hi, > > > > I would like to test a suggestion in order to improve translation into > Swedish and/or some more > > languages. > > > > There is a problem translating strings like: > > "He was born in %(birth_place)s." > > > > In English the preposition "in" is used, but in Swedish and maybe some in > other languages, the > > preposition is different for different type of places. > > Example in Swedish: > > Han föddes i Stockholm. (He was born in Stockholm) > > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > > > Using the wrong preposition gives a bad impression. > > > > So if we change the translation string to something like: > > "He was born %(prepo)s %(birth_place)s." > > and add a field to the place database/editor where the user can select > correct preposition. > > > > So, the questions are: > > 1. Can this be done? > > > > 2. Is this a Swedish only problem? > > > > 3 Is it worth the effort? > > > > /Peter > > > > > ------------------------------------------------------------------------------ > > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > > Create new apps & games for the Nokia N8 for consumers in U.S. and > Canada > > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > > http://p.sf.net/sfu/nokia-dev2dev > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2010-11-01 07:44:36
|
OK, I see it's more complicated than at a first glance. The verbose reports should be regarded as drafts, which need proof reading an adjustments. It was just a thought from my horizon... /Peter > 2010/10/31 Nick Hall <nic...@ho...> > > > Peter, > > > > I think we have the same problem with English: > > > > He was born in Stockholm > > He was born at 32 Main Street > > > > and a similar problem with dates: > > > > He was born in October 2010 > > He was born on 31st October 2010 > > > > For places we just use the place title for reports so we don't know the > > context. We could possibly use the street field in addition to the > > title to improve this. > > I believe this is all far too complicated. > A project like Gramps should only go this way if we have examples in OSS > how to do it (preferably by linguistics :-), or a base library we can > call. > > You need to analyze the part after the prepo to know what it has to be. > Gramps is not the kind of project that has people with the expertise to > know how to do that. > It is better to consider our reports a first draft that the user must > improve for a final version, or to word things differently so the problem > does not pose itself (eg "Birthplace: ...., Date: ...). > If we write handlers for it, it must be done in utility code reports can > reuse, and be very readable. I don't have high hopes however on readable > code if we want to support several languages.. > > For dates we don't do the processing at the moment. > > > I believe some reports have a string for dates which only have months, and > dates that have a day and a month. We should pull that in a utility > function somehow, but the point is that a report is perfectly capable of > making as many distinguishes for translation as deemed useful. > > Benny > > > Nick. > > > > Peter Landgren wrote: > > > Hi, > > > > > > I would like to test a suggestion in order to improve translation into > > > > Swedish and/or some more > > > > > languages. > > > > > > There is a problem translating strings like: > > > "He was born in %(birth_place)s." > > > > > > In English the preposition "in" is used, but in Swedish and maybe some > > > in > > > > other languages, the > > > > > preposition is different for different type of places. > > > Example in Swedish: > > > Han föddes i Stockholm. (He was born in Stockholm) > > > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > > > > > Using the wrong preposition gives a bad impression. > > > > > > So if we change the translation string to something like: > > > "He was born %(prepo)s %(birth_place)s." > > > and add a field to the place database/editor where the user can select > > > > correct preposition. > > > > > So, the questions are: > > > 1. Can this be done? > > > > > > 2. Is this a Swedish only problem? > > > > > > 3 Is it worth the effort? > > > > > > /Peter |
From: Jérôme <rom...@ya...> - 2010-11-01 09:05:07
|
Hello, For translation on "verbose" reports, which seems not perfect, can I propose the last commit for "2371:Make printing reports in different languages easier" [1] ? Current libtranslate is only used on Ancestor report (Ahnentafel Report), so why not to commit changes on detailed reports (DDR, DAR), this will finish this bug-report. It is practical for quickly and easily generating a report into an other language without knowing this language (ex: for distant cousins). Other textual reports do not need a lang selector because they do not have a lot of sentences: less translation strings or short name, date with place. Otherwise, maybe (if need) this librairie might be used on NarrativeWeb? Some users generate Narrative into differents languages: http://www.gramps-project.org/wiki/index.php?title=Howto:_Make_a_genealogy_website_with_GRAMPS#Multilingual_Web_Site [1] http://www.gramps-project.org/bugs/view.php?id=2371 Jérôme Peter Landgren a écrit : > OK, > > I see it's more complicated than at a first glance. > The verbose reports should be regarded as drafts, which need proof reading an adjustments. > > It was just a thought from my horizon... > > /Peter > > >> 2010/10/31 Nick Hall <nic...@ho...> >> >>> Peter, >>> >>> I think we have the same problem with English: >>> >>> He was born in Stockholm >>> He was born at 32 Main Street >>> >>> and a similar problem with dates: >>> >>> He was born in October 2010 >>> He was born on 31st October 2010 >>> >>> For places we just use the place title for reports so we don't know the >>> context. We could possibly use the street field in addition to the >>> title to improve this. >> I believe this is all far too complicated. >> A project like Gramps should only go this way if we have examples in OSS >> how to do it (preferably by linguistics :-), or a base library we can >> call. >> >> You need to analyze the part after the prepo to know what it has to be. >> Gramps is not the kind of project that has people with the expertise to >> know how to do that. >> It is better to consider our reports a first draft that the user must >> improve for a final version, or to word things differently so the problem >> does not pose itself (eg "Birthplace: ...., Date: ...). >> If we write handlers for it, it must be done in utility code reports can >> reuse, and be very readable. I don't have high hopes however on readable >> code if we want to support several languages.. >> >> For dates we don't do the processing at the moment. >> >> >> I believe some reports have a string for dates which only have months, and >> dates that have a day and a month. We should pull that in a utility >> function somehow, but the point is that a report is perfectly capable of >> making as many distinguishes for translation as deemed useful. >> >> Benny >> >>> Nick. >>> >>> Peter Landgren wrote: >>>> Hi, >>>> >>>> I would like to test a suggestion in order to improve translation into >>> Swedish and/or some more >>> >>>> languages. >>>> >>>> There is a problem translating strings like: >>>> "He was born in %(birth_place)s." >>>> >>>> In English the preposition "in" is used, but in Swedish and maybe some >>>> in >>> other languages, the >>> >>>> preposition is different for different type of places. >>>> Example in Swedish: >>>> Han föddes i Stockholm. (He was born in Stockholm) >>>> Han föddes på Storgatan 32. (He was born in 32 Main Street) >>>> >>>> Using the wrong preposition gives a bad impression. >>>> >>>> So if we change the translation string to something like: >>>> "He was born %(prepo)s %(birth_place)s." >>>> and add a field to the place database/editor where the user can select >>> correct preposition. >>> >>>> So, the questions are: >>>> 1. Can this be done? >>>> >>>> 2. Is this a Swedish only problem? >>>> >>>> 3 Is it worth the effort? >>>> >>>> /Peter > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2010-11-01 13:00:54
|
Benny Malengier wrote: > > > 2010/10/31 Nick Hall <nic...@ho... > <mailto:nic...@ho...>> > > Peter, > > I think we have the same problem with English: > > He was born in Stockholm > He was born at 32 Main Street > > and a similar problem with dates: > > He was born in October 2010 > He was born on 31st October 2010 > > For places we just use the place title for reports so we don't > know the > context. We could possibly use the street field in addition to the > title to improve this. > > > I believe this is all far too complicated. In English the logic is quite simple: If a date has a day part, then use "on", else use "in". If a location has a street part, then use "at", else use "in". Not 100% reliable but better than what we currently have. I don't know if this is applicable to other languages though. An example of a report that I use is the Complete Individual Report. This uses a hard-coded "is". It would be very easy to put an "if" statement in this report. > A project like Gramps should only go this way if we have examples in > OSS how to do it (preferably by linguistics :-), or a base library we > can call. > > You need to analyze the part after the prepo to know what it has to > be. Gramps is not the kind of project that has people with the > expertise to know how to do that. > It is better to consider our reports a first draft that the user must > improve for a final version, or to word things differently so the > problem does not pose itself (eg "Birthplace: ...., Date: ...). I like the idea of re-wording things so as not to try to construct complete sentences. > If we write handlers for it, it must be done in utility code reports > can reuse, and be very readable. I don't have high hopes however on > readable code if we want to support several languages.. Extending libnarrate.py would ensure that we were consistent between reports. > > For dates we don't do the processing at the moment. > > > I believe some reports have a string for dates which only have months, > and dates that have a day and a month. We should pull that in a > utility function somehow, but the point is that a report is perfectly > capable of making as many distinguishes for translation as deemed useful. Yes, it looks like different reports handle things in different ways. Nick. > > Benny > > > Nick. > > > Peter Landgren wrote: > > Hi, > > > > I would like to test a suggestion in order to improve > translation into Swedish and/or some more > > languages. > > > > There is a problem translating strings like: > > "He was born in %(birth_place)s." > > > > In English the preposition "in" is used, but in Swedish and > maybe some in other languages, the > > preposition is different for different type of places. > > Example in Swedish: > > Han föddes i Stockholm. (He was born in Stockholm) > > Han föddes på Storgatan 32. (He was born in 32 Main Street) > > > > Using the wrong preposition gives a bad impression. > > > > So if we change the translation string to something like: > > "He was born %(prepo)s %(birth_place)s." > > and add a field to the place database/editor where the user can > select correct preposition. > > > > So, the questions are: > > 1. Can this be done? > > > > 2. Is this a Swedish only problem? > > > > 3 Is it worth the effort? > > > > /Peter > > > > > ------------------------------------------------------------------------------ > > Nokia and AT&T present the 2010 Calling All Innovators-North > America contest > > Create new apps & games for the Nokia N8 for consumers in U.S. > and Canada > > $10 million total in prizes - $4M cash, 500 devices, nearly $6M > in marketing > > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to > Ovi Store > > http://p.sf.net/sfu/nokia-dev2dev > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > <mailto:Gra...@li...> > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North > America contest > Create new apps & games for the Nokia N8 for consumers in U.S. > and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi > Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > <mailto:Gra...@li...> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Jérôme <rom...@ya...> - 2010-11-01 15:18:37
|
Maybe I know why Peter has additionnal problem: he uses two forms on place name: "street, city/town" or "city/town". In this case, I suppose language can have a preposition issue. To avoid this, I set subdivision on the second position on my place names: city-subdivision, county, state, country. I commited to SVN the lang selector on Detailed reports. For playing with this feature, we need compiled translations. I used GRAMPSI18N environnement variable for testing and it works fine. http://www.gramps-project.org/wiki/index.php?title=Translating_GRAMPS#.24GRAMPSI18N Jérôme Nick Hall a écrit : > > Benny Malengier wrote: >> >> 2010/10/31 Nick Hall <nic...@ho... >> <mailto:nic...@ho...>> >> >> Peter, >> >> I think we have the same problem with English: >> >> He was born in Stockholm >> He was born at 32 Main Street >> >> and a similar problem with dates: >> >> He was born in October 2010 >> He was born on 31st October 2010 >> >> For places we just use the place title for reports so we don't >> know the >> context. We could possibly use the street field in addition to the >> title to improve this. >> >> >> I believe this is all far too complicated. > > In English the logic is quite simple: > > If a date has a day part, then use "on", else use "in". > If a location has a street part, then use "at", else use "in". > Not 100% reliable but better than what we currently have. > > I don't know if this is applicable to other languages though. > > An example of a report that I use is the Complete Individual Report. > This uses a hard-coded "is". It would be very easy to put an "if" > statement in this report. > > >> A project like Gramps should only go this way if we have examples in >> OSS how to do it (preferably by linguistics :-), or a base library we >> can call. >> >> You need to analyze the part after the prepo to know what it has to >> be. Gramps is not the kind of project that has people with the >> expertise to know how to do that. >> It is better to consider our reports a first draft that the user must >> improve for a final version, or to word things differently so the >> problem does not pose itself (eg "Birthplace: ...., Date: ...). > > I like the idea of re-wording things so as not to try to construct > complete sentences. > > >> If we write handlers for it, it must be done in utility code reports >> can reuse, and be very readable. I don't have high hopes however on >> readable code if we want to support several languages.. > > Extending libnarrate.py would ensure that we were consistent between > reports. > > >> For dates we don't do the processing at the moment. >> >> >> I believe some reports have a string for dates which only have months, >> and dates that have a day and a month. We should pull that in a >> utility function somehow, but the point is that a report is perfectly >> capable of making as many distinguishes for translation as deemed useful. > > Yes, it looks like different reports handle things in different ways. > > > Nick. > > >> Benny >> >> >> Nick. >> >> >> Peter Landgren wrote: >> > Hi, >> > >> > I would like to test a suggestion in order to improve >> translation into Swedish and/or some more >> > languages. >> > >> > There is a problem translating strings like: >> > "He was born in %(birth_place)s." >> > >> > In English the preposition "in" is used, but in Swedish and >> maybe some in other languages, the >> > preposition is different for different type of places. >> > Example in Swedish: >> > Han föddes i Stockholm. (He was born in Stockholm) >> > Han föddes på Storgatan 32. (He was born in 32 Main Street) >> > >> > Using the wrong preposition gives a bad impression. >> > >> > So if we change the translation string to something like: >> > "He was born %(prepo)s %(birth_place)s." >> > and add a field to the place database/editor where the user can >> select correct preposition. >> > >> > So, the questions are: >> > 1. Can this be done? >> > >> > 2. Is this a Swedish only problem? >> > >> > 3 Is it worth the effort? >> > >> > /Peter >> > >> > >> ------------------------------------------------------------------------------ >> > Nokia and AT&T present the 2010 Calling All Innovators-North >> America contest >> > Create new apps & games for the Nokia N8 for consumers in U.S. >> and Canada >> > $10 million total in prizes - $4M cash, 500 devices, nearly $6M >> in marketing >> > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to >> Ovi Store >> > http://p.sf.net/sfu/nokia-dev2dev >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> <mailto:Gra...@li...> >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> > >> > >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North >> America contest >> Create new apps & games for the Nokia N8 for consumers in U.S. >> and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >> Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> <mailto:Gra...@li...> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Jérôme <rom...@ya...> - 2010-11-01 09:43:40
|
Hi, For dates we currently have: %(full_date)s %(partial_date)s %(modified_date)s %(month_year)s + something like: %(event_date)s For place, we have: %(place)s + something like: %(event_place)s To extend this idea on place, means of lot of changes. > For places we just use the place title for reports so we don't know the > context. We could possibly use the street field in addition to the > title to improve this. As pointed out on user-mailing list, reports based on GraphViz use locations fields: if place: location = place.get_main_location() if location.get_city: birthplace = location.get_city() elif location.get_state: birthplace = location.get_state() elif location.get_country: birthplace = location.get_country() This makes sense on "graphical" reports but this might be hard to get the correct article for all fields (also for latin languages, which often use gender forms). But this is not available on other reports yet, right? OK, if available on textual reports, french preposition may also be wrong. > In English the preposition "in" is used, but in Swedish and maybe some in other languages, the > preposition is different for different type of places. > Example in Swedish: > Han föddes i Stockholm. (He was born in Stockholm) > Han föddes på Storgatan 32. (He was born in 32 Main Street) Peter, Do you have a current textual report, which needs to use "Han föddes på Storgatan 32" sentence ? Jérôme Nick Hall a écrit : > Peter, > > I think we have the same problem with English: > > He was born in Stockholm > He was born at 32 Main Street > > and a similar problem with dates: > > He was born in October 2010 > He was born on 31st October 2010 > > For places we just use the place title for reports so we don't know the > context. We could possibly use the street field in addition to the > title to improve this. > > For dates we don't do the processing at the moment. > > Nick. > > > Peter Landgren wrote: >> Hi, >> >> I would like to test a suggestion in order to improve translation into Swedish and/or some more >> languages. >> >> There is a problem translating strings like: >> "He was born in %(birth_place)s." >> >> In English the preposition "in" is used, but in Swedish and maybe some in other languages, the >> preposition is different for different type of places. >> Example in Swedish: >> Han föddes i Stockholm. (He was born in Stockholm) >> Han föddes på Storgatan 32. (He was born in 32 Main Street) >> >> Using the wrong preposition gives a bad impression. >> >> So if we change the translation string to something like: >> "He was born %(prepo)s %(birth_place)s." >> and add a field to the place database/editor where the user can select correct preposition. >> >> So, the questions are: >> 1. Can this be done? >> >> 2. Is this a Swedish only problem? >> >> 3 Is it worth the effort? >> >> /Peter >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> >> > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2010-11-01 09:44:43
|
2010/11/1 John Ralls <jr...@ce...> > > On Oct 31, 2010, at 4:06 PM, Benny Malengier wrote: > > > > 2010/10/31 Nick Hall <nic...@ho...> > >> Peter, >> >> I think we have the same problem with English: >> >> He was born in Stockholm >> He was born at 32 Main Street >> >> and a similar problem with dates: >> >> He was born in October 2010 >> He was born on 31st October 2010 >> >> For places we just use the place title for reports so we don't know the >> context. We could possibly use the street field in addition to the >> title to improve this. >> > > I believe this is all far too complicated. > A project like Gramps should only go this way if we have examples in OSS > how to do it (preferably by linguistics :-), or a base library we can call. > > You need to analyze the part after the prepo to know what it has to be. > Gramps is not the kind of project that has people with the expertise to know > how to do that. > It is better to consider our reports a first draft that the user must > improve for a final version, or to word things differently so the problem > does not pose itself (eg "Birthplace: ...., Date: ...). > If we write handlers for it, it must be done in utility code reports can > reuse, and be very readable. I don't have high hopes however on readable > code if we want to support several languages.. > > For dates we don't do the processing at the moment. >> > > I believe some reports have a string for dates which only have months, and > dates that have a day and a month. We should pull that in a utility function > somehow, but the point is that a report is perfectly capable of making as > many distinguishes for translation as deemed useful. > > > You're not competing with OSS. Gramps is the only serious OSS genealogy > program (sorry Tom Wetmore, if you're out > there). You're competing with programs like Family Tree Maker and Heredis. > > That's one way of looking at it. Personally I don't compete with anyone, and I think most OSS developers are like that. I have enough competition in my job to not need it in my free time. As with all complicated features, if a developer-user needs it, and he can make a good case and a nice implementation, it will be added. Benny > Regards, > John Ralls > > |
From: Jérôme <rom...@ya...> - 2010-11-14 15:42:13
|
Peter, Nick, We could have a wrong preposition when place name begins with an address like (street number), right ? Why not to make a simple test on textual reports (who use libnarrate) ? (NarrativeWeb ?) Something like: ph = event.get_place_handle() if ph and location.get_street and location.get_city: place = self._('in %(city)s, %(street)s') % { 'city' : location.get_city, 'street' : location.get_street } elif ph and location.get_street and not location.get_city: # on, at, på place = self._('on %(street)s') % {street: location.get_street} else: place = self.database.get_place_from_handle(ph).get_title() No major change, one bug fix (properly display preposition before the place on detailed and ancestor reports), two translation strings added. User just needs to set the correct location fields for displaying the right preposition. :) Should I try to add this on detailed reports ? Regards, Jérôme Jérôme a écrit : > Hi, > > > For dates we currently have: > > %(full_date)s > %(partial_date)s > %(modified_date)s > %(month_year)s > + something like: > %(event_date)s > > For place, we have: > %(place)s > + something like: > %(event_place)s > > To extend this idea on place, means of lot of changes. > >> For places we just use the place title for reports so we don't know >> the context. We could possibly use the street field in addition to >> the title to improve this. > > As pointed out on user-mailing list, reports based on GraphViz use > locations fields: > if place: > location = place.get_main_location() > if location.get_city: > birthplace = location.get_city() > elif location.get_state: > birthplace = location.get_state() > elif location.get_country: > birthplace = location.get_country() > > This makes sense on "graphical" reports but this might be hard to get > the correct article for all fields (also for latin languages, which > often use gender forms). But this is not available on other reports yet, > right? > > OK, if available on textual reports, french preposition may also be wrong. > >> In English the preposition "in" is used, but in Swedish and maybe some >> in other languages, the preposition is different for different type of >> places. >> Example in Swedish: >> Han föddes i Stockholm. (He was born in Stockholm) >> Han föddes på Storgatan 32. (He was born in 32 Main Street) > > Peter, > > Do you have a current textual report, which needs to use "Han föddes på > Storgatan 32" sentence ? > > > Jérôme > > > > > > > Nick Hall a écrit : >> Peter, >> >> I think we have the same problem with English: >> >> He was born in Stockholm >> He was born at 32 Main Street >> >> and a similar problem with dates: >> >> He was born in October 2010 >> He was born on 31st October 2010 >> >> For places we just use the place title for reports so we don't know >> the context. We could possibly use the street field in addition to >> the title to improve this. >> >> For dates we don't do the processing at the moment. >> >> Nick. >> >> >> Peter Landgren wrote: >>> Hi, >>> >>> I would like to test a suggestion in order to improve translation >>> into Swedish and/or some more languages. >>> >>> There is a problem translating strings like: >>> "He was born in %(birth_place)s." >>> >>> In English the preposition "in" is used, but in Swedish and maybe >>> some in other languages, the preposition is different for different >>> type of places. >>> Example in Swedish: >>> Han föddes i Stockholm. (He was born in Stockholm) >>> Han föddes på Storgatan 32. (He was born in 32 Main Street) >>> >>> Using the wrong preposition gives a bad impression. >>> >>> So if we change the translation string to something like: >>> "He was born %(prepo)s %(birth_place)s." >>> and add a field to the place database/editor where the user can >>> select correct preposition. >>> >>> So, the questions are: >>> 1. Can this be done? >>> >>> 2. Is this a Swedish only problem? >>> >>> 3 Is it worth the effort? >>> >>> /Peter >>> >>> ------------------------------------------------------------------------------ >>> >>> Nokia and AT&T present the 2010 Calling All Innovators-North America >>> contest >>> Create new apps & games for the Nokia N8 for consumers in U.S. and >>> Canada >>> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >>> marketing >>> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >>> Store http://p.sf.net/sfu/nokia-dev2dev >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >>> >>> >> >> ------------------------------------------------------------------------------ >> >> Nokia and AT&T present the 2010 Calling All Innovators-North America >> contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and >> Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >> Store http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > |
From: Peter L. <pet...@te...> - 2010-11-14 18:07:34
|
Jérôme, It's far more complicated, than just preposition for street addresses, for Swedish places. There are only two prepositions used, "i" and "på". Some examples: I'm could be born i Talken (name of village) på Hagen (name of farm) but i Nystuga (name of a neighbor farm) i Värmland (län), but if the län is Gotland it's på Gotland på Gotland (big island in the Baltic) i Visby (only city på Gotland) i Stockholm på Norrmalm (part of Stockholm) på Kungsgatan 23 i Adolf Fredrik (parish in Stockholm) på Skeppsholmen (another parish in Stockholm, but also an island) So, for Swedish it must be up to the user to proof read the reports in this respect. Well it's not easy with reports in PDF-format. Otherwise, we must supply a preposition for every place and all its parts, and that is too complicated, as it also might be different prepositions in different parts of Sweden, variation in dialects. /Peter > Peter, Nick, > > We could have a wrong preposition when place name begins with an address > like (street number), right ? > > Why not to make a simple test on textual reports (who use libnarrate) ? > (NarrativeWeb ?) > > Something like: > > ph = event.get_place_handle() > if ph and location.get_street and location.get_city: > place = self._('in %(city)s, %(street)s') % { > 'city' : location.get_city, > 'street' : location.get_street } > elif ph and location.get_street and not location.get_city: > # on, at, på > place = self._('on %(street)s') % {street: location.get_street} > else: > place = self.database.get_place_from_handle(ph).get_title() > > > No major change, one bug fix (properly display preposition before the > place on detailed and ancestor reports), two translation strings added. > User just needs to set the correct location fields for displaying the > right preposition. :) > > > Should I try to add this on detailed reports ? > > > Regards, > Jérôme > > Jérôme a écrit : > > Hi, > > > > > > For dates we currently have: > > > > %(full_date)s > > %(partial_date)s > > %(modified_date)s > > %(month_year)s > > + something like: > > %(event_date)s > > > > For place, we have: > > %(place)s > > + something like: > > %(event_place)s > > > > To extend this idea on place, means of lot of changes. > > > >> For places we just use the place title for reports so we don't know > >> the context. We could possibly use the street field in addition to > >> the title to improve this. > > > > As pointed out on user-mailing list, reports based on GraphViz use > > > > locations fields: > > if place: > > location = place.get_main_location() > > > > if location.get_city: > > birthplace = location.get_city() > > > > elif location.get_state: > > birthplace = location.get_state() > > > > elif location.get_country: > > birthplace = location.get_country() > > > > This makes sense on "graphical" reports but this might be hard to get > > the correct article for all fields (also for latin languages, which > > often use gender forms). But this is not available on other reports yet, > > right? > > > > OK, if available on textual reports, french preposition may also be > > wrong. > > > >> In English the preposition "in" is used, but in Swedish and maybe some > >> in other languages, the preposition is different for different type of > >> places. > >> Example in Swedish: > >> Han föddes i Stockholm. (He was born in Stockholm) > >> Han föddes på Storgatan 32. (He was born in 32 Main Street) > > > > Peter, > > > > Do you have a current textual report, which needs to use "Han föddes på > > Storgatan 32" sentence ? > > > > > > Jérôme > > > > Nick Hall a écrit : > >> Peter, > >> > >> I think we have the same problem with English: > >> > >> He was born in Stockholm > >> He was born at 32 Main Street > >> > >> and a similar problem with dates: > >> > >> He was born in October 2010 > >> He was born on 31st October 2010 > >> > >> For places we just use the place title for reports so we don't know > >> the context. We could possibly use the street field in addition to > >> the title to improve this. > >> > >> For dates we don't do the processing at the moment. > >> > >> Nick. > >> > >> Peter Landgren wrote: > >>> Hi, > >>> > >>> I would like to test a suggestion in order to improve translation > >>> into Swedish and/or some more languages. > >>> > >>> There is a problem translating strings like: > >>> "He was born in %(birth_place)s." > >>> > >>> In English the preposition "in" is used, but in Swedish and maybe > >>> some in other languages, the preposition is different for different > >>> type of places. > >>> Example in Swedish: > >>> Han föddes i Stockholm. (He was born in Stockholm) > >>> Han föddes på Storgatan 32. (He was born in 32 Main Street) > >>> > >>> Using the wrong preposition gives a bad impression. > >>> > >>> So if we change the translation string to something like: > >>> "He was born %(prepo)s %(birth_place)s." > >>> and add a field to the place database/editor where the user can > >>> select correct preposition. > >>> > >>> So, the questions are: > >>> 1. Can this be done? > >>> > >>> 2. Is this a Swedish only problem? > >>> > >>> 3 Is it worth the effort? > >>> > >>> /Peter > >>> > >>> ----------------------------------------------------------------------- > >>> ------- > >>> > >>> Nokia and AT&T present the 2010 Calling All Innovators-North America > >>> contest > >>> Create new apps & games for the Nokia N8 for consumers in U.S. and > >>> Canada > >>> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > >>> marketing > >>> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi > >>> Store http://p.sf.net/sfu/nokia-dev2dev > >>> _______________________________________________ > >>> Gramps-devel mailing list > >>> Gra...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > >> ------------------------------------------------------------------------ > >> ------ > >> > >> Nokia and AT&T present the 2010 Calling All Innovators-North America > >> contest > >> Create new apps & games for the Nokia N8 for consumers in U.S. and > >> Canada > >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > >> marketing > >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi > >> Store http://p.sf.net/sfu/nokia-dev2dev > >> _______________________________________________ > >> Gramps-devel mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Peter Landgren Talken Hagen 671 94 BRUNSKOG 0570-530 21 070-345 0964 pet...@te... Skype: pgl4820.2 |
From: jerome <rom...@ya...> - 2010-11-14 22:29:11
|
Is it not possible to use "(på/i) %(place)s" for translation ? In french, we need to play with the gender. Sometimes (often tips or tooltips) I need to use something like "certain(e)s" /sure/ or "intéressé(e)" /interested/, where (e) is the common female letter. Readers know that it is a general form, and the brain is often able to read the correct word in context. It is like to write with some "secondary letters" (not the school tests, sounds), or to read the sentence with one typo which cannot be identified ! Jérôme --- En date de : Dim 14.11.10, Peter Landgren <pet...@te...> a écrit : > De: Peter Landgren <pet...@te...> > Objet: Re: [Gramps-devel] Translation question > À: rom...@ya... > Cc: "Nick Hall" <nic...@ho...>, "Gramps developers" <gra...@li...> > Date: Dimanche 14 novembre 2010, 19h09 > Jérôme, > > It's far more complicated, than just preposition for street > addresses, for Swedish places. > There are only two prepositions used, "i" and "på". > Some examples: I'm could be born > i Talken (name of village) > på Hagen (name of farm) > but > i Nystuga (name of a neighbor farm) > > i Värmland (län), but if the län is Gotland it's på > Gotland > > på Gotland (big island in the Baltic) > i Visby (only city på Gotland) > > i Stockholm > på Norrmalm (part of Stockholm) > på Kungsgatan 23 > i Adolf Fredrik (parish in Stockholm) > på Skeppsholmen (another parish in Stockholm, but also an > island) > > So, for Swedish it must be up to the user to proof read the > reports in this respect. > Well it's not easy with reports in PDF-format. > > Otherwise, we must supply a preposition for every place and > all its parts, and that is too > complicated, as it also might be different prepositions in > different parts of Sweden, variation in > dialects. > > /Peter > > > > Peter, Nick, > > > > We could have a wrong preposition when place name > begins with an address > > like (street number), right ? > > > > Why not to make a simple test on textual reports (who > use libnarrate) ? > > (NarrativeWeb ?) > > > > Something like: > > > > ph = event.get_place_handle() > > if ph and location.get_street and location.get_city: > > place = self._('in %(city)s, > %(street)s') % { > > > 'city' : location.get_city, > > > 'street' : location.get_street } > > elif ph and location.get_street and not > location.get_city: > > # on, at, på > > place = self._('on %(street)s') % > {street: location.get_street} > > else: > > place = > self.database.get_place_from_handle(ph).get_title() > > > > > > No major change, one bug fix (properly display > preposition before the > > place on detailed and ancestor reports), two > translation strings added. > > User just needs to set the correct location fields for > displaying the > > right preposition. :) > > > > > > Should I try to add this on detailed reports ? > > > > > > Regards, > > Jérôme > > > > Jérôme a écrit : > > > Hi, > > > > > > > > > For dates we currently have: > > > > > > %(full_date)s > > > %(partial_date)s > > > %(modified_date)s > > > %(month_year)s > > > + something like: > > > %(event_date)s > > > > > > For place, we have: > > > %(place)s > > > + something like: > > > %(event_place)s > > > > > > To extend this idea on place, means of lot of > changes. > > > > > >> For places we just use the place title for > reports so we don't know > > >> the context. We could possibly use the > street field in addition to > > >> the title to improve this. > > > > > > As pointed out on user-mailing list, reports > based on GraphViz use > > > > > > locations fields: > > > > if place: > > > > location = > place.get_main_location() > > > > > > > > if > location.get_city: > > > > > birthplace = location.get_city() > > > > > > > > elif > location.get_state: > > > > > birthplace = location.get_state() > > > > > > > > elif > location.get_country: > > > > > birthplace = location.get_country() > > > > > > This makes sense on "graphical" reports but this > might be hard to get > > > the correct article for all fields (also for > latin languages, which > > > often use gender forms). But this is not > available on other reports yet, > > > right? > > > > > > OK, if available on textual reports, french > preposition may also be > > > wrong. > > > > > >> In English the preposition "in" is used, but > in Swedish and maybe some > > >> in other languages, the preposition is > different for different type of > > >> places. > > >> Example in Swedish: > > >> Han föddes i Stockholm. (He was born > in Stockholm) > > >> Han föddes på Storgatan 32. (He was born in > 32 Main Street) > > > > > > Peter, > > > > > > Do you have a current textual report, which needs > to use "Han föddes på > > > Storgatan 32" sentence ? > > > > > > > > > Jérôme > > > > > > Nick Hall a écrit : > > >> Peter, > > >> > > >> I think we have the same problem with > English: > > >> > > >> He was born in Stockholm > > >> He was born at 32 Main Street > > >> > > >> and a similar problem with dates: > > >> > > >> He was born in October 2010 > > >> He was born on 31st October 2010 > > >> > > >> For places we just use the place title for > reports so we don't know > > >> the context. We could possibly use the > street field in addition to > > >> the title to improve this. > > >> > > >> For dates we don't do the processing at the > moment. > > >> > > >> Nick. > > >> > > >> Peter Landgren wrote: > > >>> Hi, > > >>> > > >>> I would like to test a suggestion in > order to improve translation > > >>> into Swedish and/or some more languages. > > >>> > > >>> There is a problem translating strings > like: > > >>> "He was born in %(birth_place)s." > > >>> > > >>> In English the preposition "in" is used, > but in Swedish and maybe > > >>> some in other languages, the preposition > is different for different > > >>> type of places. > > >>> Example in Swedish: > > >>> Han föddes i Stockholm. (He was > born in Stockholm) > > >>> Han föddes på Storgatan 32. (He was > born in 32 Main Street) > > >>> > > >>> Using the wrong preposition gives a bad > impression. > > >>> > > >>> So if we change the translation string to > something like: > > >>> "He was born %(prepo)s %(birth_place)s." > > >>> and add a field to the place > database/editor where the user can > > >>> select correct preposition. > > >>> > > >>> So, the questions are: > > >>> 1. Can this be done? > > >>> > > >>> 2. Is this a Swedish only problem? > > >>> > > >>> 3 Is it worth the effort? > > >>> > > >>> /Peter > > >>> > > >>> > ----------------------------------------------------------------------- > > >>> ------- > > >>> > > >>> Nokia and AT&T present the 2010 > Calling All Innovators-North America > > >>> contest > > >>> Create new apps & games for the Nokia > N8 for consumers in U.S. and > > >>> Canada > > >>> $10 million total in prizes - $4M cash, > 500 devices, nearly $6M in > > >>> marketing > > >>> Develop with Nokia Qt SDK, Web Runtime, > or Java and Publish to Ovi > > >>> Store http://p.sf.net/sfu/nokia-dev2dev > > >>> > _______________________________________________ > > >>> Gramps-devel mailing list > > >>> Gra...@li... > > >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > >> > > >> > ------------------------------------------------------------------------ > > >> ------ > > >> > > >> Nokia and AT&T present the 2010 Calling > All Innovators-North America > > >> contest > > >> Create new apps & games for the Nokia N8 > for consumers in U.S. and > > >> Canada > > >> $10 million total in prizes - $4M cash, 500 > devices, nearly $6M in > > >> marketing > > >> Develop with Nokia Qt SDK, Web Runtime, or > Java and Publish to Ovi > > >> Store http://p.sf.net/sfu/nokia-dev2dev > > >> > _______________________________________________ > > >> Gramps-devel mailing list > > >> Gra...@li... > > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > -- > Peter Landgren > Talken Hagen > 671 94 BRUNSKOG > 0570-530 21 > 070-345 0964 > pet...@te... > Skype: pgl4820.2 > |
From: Peter L. <pet...@te...> - 2010-11-15 08:27:57
|
> Is it not possible to use "(på/i) %(place)s" for translation ? Yes, of course, but the the user must edit the resulting text. And it's easy to search for "i/på" and do the corrections. However, I think that the user is aware of the the text is a concept, which needs proof reading and corrections to tune up the language, There is no misunderstanding using the wrong preposition, just thats it sounds a little awkward. I think I will stick to using only "i" as it's the most common used word. > In french, we need to play with the gender. > Sometimes (often tips or tooltips) I need to use something like > "certain(e)s" /sure/ or "intéressé(e)" /interested/, where (e) is the > common female letter. I understand. I Swedish we have two genders, "neutrum" and "reale". (We also have male and female, but that's a few words only.) So we need to differentiate between: ett hus (one house) or huset (the house) en bil (one car) or bilen (the car) but I don't think I have run into such a situation in translating Gramps yet. > Readers know that it is a general form, and the brain is often able to read > the correct word in context. Correct, no misunderstanding. /Peter > It is like to write with some "secondary letters" (not the school tests, > sounds), or to read the sentence with one typo which cannot be identified > ! > > > Jérôme > > --- En date de : Dim 14.11.10, Peter Landgren <pet...@te...> a écrit : > > De: Peter Landgren <pet...@te...> > > Objet: Re: [Gramps-devel] Translation question > > À: rom...@ya... > > Cc: "Nick Hall" <nic...@ho...>, "Gramps developers" > > <gra...@li...> Date: Dimanche 14 novembre 2010, > > 19h09 > > Jérôme, > > > > It's far more complicated, than just preposition for street > > addresses, for Swedish places. > > There are only two prepositions used, "i" and "på". > > Some examples: I'm could be born > > i Talken (name of village) > > på Hagen (name of farm) > > but > > i Nystuga (name of a neighbor farm) > > > > i Värmland (län), but if the län is Gotland it's på > > Gotland > > > > på Gotland (big island in the Baltic) > > i Visby (only city på Gotland) > > > > i Stockholm > > på Norrmalm (part of Stockholm) > > på Kungsgatan 23 > > i Adolf Fredrik (parish in Stockholm) > > på Skeppsholmen (another parish in Stockholm, but also an > > island) > > > > So, for Swedish it must be up to the user to proof read the > > reports in this respect. > > Well it's not easy with reports in PDF-format. > > > > Otherwise, we must supply a preposition for every place and > > all its parts, and that is too > > complicated, as it also might be different prepositions in > > different parts of Sweden, variation in > > dialects. > > > > /Peter > > > > > Peter, Nick, > > > > > > We could have a wrong preposition when place name > > > > begins with an address > > > > > like (street number), right ? > > > > > > Why not to make a simple test on textual reports (who > > > > use libnarrate) ? > > > > > (NarrativeWeb ?) > > > > > > Something like: > > > > > > ph = event.get_place_handle() > > > > > > if ph and location.get_street and location.get_city: > > > place = self._('in %(city)s, > > > > %(street)s') % { > > > > > > > > > 'city' : location.get_city, > > > > > > > > > 'street' : location.get_street } > > > > > elif ph and location.get_street and not > > > > location.get_city: > > > # on, at, på > > > place = self._('on %(street)s') % > > > > {street: location.get_street} > > > > > else: > > > place = > > > > self.database.get_place_from_handle(ph).get_title() > > > > > No major change, one bug fix (properly display > > > > preposition before the > > > > > place on detailed and ancestor reports), two > > > > translation strings added. > > > > > User just needs to set the correct location fields for > > > > displaying the > > > > > right preposition. :) > > > > > > > > > Should I try to add this on detailed reports ? > > > > > > > > > Regards, > > > Jérôme > > > > > > Jérôme a écrit : > > > > Hi, > > > > > > > > > > > > For dates we currently have: > > > > > > > > %(full_date)s > > > > %(partial_date)s > > > > %(modified_date)s > > > > %(month_year)s > > > > + something like: > > > > %(event_date)s > > > > > > > > For place, we have: > > > > %(place)s > > > > + something like: > > > > %(event_place)s > > > > > > > > To extend this idea on place, means of lot of > > > > changes. > > > > > >> For places we just use the place title for > > > > reports so we don't know > > > > > >> the context. We could possibly use the > > > > street field in addition to > > > > > >> the title to improve this. > > > > > > > > As pointed out on user-mailing list, reports > > > > based on GraphViz use > > > > > > locations fields: > > > > > > > > if place: > > > > > > > > location = > > place.get_main_location() > > > > > > > > > > > > > > > > > > > > if > > > > location.get_city: > > > > > > > > > > birthplace = location.get_city() > > > > > > > > > > > > > > > > > > > > elif > > > > location.get_state: > > > > > > > > > > birthplace = location.get_state() > > > > > > > > > > > > > > > > > > > > elif > > > > location.get_country: > > > > > > > > > > birthplace = location.get_country() > > > > > > This makes sense on "graphical" reports but this > > > > might be hard to get > > > > > > the correct article for all fields (also for > > > > latin languages, which > > > > > > often use gender forms). But this is not > > > > available on other reports yet, > > > > > > right? > > > > > > > > OK, if available on textual reports, french > > > > preposition may also be > > > > > > wrong. > > > > > > > >> In English the preposition "in" is used, but > > > > in Swedish and maybe some > > > > > >> in other languages, the preposition is > > > > different for different type of > > > > > >> places. > > > >> Example in Swedish: > > > >> Han föddes i Stockholm. (He was born > > > > in Stockholm) > > > > > >> Han föddes på Storgatan 32. (He was born in > > > > 32 Main Street) > > > > > > Peter, > > > > > > > > Do you have a current textual report, which needs > > > > to use "Han föddes på > > > > > > Storgatan 32" sentence ? > > > > > > > > > > > > Jérôme > > > > > > > > Nick Hall a écrit : > > > >> Peter, > > > >> > > > >> I think we have the same problem with > > > > English: > > > >> He was born in Stockholm > > > >> He was born at 32 Main Street > > > >> > > > >> and a similar problem with dates: > > > >> > > > >> He was born in October 2010 > > > >> He was born on 31st October 2010 > > > >> > > > >> For places we just use the place title for > > > > reports so we don't know > > > > > >> the context. We could possibly use the > > > > street field in addition to > > > > > >> the title to improve this. > > > >> > > > >> For dates we don't do the processing at the > > > > moment. > > > > > >> Nick. > > > >> > > > >> Peter Landgren wrote: > > > >>> Hi, > > > >>> > > > >>> I would like to test a suggestion in > > > > order to improve translation > > > > > >>> into Swedish and/or some more languages. > > > >>> > > > >>> There is a problem translating strings > > > > like: > > > >>> "He was born in %(birth_place)s." > > > >>> > > > >>> In English the preposition "in" is used, > > > > but in Swedish and maybe > > > > > >>> some in other languages, the preposition > > > > is different for different > > > > > >>> type of places. > > > >>> Example in Swedish: > > > >>> Han föddes i Stockholm. (He was > > > > born in Stockholm) > > > > > >>> Han föddes på Storgatan 32. (He was > > > > born in 32 Main Street) > > > > > >>> Using the wrong preposition gives a bad > > > > impression. > > > > > >>> So if we change the translation string to > > > > something like: > > > >>> "He was born %(prepo)s %(birth_place)s." > > > >>> and add a field to the place > > > > database/editor where the user can > > > > > >>> select correct preposition. > > > >>> > > > >>> So, the questions are: > > > >>> 1. Can this be done? > > > >>> > > > >>> 2. Is this a Swedish only problem? > > > >>> > > > >>> 3 Is it worth the effort? > > > >>> > > > >>> /Peter > > > > ----------------------------------------------------------------------- > > > > > >>> ------- > > > >>> > > > >>> Nokia and AT&T present the 2010 > > > > Calling All Innovators-North America > > > > > >>> contest > > > >>> Create new apps & games for the Nokia > > > > N8 for consumers in U.S. and > > > > > >>> Canada > > > >>> $10 million total in prizes - $4M cash, > > > > 500 devices, nearly $6M in > > > > > >>> marketing > > > >>> Develop with Nokia Qt SDK, Web Runtime, > > > > or Java and Publish to Ovi > > > > > >>> Store http://p.sf.net/sfu/nokia-dev2dev > > > > _______________________________________________ > > > > > >>> Gramps-devel mailing list > > > >>> Gra...@li... > > > >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------ > > > > > >> ------ > > > >> > > > >> Nokia and AT&T present the 2010 Calling > > > > All Innovators-North America > > > > > >> contest > > > >> Create new apps & games for the Nokia N8 > > > > for consumers in U.S. and > > > > > >> Canada > > > >> $10 million total in prizes - $4M cash, 500 > > > > devices, nearly $6M in > > > > > >> marketing > > > >> Develop with Nokia Qt SDK, Web Runtime, or > > > > Java and Publish to Ovi > > > > > >> Store http://p.sf.net/sfu/nokia-dev2dev > > > > _______________________________________________ > > > > > >> Gramps-devel mailing list > > > >> Gra...@li... > > > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Nick H. <nic...@ho...> - 2010-11-16 15:16:13
|
Jerome, You could do something like that for English. If it is a precise location (street field present) use "at" else use "in". We would normally put the street before the city. Nick. Jérôme wrote: > Peter, Nick, > > We could have a wrong preposition when place name begins with an > address like (street number), right ? > > Why not to make a simple test on textual reports (who use libnarrate) > ? (NarrativeWeb ?) > > Something like: > > ph = event.get_place_handle() > if ph and location.get_street and location.get_city: > place = self._('in %(city)s, %(street)s') % { > 'city' : location.get_city, > 'street' : location.get_street } > elif ph and location.get_street and not location.get_city: > # on, at, på > place = self._('on %(street)s') % {street: location.get_street} > else: > place = self.database.get_place_from_handle(ph).get_title() > > > No major change, one bug fix (properly display preposition before the > place on detailed and ancestor reports), two translation strings added. > User just needs to set the correct location fields for displaying the > right preposition. :) > > > Should I try to add this on detailed reports ? > > > Regards, > Jérôme > > > Jérôme a écrit : >> Hi, >> >> >> For dates we currently have: >> >> %(full_date)s >> %(partial_date)s >> %(modified_date)s >> %(month_year)s >> + something like: >> %(event_date)s >> >> For place, we have: >> %(place)s >> + something like: >> %(event_place)s >> >> To extend this idea on place, means of lot of changes. >> >>> For places we just use the place title for reports so we don't know >>> the context. We could possibly use the street field in addition to >>> the title to improve this. >> >> As pointed out on user-mailing list, reports based on GraphViz use >> locations fields: >> if place: >> location = place.get_main_location() >> if location.get_city: >> birthplace = location.get_city() >> elif location.get_state: >> birthplace = location.get_state() >> elif location.get_country: >> birthplace = location.get_country() >> >> This makes sense on "graphical" reports but this might be hard to get >> the correct article for all fields (also for latin languages, which >> often use gender forms). But this is not available on other reports >> yet, right? >> >> OK, if available on textual reports, french preposition may also be >> wrong. >> >>> In English the preposition "in" is used, but in Swedish and maybe >>> some in other languages, the preposition is different for different >>> type of places. >>> Example in Swedish: >>> Han föddes i Stockholm. (He was born in Stockholm) >>> Han föddes på Storgatan 32. (He was born in 32 Main Street) >> >> Peter, >> >> Do you have a current textual report, which needs to use "Han föddes >> på Storgatan 32" sentence ? >> >> >> Jérôme >> >> >> >> >> >> >> Nick Hall a écrit : >>> Peter, >>> >>> I think we have the same problem with English: >>> >>> He was born in Stockholm >>> He was born at 32 Main Street >>> >>> and a similar problem with dates: >>> >>> He was born in October 2010 >>> He was born on 31st October 2010 >>> >>> For places we just use the place title for reports so we don't know >>> the context. We could possibly use the street field in addition to >>> the title to improve this. >>> >>> For dates we don't do the processing at the moment. >>> >>> Nick. >>> >>> >>> Peter Landgren wrote: >>>> Hi, >>>> >>>> I would like to test a suggestion in order to improve translation >>>> into Swedish and/or some more languages. >>>> >>>> There is a problem translating strings like: >>>> "He was born in %(birth_place)s." >>>> >>>> In English the preposition "in" is used, but in Swedish and maybe >>>> some in other languages, the preposition is different for different >>>> type of places. >>>> Example in Swedish: >>>> Han föddes i Stockholm. (He was born in Stockholm) >>>> Han föddes på Storgatan 32. (He was born in 32 Main Street) >>>> >>>> Using the wrong preposition gives a bad impression. >>>> >>>> So if we change the translation string to something like: >>>> "He was born %(prepo)s %(birth_place)s." >>>> and add a field to the place database/editor where the user can >>>> select correct preposition. >>>> >>>> So, the questions are: >>>> 1. Can this be done? >>>> >>>> 2. Is this a Swedish only problem? >>>> >>>> 3 Is it worth the effort? >>>> >>>> /Peter >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> Nokia and AT&T present the 2010 Calling All Innovators-North >>>> America contest >>>> Create new apps & games for the Nokia N8 for consumers in U.S. and >>>> Canada >>>> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >>>> marketing >>>> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >>>> Store http://p.sf.net/sfu/nokia-dev2dev >>>> _______________________________________________ >>>> Gramps-devel mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>>> >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Nokia and AT&T present the 2010 Calling All Innovators-North America >>> contest >>> Create new apps & games for the Nokia N8 for consumers in U.S. and >>> Canada >>> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >>> marketing >>> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >>> Store http://p.sf.net/sfu/nokia-dev2dev >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >> >> > > > |