Empty death event and alive status

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Empty death event and alive status

Hubert Toullec
Bonjour,

Personnes vivantes : j'ai constaté que le simple fait d'enregistrer un événement de type "Décès" ne suffit pas pour que Gramps considère que la personne ne fait plus partie des vivants. Il semble qu'il faille impérativement indiquer une date de décès valide, pas une date vide ou de type "texte". Bizarre !

D'une façon générale, est-il souhaitable de saisir un événement certain (naissance ou décès, par exemple), même si aucune information n'est disponible sur cet événement ?

Je ne trouve pas comment faire un filtre sur la rubrique "nom usuel". Est-ce possible ?

Merci pour vos réponses.


Hello,

Alive people : I have noted that the simple fact to record an event of type Death is not enough for Gramps to consider the person is no more alive. It seems it is necessary to indicate a valid date of death, not an empty one or a text one. Odd!
In a general way, is it desirable to enter an event one consider unquestionable (birth or death of a person, for example), even if no information is available on that event ?

I do not find how to make a filter on the field "Call name". Is this possible ?

Thank you for your answers.
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

Benny Malengier


2008/10/25 Hubert Toullec <[hidden email]>

Bonjour,

Personnes vivantes : j'ai constaté que le simple fait d'enregistrer un
événement de type "Décès" ne suffit pas pour que Gramps considère que la
personne ne fait plus partie des vivants. Il semble qu'il faille
impérativement indiquer une date de décès valide, pas une date vide ou de
type "texte". Bizarre !

You can always add a calculated date with the calc modifier, or an estimated date.
Eg: Est before 1900
indicating the death is estimated before 1900
You should normally be able to make valid estimated dates, and so fullfill the requirement of a death date.

Note that GRAMPS has a 'probably alive' function to determine who probably is death, but this is costly, adding estimated dates resolves it.
 


D'une façon générale, est-il souhaitable de saisir un événement certain
(naissance ou décès, par exemple), même si aucune information n'est
disponible sur cet événement ?

 

Je ne trouve pas comment faire un filtre sur la rubrique "nom usuel". Est-ce
possible ?

You are right. It would be easy to add this to the Person with <name> filter though. Please, do a feature request for this.

Technically, open file src/Filters/Rules/Person/_HasNameOf
add label for call name, then eg
  self.call = self.list[4]
and add a find on the call name as done for give name/family name...

Should somebody have time to quickly add this....

Benny


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

jerome
> You are right. It would be easy to add this to the Person with <name>
> filter though. Please, do a feature request for this.

I have seen some request or patch dealing with filter and name on
bug-report...

* 2446: New filter: by grouped-as name
http://www.gramps-project.org/bugs/view.php?id=2446

* 760: add regex in rules with <name>
  http://www.gramps-project.org/bugs/view.php?id=760

>> I do not find how to make a filter on the field "Call name".
> Should somebody have time to quickly add this....

I might try !




Benny Malengier a écrit :

>
>
> 2008/10/25 Hubert Toullec <[hidden email]
> <mailto:[hidden email]>>
>
>
>     Bonjour,
>
>     Personnes vivantes : j'ai constaté que le simple fait d'enregistrer un
>     événement de type "Décès" ne suffit pas pour que Gramps considère que la
>     personne ne fait plus partie des vivants. Il semble qu'il faille
>     impérativement indiquer une date de décès valide, pas une date vide
>     ou de
>     type "texte". Bizarre !
>
>
> You can always add a calculated date with the calc modifier, or an
> estimated date.
> Eg: Est before 1900
> indicating the death is estimated before 1900
> You should normally be able to make valid estimated dates, and so
> fullfill the requirement of a death date.
>
> Note that GRAMPS has a 'probably alive' function to determine who
> probably is death, but this is costly, adding estimated dates resolves it.
>  
>
>
>
>     D'une façon générale, est-il souhaitable de saisir un événement certain
>     (naissance ou décès, par exemple), même si aucune information n'est
>     disponible sur cet événement ?
>
>
>  
>
>
>     Je ne trouve pas comment faire un filtre sur la rubrique "nom
>     usuel". Est-ce
>     possible ?
>
>
> You are right. It would be easy to add this to the Person with <name>
> filter though. Please, do a feature request for this.
>
> Technically, open file src/Filters/Rules/Person/_HasNameOf
> add label for call name, then eg
>   self.call = self.list[4]
> and add a find on the call name as done for give name/family name...
>
> Should somebody have time to quickly add this....
>
> Benny
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gramps-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-users



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

jerome
In reply to this post by Benny Malengier
> Technically, open file src/Filters/Rules/Person/_HasNameOf
> add label for call name, then eg
>   self.call = self.list[4]
> and add a find on the call name as done for give name/family name...

Also, prefix and patronymic are missing (Réf. _SearchName.py)
Maybe because it is related to search (partial) name or they just was
added on name structure later !
Should we add them too ?


For fun, I amused myself to make a simple rule for finding individuals
with a call name ;)

Need to paste it on Filters/Rules/Person and to add few lines on
__init__.py if you want to use it :

   from _FamilyWithIncompleteEvent import FamilyWithIncompleteEvent
+ from _HasCallName import HasCallName
   from _HasAttribute import HasAttribute

editor_rule_list = [
     Everyone,
+   HasCallName,
     IsFemale,



Benny Malengier a écrit :

>
>
> 2008/10/25 Hubert Toullec <[hidden email]
> <mailto:[hidden email]>>
>
>
>     Bonjour,
>
>     Personnes vivantes : j'ai constaté que le simple fait d'enregistrer un
>     événement de type "Décès" ne suffit pas pour que Gramps considère que la
>     personne ne fait plus partie des vivants. Il semble qu'il faille
>     impérativement indiquer une date de décès valide, pas une date vide
>     ou de
>     type "texte". Bizarre !
>
>
> You can always add a calculated date with the calc modifier, or an
> estimated date.
> Eg: Est before 1900
> indicating the death is estimated before 1900
> You should normally be able to make valid estimated dates, and so
> fullfill the requirement of a death date.
>
> Note that GRAMPS has a 'probably alive' function to determine who
> probably is death, but this is costly, adding estimated dates resolves it.
>  
>
>
>
>     D'une façon générale, est-il souhaitable de saisir un événement certain
>     (naissance ou décès, par exemple), même si aucune information n'est
>     disponible sur cet événement ?
>
>
>  
>
>
>     Je ne trouve pas comment faire un filtre sur la rubrique "nom
>     usuel". Est-ce
>     possible ?
>
>
> You are right. It would be easy to add this to the Person with <name>
> filter though. Please, do a feature request for this.
>
> Technically, open file src/Filters/Rules/Person/_HasNameOf
> add label for call name, then eg
>   self.call = self.list[4]
> and add a find on the call name as done for give name/family name...
>
> Should somebody have time to quickly add this....
>
> Benny
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gramps-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-users

#
# Gramps - a GTK+/GNOME based genealogy program
#
# Copyright (C) 2008  Brian G. Matherly
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
#

#-------------------------------------------------------------------------
#
# Standard Python modules
#
#-------------------------------------------------------------------------
from gettext import gettext as _

#-------------------------------------------------------------------------
#
# GRAMPS modules
#
#-------------------------------------------------------------------------

from Filters.Rules import Rule

#-------------------------------------------------------------------------
#
# HasCallName
#
#-------------------------------------------------------------------------
class HasCallName(Rule):
    """Rule that checks for a person with a call name"""

    name        = _('People with call name')
    description = _("Matches people with call name")
    category    = _('General filters')
   
    def apply(self, db, person):
        for name in [person.get_primary_name()] + person.get_alternate_names() :
            if name.get_call_name():
                return True
            else:
                return False

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

jerome
In reply to this post by Benny Malengier
Benny,

> You are right. It would be easy to add this to the Person with <name>
> filter though. Please, do a feature request for this.
>
> Technically, open file src/Filters/Rules/Person/_HasNameOf
> add label for call name, then eg
>   self.call = self.list[4]
> and add a find on the call name as done for give name/family name...
>
> Should somebody have time to quickly add this....

Should be OK with patchs, but does english people like the label
"person|Title:" ?

I know that a context tag exists on last gettext version :
msgctxt.http://www.gnu.org/software/autoconf/manual/gettext/PO-Files.html
Maybe this could avoid such a string ? How coding for this context ?


Jérôme


Benny Malengier a écrit :

>
>
> 2008/10/25 Hubert Toullec <[hidden email]
> <mailto:[hidden email]>>
>
>
>     Bonjour,
>
>     Personnes vivantes : j'ai constaté que le simple fait d'enregistrer un
>     événement de type "Décès" ne suffit pas pour que Gramps considère que la
>     personne ne fait plus partie des vivants. Il semble qu'il faille
>     impérativement indiquer une date de décès valide, pas une date vide
>     ou de
>     type "texte". Bizarre !
>
>
> You can always add a calculated date with the calc modifier, or an
> estimated date.
> Eg: Est before 1900
> indicating the death is estimated before 1900
> You should normally be able to make valid estimated dates, and so
> fullfill the requirement of a death date.
>
> Note that GRAMPS has a 'probably alive' function to determine who
> probably is death, but this is costly, adding estimated dates resolves it.
>  
>
>
>
>     D'une façon générale, est-il souhaitable de saisir un événement certain
>     (naissance ou décès, par exemple), même si aucune information n'est
>     disponible sur cet événement ?
>
>
>  
>
>
>     Je ne trouve pas comment faire un filtre sur la rubrique "nom
>     usuel". Est-ce
>     possible ?
>
>
> You are right. It would be easy to add this to the Person with <name>
> filter though. Please, do a feature request for this.
>
> Technically, open file src/Filters/Rules/Person/_HasNameOf
> add label for call name, then eg
>   self.call = self.list[4]
> and add a find on the call name as done for give name/family name...
>
> Should somebody have time to quickly add this....
>
> Benny
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gramps-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-users

Index: _HasNameOf.py
===================================================================
--- _HasNameOf.py (révision 11213)
+++ _HasNameOf.py (copie de travail)
@@ -45,7 +45,10 @@
     labels      = [ _('Given name:'),
                     _('Family name:'),
                     _('Suffix:'),
-                    _('person|Title:')]
+                    _('person|Title:'),
+                    _('Prefix:'),
+                    _('Patronymic:'),
+                    _('Call Name:'),]
     name        = _('People with the <name>')
     description = _("Matches people with a specified (partial) name")
     category    = _('General filters')
@@ -55,6 +58,9 @@
         self.l = self.list[1]
         self.s = self.list[2]
         self.t = self.list[3]
+        self.p = self.list[4]
+        self.a = self.list[5]
+        self.c = self.list[6]
         for name in [person.get_primary_name()] + person.get_alternate_names():
             val = 1
             if self.f and name.get_first_name().upper().find(self.f.upper()) == -1:
@@ -65,6 +71,12 @@
                 val = 0
             if self.t and name.get_title().upper().find(self.t.upper()) == -1:
                 val = 0
+            if self.p and name.get_prefix().upper().find(self.p.upper()) == -1:
+                val = 0
+            if self.a and name.get_patronymic().upper().find(self.a.upper()) == -1:
+                val = 0
+            if self.c and name.get_call_name().upper().find(self.c.upper()) == -1:
+                val = 0
             if val == 1:
                 return True
         return False

Index: _SearchName.py
===================================================================
--- _SearchName.py (révision 11213)
+++ _SearchName.py (copie de travail)
@@ -53,7 +53,7 @@
 
         for name in [person.get_primary_name()] + person.get_alternate_names():
             for field in [name.first_name, name.surname, name.suffix, name.title,
-                          name.prefix, name.patronymic]:
+                          name.prefix, name.patronymic, name.call_name]:
                 if src and field.upper().find(src) != -1:
                     return True
         else:

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

Benny Malengier


2008/10/29 Jérôme <[hidden email]>
Benny,


You are right. It would be easy to add this to the Person with <name> filter though. Please, do a feature request for this.

Technically, open file src/Filters/Rules/Person/_HasNameOf
add label for call name, then eg
 self.call = self.list[4]
and add a find on the call name as done for give name/family name...

Should somebody have time to quickly add this....

Should be OK with patchs, but does english people like the label "person|Title:" ?

The English persion does not see person|Title, he sees Title
The person| part is for translators so they know it is not a book title, but a title given to a person. 
Well, if sgettext from TransUtils is used instead of gettext (which it should in GRAMPS).

The patch looks ok. I do not like the variables as self.c, self.p, ... I would rather see self.calln and self.patr. As your class inherits from another class, using too short variables can create clashes if everybody starts to code like that. Just to let you know, I understand you patched the rule based on the coding style already present.



I know that a context tag exists on last gettext version :
msgctxt.http://www.gnu.org/software/autoconf/manual/gettext/PO-Files.html
Maybe this could avoid such a string ? How coding for this context ?

If you can figure out how to define context from within python to use this  msgctxt  field, please inform us.
It should be as simple to use as now, so instead of
_('person|Title:')
perhaps
_('Title:', person)
However, I don't see context mentioned here: http://www.python.org/doc/2.5.2/lib/node731.html

Benny


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

jerome
> The English persion does not see person|Title, he sees Title
> The person| part is for translators so they know it is not a book title,
> but a title given to a person.

I tried $ python gramps.py
(ignoring my locale !)

and I have seen person|Title on filter : people with <name> ...



Benny Malengier a écrit :

>
>
> 2008/10/29 Jérôme <[hidden email] <mailto:[hidden email]>>
>
>     Benny,
>
>
>         You are right. It would be easy to add this to the Person with
>         <name> filter though. Please, do a feature request for this.
>
>         Technically, open file src/Filters/Rules/Person/_HasNameOf
>         add label for call name, then eg
>          self.call = self.list[4]
>         and add a find on the call name as done for give name/family name...
>
>         Should somebody have time to quickly add this....
>
>
>     Should be OK with patchs, but does english people like the label
>     "person|Title:" ?
>
>
> The English persion does not see person|Title, he sees Title
> The person| part is for translators so they know it is not a book title,
> but a title given to a person.
> Well, if sgettext from TransUtils is used instead of gettext (which it
> should in GRAMPS).
>
> The patch looks ok. I do not like the variables as self.c, self.p, ... I
> would rather see self.calln and self.patr. As your class inherits from
> another class, using too short variables can create clashes if everybody
> starts to code like that. Just to let you know, I understand you patched
> the rule based on the coding style already present.
>
>
>
>     I know that a context tag exists on last gettext version :
>     msgctxt.http://www.gnu.org/software/autoconf/manual/gettext/PO-Files.html
>     Maybe this could avoid such a string ? How coding for this context ?
>
>
> If you can figure out how to define context from within python to use
> this  msgctxt  field, please inform us.
> It should be as simple to use as now, so instead of
> _('person|Title:')
> perhaps
> _('Title:', person)
> However, I don't see context mentioned here:
> http://www.python.org/doc/2.5.2/lib/node731.html
>
> Benny
>



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

Benny Malengier
Yes, I see the error.

Change in _HasNameof :

from gettext import gettext as _

into

from TransUtils import sgettext as _

The above should be used everywhere where context is used, otherwise it is a bug.

You do this?

Benny

2008/10/29 Jérôme <[hidden email]>
The English persion does not see person|Title, he sees Title
The person| part is for translators so they know it is not a book title, but a title given to a person.

I tried $ python gramps.py
(ignoring my locale !)

and I have seen person|Title on filter : people with <name> ...



Benny Malengier a écrit :


2008/10/29 Jérôme <[hidden email] <mailto:[hidden email]>>


   Benny,


       You are right. It would be easy to add this to the Person with
       <name> filter though. Please, do a feature request for this.

       Technically, open file src/Filters/Rules/Person/_HasNameOf
       add label for call name, then eg
        self.call = self.list[4]
       and add a find on the call name as done for give name/family name...

       Should somebody have time to quickly add this....


   Should be OK with patchs, but does english people like the label
   "person|Title:" ?


The English persion does not see person|Title, he sees Title
The person| part is for translators so they know it is not a book title, but a title given to a person. Well, if sgettext from TransUtils is used instead of gettext (which it should in GRAMPS).

The patch looks ok. I do not like the variables as self.c, self.p, ... I would rather see self.calln and self.patr. As your class inherits from another class, using too short variables can create clashes if everybody starts to code like that. Just to let you know, I understand you patched the rule based on the coding style already present.



   I know that a context tag exists on last gettext version :
   msgctxt.http://www.gnu.org/software/autoconf/manual/gettext/PO-Files.html
   Maybe this could avoid such a string ? How coding for this context ?


If you can figure out how to define context from within python to use this  msgctxt  field, please inform us.
It should be as simple to use as now, so instead of
_('person|Title:')
perhaps
_('Title:', person)
However, I don't see context mentioned here: http://www.python.org/doc/2.5.2/lib/node731.html

Benny





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|

Re: Empty death event and alive status

jerome
> You do this?

done,
http://gramps.svn.sourceforge.net/viewvc/gramps?view=rev&revision=11218
http://gramps.svn.sourceforge.net/viewvc/gramps?view=rev&revision=11219

> I would rather see self.calln and self.patr. As your class inherits from another class, using too short variables can create clashes if everybody starts to code like that.

I will do changes this week. I would like to see if to rename existing
class does not introduce other errors !



Benny Malengier a écrit :

> Yes, I see the error.
>
> Change in _HasNameof :
>
> from gettext import gettext as _
>
> into
>
> from TransUtils import sgettext as _
>
> The above should be used everywhere where context is used, otherwise it
> is a bug.
>
> You do this?
>
> Benny
>
> 2008/10/29 Jérôme <[hidden email] <mailto:[hidden email]>>
>
>         The English persion does not see person|Title, he sees Title
>         The person| part is for translators so they know it is not a
>         book title, but a title given to a person.
>
>
>     I tried $ python gramps.py
>     (ignoring my locale !)
>
>     and I have seen person|Title on filter : people with <name> ...
>
>
>
>     Benny Malengier a écrit :
>
>
>
>         2008/10/29 Jérôme <[hidden email]
>         <mailto:[hidden email]> <mailto:[hidden email]
>         <mailto:[hidden email]>>>
>
>
>            Benny,
>
>
>                You are right. It would be easy to add this to the Person
>         with
>                <name> filter though. Please, do a feature request for this.
>
>                Technically, open file src/Filters/Rules/Person/_HasNameOf
>                add label for call name, then eg
>                 self.call = self.list[4]
>                and add a find on the call name as done for give
>         name/family name...
>
>                Should somebody have time to quickly add this....
>
>
>            Should be OK with patchs, but does english people like the label
>            "person|Title:" ?
>
>
>         The English persion does not see person|Title, he sees Title
>         The person| part is for translators so they know it is not a
>         book title, but a title given to a person. Well, if sgettext
>         from TransUtils is used instead of gettext (which it should in
>         GRAMPS).
>
>         The patch looks ok. I do not like the variables as self.c,
>         self.p, ... I would rather see self.calln and self.patr. As your
>         class inherits from another class, using too short variables can
>         create clashes if everybody starts to code like that. Just to
>         let you know, I understand you patched the rule based on the
>         coding style already present.
>
>
>
>            I know that a context tag exists on last gettext version :
>          
>          msgctxt.http://www.gnu.org/software/autoconf/manual/gettext/PO-Files.html
>            Maybe this could avoid such a string ? How coding for this
>         context ?
>
>
>         If you can figure out how to define context from within python
>         to use this  msgctxt  field, please inform us.
>         It should be as simple to use as now, so instead of
>         _('person|Title:')
>         perhaps
>         _('Title:', person)
>         However, I don't see context mentioned here:
>         http://www.python.org/doc/2.5.2/lib/node731.html
>
>         Benny
>
>
>
>



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users