Menu
▾
▴
Re: [Gramps-devel] Translation question
|
From: jerome <rom...@ya...> - 2010-11-16 15:40:42
|
Note, it is only (maybe also Narrative ?) for complete sentences on detailed reports, something "more written". Graphical and Draw reports have limited place.
> We would normally put the street before the city.
No problem, I was wondering when I needed to make an alternative translation for strings like : _('in %(city)s, %(street)s')
We will translate according our standard use, english is the model.
What about the separator between city and street (comma, dash, slash ?)
Jérôme
--- En date de : Mar 16.11.10, Doug Blank <dou...@gm...> a écrit :
> De: Doug Blank <dou...@gm...>
> Objet: Re: [Gramps-devel] Translation question
> À: "Nick Hall" <nic...@ho...>
> Cc: rom...@ya..., "Gramps developers" <gra...@li...>
> Date: Mardi 16 novembre 2010, 16h28
> I've been trying to follow the
> BetterGEDCOM discussion (which is hard
> because it is all over the place---literally all over their
> wiki, and
> also discusses all aspects of genealogy, from process to
> compressed
> file format protocols.)
>
> But, one suggestion I saw that was relevant to this issue
> was the idea
> of including the preposition word in the place record
> itself. Now, I
> think one would want to do something more sophisticated,
> such as a
> Place Type. This could the idea of "on" (as in ship), "in",
> "at", or
> custom. This would (perhaps) allow for better reading of
> text. But
> some languages (as shown above) would also need to know the
> gender.
> (One could this with attributes).
>
> However, perhaps just avoiding the preposition (say be
> using commas)
> is better and easier.
>
> How important is this issue to get right to people?
>
> -Doug
>
> On Tue, Nov 16, 2010 at 10:16 AM, Nick Hall <nic...@ho...>
> wrote:
> > 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
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> ------------------------------------------------------------------------------
> > Beautiful is writing same markup. Internet Explorer 9
> supports
> > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and
> DOM L2 & L3.
> > Spend less time writing and rewriting code and more
> time creating great
> > experiences on the web. Be a part of the beta today
> > http://p.sf.net/sfu/msIE9-sfdev2dev
> > _______________________________________________
> > Gramps-devel mailing list
> > Gra...@li...
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >
>
|