1
UPDATES / Translation update
« on: Yesterday at 21:19:14 »
v14 - Catalan translation update (thanks Jordi)
v14 - Castellan translation update (thanks Jordi)
v14 - Castellan translation update (thanks Jordi)
Select language :
News:
Tree sharing session 1st Saturdays of odd months to see if other users share a common ancestor with you!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
ENGLISH / Re: Canceling input for Source not working as expected
« on: April 08, 2026, 17:42:25 »
The log fils will be useless.
There is no error, we don't log every actions.
Zurga
There is no error, we don't log every actions.
Zurga
3
UPDATES / Translation update
« on: April 07, 2026, 07:40:55 »
v14 - Castellan translation update (thanks Jordi)
4
FRANÇAIS / Re: Export Geneanet ne respecte pas l'étiquette RESN ( résolu )
« on: April 06, 2026, 19:36:41 »
Mauvais réglage : vous excluez les propriétés RESN, pas les entités qui contiennent RESN.
C'est sur l'onglet "Filtrer par entités"
Zurga
C'est sur l'onglet "Filtrer par entités"
Zurga
5
UPDATES / Translation update
« on: April 06, 2026, 17:38:23 »
v14 - Portuguese translation update (thanks Pedro)
6
FRANÇAIS / Re: Export Geneanet ne respecte pas l'étiquette RESN ( résolu )
« on: April 06, 2026, 17:36:48 »
Si c'est possible.
Si vous mettez des critères qui exclut cette personne, elle ne sera pas dans le fichier envoyé.
Zurga
Si vous mettez des critères qui exclut cette personne, elle ne sera pas dans le fichier envoyé.
Zurga
7
FRANÇAIS / Re: Export Geneanet ne respecte pas l'étiquette RESN
« on: April 05, 2026, 19:29:59 »
Quelles sont les options que vous avez cochées au moment de la création de l'export ?
Je rappelle que RESN est une indication dans le GEDCOM pour indiquer au destinataire qu'il ne faut pas les diffuser.
Il n'oblige pas le programme émetteur à ne pas exporter les données.
Personnellement, j'ajoute dans les options d'export "Exclure tous les individus avec l'étiquette suivante" et je remplis avec "RESN"
Zurga
Je rappelle que RESN est une indication dans le GEDCOM pour indiquer au destinataire qu'il ne faut pas les diffuser.
Il n'oblige pas le programme émetteur à ne pas exporter les données.
Personnellement, j'ajoute dans les options d'export "Exclure tous les individus avec l'étiquette suivante" et je remplis avec "RESN"
Zurga
9
ENGLISH / Re: Canceling input for Source not working as expected
« on: April 03, 2026, 14:17:31 »Thank you very much for this fix. I would love to test it, but I can't because I'm using Ancestris 13.It's a good time to evolve and use the v14
Zurga
10
UPDATES / Aries Editor
« on: April 03, 2026, 07:46:06 »
v14 - Aries editor : adjustment in the undo sequence.
11
ENGLISH / Re: Changing WIFE to HUSB
« on: April 02, 2026, 15:43:46 »
And reciprocally, one of the female to be defined with a HUSB role.
This is understandable, however: the purpose of GEDCOM is to transmit genealogical data, most of which is much older than the last 25 years.
Zurga
This is understandable, however: the purpose of GEDCOM is to transmit genealogical data, most of which is much older than the last 25 years.
Zurga
12
ENGLISH / Re: Changing WIFE to HUSB
« on: April 02, 2026, 12:46:37 »
It is not possible.
GEDCOM structure doesn't allow to put 2 HUSB or 2 WIFE in a family structure.
You always have one defined as HUSB and the other as WIFE, even they are same-sex.
Zurga
GEDCOM structure doesn't allow to put 2 HUSB or 2 WIFE in a family structure.
You always have one defined as HUSB and the other as WIFE, even they are same-sex.
Zurga
13
ENGLISH / Re: Automated Entry of "Type" when selecting a "occupation"
« on: April 02, 2026, 08:59:35 »- For OCCU, the specification does not say, but it should continue to be a type of occupation, as for other attributes, and the description text should then be the full occupation as written in the official documents of that person. Let's say the person was "Soldier in the 5th infantery regiment of the French territory army", that is what the description should say, and the type could be then "Military".The specification gives the same TYPE for all attributes and all event.
Only one description to rule them all
Zurga
14
UPDATES / GEDCOM Conversion
« on: April 02, 2026, 07:59:00 »
v13/v14 - GEDCOM conversion : avoid error when role of association is the predefined keyword "Other".
15
ENGLISH / Re: Automated Entry of "Type" when selecting a "occupation"
« on: April 02, 2026, 07:56:42 »
Here is the exact definition in the GEDCOM specification :
EVENT_OR_FACT_CLASSIFICATION:= {Size=1:90}
A descriptive word or phrase used to further classify the parent event or attribute tag. This should be used whenever either of the generic EVEN or FACT tags are used. The value of this primative is responsible for classifying the generic event or fact being cited. For example, if the attribute being defined was one of the persons skills, such as woodworking, the FACT tag would have the value of `Woodworking', followed by a subordinate TYPE tag with the value `Skills.'
1 FACT Woodworking
2 TYPE Skills
This groups the fact into a generic skills attribute, and in particular this entry records the fact that this individual possessed the skill of woodworking. Using the subordinate TYPE tag classification method with any of the other defined event tags provides a further classification of the parent tag but does not change the basic meaning of the parent tag. For example, a MARR tag could be subordinated with a TYPE tag with an EVENT_DESCRIPTOR value of `Common Law.'
1 MARR
2 TYPE Common Law
This classifies the entry as a common law marriage but the event is still a marriage event. Other descriptor values might include, for example,`stillborn' as a qualifier to BIRTh or `Tribal Custom' as a qualifier to MARRiage.
So, yes, the TYPE is a higher classification of OCCU.
Zurga
EVENT_OR_FACT_CLASSIFICATION:= {Size=1:90}
A descriptive word or phrase used to further classify the parent event or attribute tag. This should be used whenever either of the generic EVEN or FACT tags are used. The value of this primative is responsible for classifying the generic event or fact being cited. For example, if the attribute being defined was one of the persons skills, such as woodworking, the FACT tag would have the value of `Woodworking', followed by a subordinate TYPE tag with the value `Skills.'
1 FACT Woodworking
2 TYPE Skills
This groups the fact into a generic skills attribute, and in particular this entry records the fact that this individual possessed the skill of woodworking. Using the subordinate TYPE tag classification method with any of the other defined event tags provides a further classification of the parent tag but does not change the basic meaning of the parent tag. For example, a MARR tag could be subordinated with a TYPE tag with an EVENT_DESCRIPTOR value of `Common Law.'
1 MARR
2 TYPE Common Law
This classifies the entry as a common law marriage but the event is still a marriage event. Other descriptor values might include, for example,`stillborn' as a qualifier to BIRTh or `Tribal Custom' as a qualifier to MARRiage.
So, yes, the TYPE is a higher classification of OCCU.
Zurga