Ancestris - Forum

Ancestris Support => ENGLISH => Topic started by: mother10 on August 06, 2023, 14:08:51

Title: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 06, 2023, 14:08:51
Hello Everyone / Hallo Allemaal,

(Topic will contain some Dutch text for the Dutch readers)

On special request by Zurga in the French Forum, topic: https://forum.ancestris.org/index.php?topic=4402.msg13351#msg13351 (https://forum.ancestris.org/index.php?topic=4402.msg13351#msg13351) I opened a topic here in the English Forum about the same subject.

Original Topic title: "Rapport Lignée narrative d'ascendance ou de descendance"
In English: "Narrative lineage of ascendants or descendants"
en in het Nederlands: "Verhalende afstamming van voorouders of nakomelingen".

A lot of work has been done recently to get the text in this French report as precise as possible.

Now this topic is meant to do the same for this report in English and in Dutch.

In the English Ancestris, this report is reached from "Tools/Lists and Reports", then choose: "Lineage/Narrative lineage .....".
After choosing the first person, you can start the report.

In de Nederlandse Ancestris krijgt U het rapport via "Gereedschap/Lijsten en rapporten", en daarna kiest U "Afkomst/Verhalende afstamming...".
Na het kiezen van een Begin-persoon, kunt u het rapport starten.


I created the same report kennedy example in French, English and Dutch. And put them side by side.
Unfortunately max screenshot size for upload is 256K so might be more dificult to see now than the original

Differences: Yellow accented areas:

Topmost 1 in French: Just the brackets and **. The English version has [S2] and below that [: ** Text : .], The Dutch version has "Bron" (Source) between []

Second yellow areas, near the sources part.  The French version has the contents of the sources??; The English version just has the SourceNr, no contents. The Dutch version only has the word "Bron" (which is Sources) no contents and no nr.

In Pink: Why do all lines start with a Capital, even inside what is in fact 1 sentence.

In Green in the Dutch version: Untranslated words (Dont seem to appear in Trancestris either)

In Blue: Dutch version only: Each line of what is in fact 1 Note, starts with the word "Notitie" (Note)

Red arrows in English and Dutch version: Markings that dont appear in the French version.

Blue arrow, Dutch version, but is also the fact in the other languages: This is just 1 Note, so why does it say Notes (plurial)

Thats it for now.

Regards,
Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 06, 2023, 17:36:07
Normally, each text is in Transcestris bundle for ReportNarrative.

The "* Notes :" is "phrase.note.header", if not translated, you got the English version.

In dutch, the translation of "phrase.note" is "Notitie: [1].", in French "[1]", in English " [1]"
I suggest to change it to "[1]"

I will check for the contents of sources, we should have the same in any language.
As far As I can see, you don't have used the same version for the french report and the English one (space between children list, text alignment)

Zurga
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 06, 2023, 17:46:45
For the differences between the source management, il French, you haven't asked for the list of sources, so the details of each source is printed directly.
For the English and Dutch version, you have the list of Source. Then the source is printed after individual with only the Number of Source.

The Source "S2" in Kennedy genealogy as no title and no text, so this appears with very limited text in the report.

Zurga
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 06, 2023, 18:15:37
The best way is to run the report against her/his own genealogy gedcom file. But, be aware that sometimes the result is not as expected, but that's not the report fault, but our own fault. ;-) I saw some errors in my genealogy, because of the result seen when I ran that report. Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 16, 2023, 15:01:05
Hello all,

Here some things I noticed when creating this report from 1 and the same Gedcom, namely the latest Kennedy Gedcom.
(will test later with my own, but because of all translations that tree is still in the import fase, so that will only be ready for test, many weeks maybe months later, sorry)

If things are caused by translation errors, please tell me what variable has to change in Trancestris.

Note with Patrick Kennedy (I121) contains many lines, but those lines are in fact split here and there in the middle of a sentence.
French and English report: Each line of the note starts with a Capital, even in the middle of a sentence.
Dutch report: Each line starts with "Notitie:", followed by a space, followed by the text of only 1 line of the note itself.

First picture:
Yellow: Capitals, some are in the middle of a sentence. In the Dutch version no capitals, but, in orange, an unnecessary text "Notitie:" before each line of the note.
Top of the picture: the Gedcom of the note. (Contains CONT ?? or should that be CONC, if so the Kennedy gedcom should be changed and maybe the Bourbon also)

Why are there periods added at the end of each noteline in Dutch? (with 1 separating unnessesary space)

--------------------
With the same parameters, asking for places and names list, in French we get the sequence: Places (lieux) followed by Names (noms). In English we get: Names followed by places. In Dutch we get Names followed by Places.
Why the difference in sequence. It does not matter much, but I just wonder why.

--------------------
When a couple has no known children, the English says "No child known". I would have said: "No known children". (So plurial and other sequnce of the words)
Anyone know what it should be?

----------------------

Index on lastnames:
When there are pointers to pages for the lastname only (without a firstname), the number of periods is too less. So the pagenumbers dont align to the right.
Pointers to pages for Firstnames are correctly aligned to the right.

---------------------------
Placename index, see screenshot.
Why that many spaces in between in the first yellow area?

----------------------------
The footnotes are great. But why do the numbers keep getting higher?
Why dont they start with one on every new page?
Now, when you have many people and many notes, you might get very long numbers,

Could the notes in the text itself be printed bold?
Near the bottom of the page they are not bold, thats ok. But maybe to better stand out, have them in bold on the page itself.

----------------------------

I have a person born in 1955. Max age is set to 120. Report says he was driver. So as if he is dead already. But there is no death mentioned, nor a burial or something.
So I think that should have been "He is driver"

Another one born in 1984. There it says he lived in Someplace, so the past, but he is programmer, so present.
Why this difference for 1 and the same person?

-----------------------------
For children it says: "child of" wouldnt it be nicer if it said "son of", or "daughter of".



Thats it for now.

Regards,
Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 16, 2023, 18:47:44
I try to give you the best answer I can :
Note with Patrick Kennedy (I121) contains many lines, but those lines are in fact split here and there in the middle of a sentence.
French and English report: Each line of the note starts with a Capital, even in the middle of a sentence.
Dutch report: Each line starts with "Notitie:", followed by a space, followed by the text of only 1 line of the note itself.

First picture:
Yellow: Capitals, some are in the middle of a sentence. In the Dutch version no capitals, but, in orange, an unnecessary text "Notitie:" before each line of the note.
Top of the picture: the Gedcom of the note. (Contains CONT ?? or should that be CONC, if so the Kennedy gedcom should be changed and maybe the Bourbon also)

Why are there periods added at the end of each noteline in Dutch? (with 1 separating unnessesary space)
I have done nothing for the capitalization of the line.
The way the note is displayed will be changed tomorrow, I thing this will correct the capitalization
For the text ("Notitie :") and the period, the labels have been changed in French and English. This text is in the label in Dutch (phrase.note.header and phrase.note)
I can adjust the period and the labels in Dutch to be in-line with the English version.
--------------------
With the same parameters, asking for places and names list, in French we get the sequence: Places (lieux) followed by Names (noms). In English we get: Names followed by places. In Dutch we get Names followed by Places.
Why the difference in sequence. It does not matter much, but I just wonder why.
Alphabetic order.
The index are put automatically with the alphabetic order of the title.
I can try to choose a specific order if you prefer.
--------------------
When a couple has no known children, the English says "No child known". I would have said: "No known children". (So plurial and other sequnce of the words)
Anyone know what it should be?
You're right, I correct the label.
----------------------

Index on lastnames:
When there are pointers to pages for the lastname only (without a firstname), the number of periods is too less. So the pagenumbers dont align to the right.
Pointers to pages for Firstnames are correctly aligned to the right.
I will check, the number of period is automatic. It should fit the line.
---------------------------
Placename index, see screenshot.
Why that many spaces in between in the first yellow area?
Because 2 lines needed. I'm not sure I can do anything about this.
----------------------------
The footnotes are great. But why do the numbers keep getting higher?
Why dont they start with one on every new page?
Now, when you have many people and many notes, you might get very long numbers,

Could the notes in the text itself be printed bold?
Near the bottom of the page they are not bold, thats ok. But maybe to better stand out, have them in bold on the page itself.
The footnotes are placed automatically by the conversion tool.
I have no clues on which page the note will appear.
So, the best way is to keep a sequence from the beginning.
I can put the number in bold.
Perhaps in an option, I'm not sure that put in bold any reference is a good way to do it.
----------------------------

I have a person born in 1955. Max age is set to 120. Report says he was driver. So as if he is dead already. But there is no death mentioned, nor a burial or something.
So I think that should have been "He is driver"

Another one born in 1984. There it says he lived in Someplace, so the past, but he is programmer, so present.
Why this difference for 1 and the same person?
The code is written to believe that an individual aged more than 65 is retired and the occupation text is in past.
I have not changed that, it was written this way the last 20 years.
-----------------------------
For children it says: "child of" wouldnt it be nicer if it said "son of", or "daughter of".
I will try to do that.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 16, 2023, 20:49:03
Hi Zurga,

Thanks for your answer and all the work you have done.

Quote
I have done nothing for the capitalization of the line.
The way the note is displayed will be changed tomorrow, I thing this will correct the capitalization
For the text ("Notitie :") and the period, the labels have been changed in French and English. This text is in the label in Dutch (phrase.note.header and phrase.note)
I can adjust the period and the labels in Dutch to be in-line with the English version.
Great, I will check tomorrow.

Quote
Alphabetic order.
The index are put automatically with the alphabetic order of the title.
I can try to choose a specific order if you prefer.
No its ok, just wondered why it was like that.

Quote
I will check, the number of period is automatic. It should fit the line.
Ok I will check after the update.
Added a screenshot.

Quote
The footnotes are placed automatically by the conversion tool.
I have no clues on which page the note will appear.
So, the best way is to keep a sequence from the beginning.
I can put the number in bold.
Perhaps in an option, I'm not sure that put in bold any reference is a good way to do it.

It looks as if the footnotes are always on the page they belong, but I cannot check that.
Option to put number in bold (only inside the normal text, not inside the footnotes) would be great.

Quote
The code is written to believe that an individual aged more than 65 is retired and the occupation text is in past.
I have not changed that, it was written this way the last 20 years.
Well thats a bit oldfashioned??? People work until 67 overhere. And some just go on after that. Especially teachers and other personal where there are too less of.
And certainly that other case I mentioned, that is 1 and the same person, with something in the past and something in the present.

Would it be possible to check if a person is indeed retired? or is that too much work.
Assuming a number here (65) is a bit strange.

Quote
-----------------------------
For children it says: "child of" wouldnt it be nicer if it said "son of", or "daughter of".
I will try to do that.
That would be great.


Last thing:
I still think there should be 1 option to tell:
===Either to have all event-notes inside the main note.
===Or have it like it is now.

Will you mention these changes in the French forum too, or is that just a surprise for the French readers tomorrow  :)

Well let you now after the updates are done.

Thanks a lot!!!

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 16, 2023, 23:05:20
Enhancements :
- Fix index name padding
- Modify Dutch labels
- Modify notes display, so the note should exactly the same as in the editor.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 17, 2023, 10:27:25
Enhancements :
- Fix index name padding
- Modify Dutch labels
- Modify notes display, so the note should exactly the same as in the editor.

Zurga
As noticed in the french subforum, we have a side effect concerning a blank space between two words, if the that blank space is at the beginning of a line when you're doing a retranscription of the note contain, that line appears to be indented of the others (the ones above and below). Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 17, 2023, 23:17:40
Evolution of the day :
- Add separator between text and footnotes
- Change display of footnote
- Allow to put number of footnote in italic (bold doesn't emphasize enough to be noticeable)
- Separate son/daughter in narrative part.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 18, 2023, 04:43:20
A great step forward. The problem I reported is no longer there.

one small step for the code, one giant leap for the users :-)
Thanks. Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 18, 2023, 14:02:18
Hello All,

Some remarks (and ideas) after this mornings update:

--------------------
I noticed that for education (going to a certain school) the text says: "was awarded primary school", I think that should be: "attended primary school". You are not awarded a school, but you are awarded a diplom or something.
This is coming from Trancestris: [sentence.EDUC]. I dont see a [sentence.GRAD] there.
Also, in Cygnus I see 36 possible events, but in this part of Trancestris I only see 18. Are some missing?

-------------------
Marriages, Deaths etc:
Would it be possible to get something like this:
Married at the age of xxx, on may 18 1822 in Someplace .....

So you can see at what age he married?, For both partners.

Same for the death, so "Died at the age of xxx"
And if possible age like (if known, or if it is possible to calculate it from the information) "57 year, 3 Months, 10 Days". (Sometimes this way of mentioning the age is on death certificates)

Otherwise just "At the age of 57 Years" will do. In case it cannot be calculated it could also be "At the age of at least 56 Years", or something.

Doing it like that, users could send this report to others and ask if they have more info to get the dates corrected.

-------------------
Residency: The addresses are all put on 1 line, while other events (EDUC) each get their own line.
Please put addresses on their own line also.

Furthermore the text in Dutch now says for example
Hij woonde "in xxxstraat", which is almost correct, should be "in de xxxstraat"
Hij woonde "in kerkplein", which is wrong that should have been "Hij woonde op het Kerkplein".
Depending on the name of the street you sometimes have "in de", sometimes "op het", and others are possible.
To prevent all this "in", "op", "whatever", wouldnot it be better and way easier to have a list like:

Addresses:
1910-1918         Kerkplein 16, Sometown
1918-1920         Bovenweg 123, Othertown
on 01-03-1923   Binnenweg 7, Othertown
---   etc

That way it always looks good.

For education you could have:

Education:
1910-1918     Primary School, Someroad 4, Thistown
1918-1919     Next School, Otherroad 321, Othertown
--- etc

Same kind of thing for professions, diploms etc. That gives a general approach of all this kind of information.
Maybe to prevent lots of empty space, in case only 1 line for a subject is present, it could be put right behind "Addresses:" or such. (Dont know if that will look ok, or if it should be a new option for the user to always have the list, OR to put only 1 line right after the header)
Hope you understand what I mean. See Dutch screenshot as an example.

-----------------------------
NOTEs

Now I have my own tree tested in this report, I would really really want to have the option to put every note inside the mainnote (with a small header saying "Birth", or "Death" etc, in front of it.) Now I get Note contents of 1 individual, placed a couple of individuals down the page, or in the middle of other information for this individual.

I forgot why the notes could not be put where they belong, that reason is buried somewhere in the whole thread. I remember reading you gave a reason, but forgot what it was.

I have a very good reason (I think) to ask this. In Dutch we have 2 very basic reports, called "Parenteel" and "Kwartierstaat", where "Parenteel" is eldest ancestor, downto the most recent one, and "Kwartierstaat" is the other way around.
Both are descriptive reports, and contain EACH AND ALL piece of information you have for an individual.
The Narrative report is the one that comes closest to this, but not completely.

I could not find any other report so far, that looks like the 2 Dutch ones I mentioned.
So certainly for Dutch people this might be important.

-----------------------------------
Sex of a child.

It is not always clear or obvious what the sex of a child is, just looking at their names. (Inside Ancestris yes, but on this report, no)
So in the list of children, just below their parents, could their names be preceded with "♂", or "♀", or "U". (Maybe in bold?)

See the list of sex-symbols here:
http://xahlee.info/comp/unicode_sex_symbols.html (http://xahlee.info/comp/unicode_sex_symbols.html)
 
(Those symbols could be used on other places too??) Maybe the partnership symbol on that page, or in the Ancestris tree?

----------------------------------
Jumping inside the report.
It was only today I realized you could jump up and down individuals in the report.
There is no visible sign to tell a user what is a jump.
Maybe some people dont want to see them, but I would like to have a configurable way to make a link more prominent for the readers of my report.
Like:
Yes or No in Bold, and be able to define their color?

-----------------------------------
Idea coming from the things above:
Last thing about options and the amount of options people have trouble with.

Would not it be better to have a set of standard options on the Options screen (there are already options for the website on their own tab)
Define at that place things about what people want to see in a Graphical report, and what in a Text report.
Have options there, to color and define links (options are already there for the website) and many other things.
Define font and fontsize, things like that.
A list of markers to define what info should be on a report. (With 1 marker to mark or unmark a whole set)

This might be a bigger undertaking than putting things here, but it would help preventing duplicate options.
When you have 1 central place for report options users know to go there and sit down and define each and everything they want, just once for all their reports.

This will be only true for a lot of things off course, and there will be things to specify just for 1 certain report.
But by having as much as possible at 1 place, things might be easier to maintain, and more obvious for users.

After all there is a specialised settings/options screen for all other settings in Ancestris. Just add a tab there for this kind of reports.

What do others think about this?
Please comment below!

Regards,
Mother10






Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 18, 2023, 14:44:14
Stop.

I could make some adjustments but you give a list of total change of everything.
Sorry, but I won't do that.
I already said in the French part that this report is not intended to be a full possible options book generator.
The report will never be perfect for all cases.
We have to deal with that limitation.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 18, 2023, 14:45:01
Some remarks (and ideas) after this mornings update:
When you write a message, it's a very very long one ;-)

Quote
I noticed that for education (going to a certain school) the text says: "was awarded primary school", I think that should be: "attended primary school". You are not awarded a school, but you are awarded a diplom or something.
What about "has completed elementary school" ?

Quote
Marriages, Deaths etc:
Would it be possible to get something like this:
Married at the age of xxx, on may 18 1822 in Someplace .....

So you can see at what age he married?, For both partners.
Absolutely, but Zurga will have to deal when there are no information about the age at marriage, death.

Quote
Doing it like that, users could send this report to others and ask if they have more info to get the dates corrected.
Yeap, but here you can see the interest of adding a tag note for such information, and now with the way those tag notes are displayed, it's very easy for a reader to be informed of the missing information.

Quote
Residency: The addresses are all put on 1 line, while other events (EDUC) each get their own line.
Please put addresses on their own line also.
why not.


Quote
For education you could have:
Education:
1910-1918     Primary School, Someroad 4, Thistown
1918-1919     Next School, Otherroad 321, Othertown
The result of that report must be a BOOK, something you enjoy reading, in an academic, publishing writing.



-----------------------------
Quote
NOTEs

Now I have my own tree tested in this report, I would really really want to have the option to put every note inside the mainnote (with a small header saying "Birth", or "Death" etc, in front of it.) Now I get Note contents of 1 individual, placed a couple of individuals down the page, or in the middle of other information for this individual.

I forgot why the notes could not be put where they belong, that reason is buried somewhere in the whole thread. I remember reading you gave a reason, but forgot what it was.
I really do like the way Notes and tag notes are now displayed in the report, and lots of people too. So if Zurga want to fullfill and satisfy all users requests, an option is the only way to go. Two kinds of output : the one we have, and the one you would like to have, but it means lots of work. ... ;-(
Don't forget we have two kind of notes, the general ones which are displayed at the end of an individual recording, and the ones I name tag notes, which must be displayed at the end of each page IMHO.
Francois

Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 18, 2023, 15:00:45
Hello All,

I could make some adjustments but you give a list of total change of everything.


I know yeah, but I did it mostly for the Dutch users who want their 2 basic reports as they are used to.

I'll keep it in the back of my head.

Thanks and regards,
Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 18, 2023, 15:02:45
Hello All,

Thank you Francois for your comments.

Much appreciated.
Maybe others will follow.

Regards,
Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 18, 2023, 16:34:43
Much appreciated.
Maybe others will follow.
There are thousand and thousand of ancestris users around the world, but it seems they don't like to post in the english sub-forum. I don't know why? Maybe Ancestris fullfills their needs, maybe they are too shy to post something. I hope it will change in the future. At the beginning of the french sub-forum, it was very difficult to get people to post there, but as time has gone, they began to post.

There is one thing to remember : the people behind Ancestris are volunteers, so they are not paid for their work, nor their time developping Ancestris, so, changes, improvements, etc... will come but as time goes by. And even if someone has lots of requests, it's always better to ask for them one by one. It's easier that way for developers. I saw you requested some changes about the wording, it would have been great to have an english translator doing that work with Trancestris.
Zurga nor Frederic can't do everything. In a very well known film, they say : "winter is coming", I would say, "the better is coming" but I hope there will be people as you are, who will help to develop Ancestris and make it better and better (IMHO, it is a really great genealogy program, and I don't know of such program which offers so many capabilities). A very famous sentence could be modified that way : "don't ask what Ancestris can do for you, but ask what you can do for Ancestris", and you are one of the persons who is providing a great help for Ancestris. Thanks Tineke.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 18, 2023, 16:46:05
A very famous sentence could be modified that way : "don't ask what Ancestris can do for you, but ask what you can do for Ancestris", and you are one of the persons who is providing a great help for Ancestris. Thanks Tineke.

Geeeez dont know what to say now.

:)

Thank you Francois.
Title: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 18, 2023, 18:31:19
OK, with some time I answer on each points on what is possible and what is not
--------------------
I noticed that for education (going to a certain school) the text says: "was awarded primary school", I think that should be: "attended primary school". You are not awarded a school, but you are awarded a diplom or something.
This is coming from Trancestris: [sentence.EDUC]. I dont see a [sentence.GRAD] there.
"sentence.GRAD" is present in the translation file before "sentence.CHR"
The difference of EDUC and GRAD is explained in the GEDCOM norm.
EDUC : Indicator of a level of education attained
GRAD : An event of awarding educational diplomas or degrees to individuals.
As far as I understand, the choice of the GEDCOM creator is to put the degree of education obtained.
I don't know exactly the use of the majority of users with this tag.
If you put "primary school", the sentence is wrong, if you put "primary school degree", the sentence fits better.
 
Also, in Cygnus I see 36 possible events, but in this part of Trancestris I only see 18. Are some missing?
I have 38 "sentence.TAG" in the english file.
-------------------
Marriages, Deaths etc:
Would it be possible to get something like this:
Married at the age of xxx, on may 18 1822 in Someplace .....

So you can see at what age he married?, For both partners.

Same for the death, so "Died at the age of xxx"
And if possible age like (if known, or if it is possible to calculate it from the information) "57 year, 3 Months, 10 Days". (Sometimes this way of mentioning the age is on death certificates)

Otherwise just "At the age of 57 Years" will do. In case it cannot be calculated it could also be "At the age of at least 56 Years", or something.

Doing it like that, users could send this report to others and ask if they have more info to get the dates corrected.
I can put age in the events and narration, but only if the tag AGE is populated in the GEDCOM. I will not add calculation of age in the report.
The value displayed will be the exact value calculated in the software (menu "Edit", "Calculate ages").
-------------------
Residency: The addresses are all put on 1 line, while other events (EDUC) each get their own line.
Please put addresses on their own line also.
I don't get this one.
Each residency (RESI) tag have his own line with the date and place.
Furthermore the text in Dutch now says for example
Hij woonde "in xxxstraat", which is almost correct, should be "in de xxxstraat"
Hij woonde "in kerkplein", which is wrong that should have been "Hij woonde op het Kerkplein".
Depending on the name of the street you sometimes have "in de", sometimes "op het", and others are possible.
To prevent all this "in", "op", "whatever", wouldnot it be better and way easier to have a list like:

Addresses:
1910-1918         Kerkplein 16, Sometown
1918-1920         Bovenweg 123, Othertown
on 01-03-1923   Binnenweg 7, Othertown
---   etc

That way it always looks good.

For education you could have:

Education:
1910-1918     Primary School, Someroad 4, Thistown
1918-1919     Next School, Otherroad 321, Othertown
--- etc

Same kind of thing for professions, diploms etc. That gives a general approach of all this kind of information.
Maybe to prevent lots of empty space, in case only 1 line for a subject is present, it could be put right behind "Addresses:" or such. (Dont know if that will look ok, or if it should be a new option for the user to always have the list, OR to put only 1 line right after the header)
Hope you understand what I mean. See Dutch screenshot as an example.
No for the lists.
Beside this, you can change the label in Dutch to fit more your languages specifics needs
for example, if you put in translation : [OPTIONAL_PP_DATE] : [1][OPTIONAL_PP_PLACE].
You will get something like the list you have defined.
-----------------------------
NOTEs

Now I have my own tree tested in this report, I would really really want to have the option to put every note inside the mainnote (with a small header saying "Birth", or "Death" etc, in front of it.) Now I get Note contents of 1 individual, placed a couple of individuals down the page, or in the middle of other information for this individual.

I forgot why the notes could not be put where they belong, that reason is buried somewhere in the whole thread. I remember reading you gave a reason, but forgot what it was.

I have a very good reason (I think) to ask this. In Dutch we have 2 very basic reports, called "Parenteel" and "Kwartierstaat", where "Parenteel" is eldest ancestor, downto the most recent one, and "Kwartierstaat" is the other way around.
Both are descriptive reports, and contain EACH AND ALL piece of information you have for an individual.
The Narrative report is the one that comes closest to this, but not completely.

I could not find any other report so far, that looks like the 2 Dutch ones I mentioned.
So certainly for Dutch people this might be important.
No.
I keep the notes as there are now.
I give the explanation in French : General information note describes often the individual when tags notes give precision on the event with no reason to be read in normal text.

For your specific use, I suggest to print individual sheets.
It could be possible to adapt the GEDART template to fit better the need of all and every piece of information known.
-----------------------------------
Sex of a child.

It is not always clear or obvious what the sex of a child is, just looking at their names. (Inside Ancestris yes, but on this report, no)
So in the list of children, just below their parents, could their names be preceded with "♂", or "♀", or "U". (Maybe in bold?)

See the list of sex-symbols here:
http://xahlee.info/comp/unicode_sex_symbols.html (http://xahlee.info/comp/unicode_sex_symbols.html)
 
(Those symbols could be used on other places too??) Maybe the partnership symbol on that page, or in the Ancestris tree?
No.
I have differentiated son and daughter in the text, it should be sufficient to know which sex has the individual.
I don't see the gain to charge the name line with the symbol of sex.
 
----------------------------------
Jumping inside the report.
It was only today I realized you could jump up and down individuals in the report.
There is no visible sign to tell a user what is a jump.
Maybe some people dont want to see them, but I would like to have a configurable way to make a link more prominent for the readers of my report.
Like:
Yes or No in Bold, and be able to define their color?
The link are basically for a web export.
In html export,the link are underlined.
In pdf, the link are present but the intended printing is on paper. I don't get the point to emphasize the link on paper.
It seems enough for me.
-----------------------------------
Idea coming from the things above:
Last thing about options and the amount of options people have trouble with.

Would not it be better to have a set of standard options on the Options screen (there are already options for the website on their own tab)
Define at that place things about what people want to see in a Graphical report, and what in a Text report.
Have options there, to color and define links (options are already there for the website) and many other things.
Define font and fontsize, things like that.
A list of markers to define what info should be on a report. (With 1 marker to mark or unmark a whole set)

This might be a bigger undertaking than putting things here, but it would help preventing duplicate options.
When you have 1 central place for report options users know to go there and sit down and define each and everything they want, just once for all their reports.

This will be only true for a lot of things off course, and there will be things to specify just for 1 certain report.
But by having as much as possible at 1 place, things might be easier to maintain, and more obvious for users.

After all there is a specialised settings/options screen for all other settings in Ancestris. Just add a tab there for this kind of reports.
No.
I will rearrange the options in the option tab when the job is finished with adding options from all requests.
But each report is conceived as independent from the others.
So no common tab of options.

Zurga
Title: Re: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 18, 2023, 18:37:53
-------------------
Residency: The addresses are all put on 1 line, while other events (EDUC) each get their own line.
Please put addresses on their own line also.
I don't get this one.
Each residency (RESI) tag have his own line with the date and place.
Gotcha.
If all RESI tag are one after the other, you get a list of value instead of list of sentence.
It's something I will remove from the code.
The way it is done is wrong, it's works only if all the tag from a type are next to each other in the GEDCOM.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 18, 2023, 20:40:00
Hi Zurga,

Thanks a lot for all your replies.
I will look at your remarks tomorrow and see if changing the translation for some might help.
Or change the gedcom a bit.

I know you are doing your utmost and I value that.

-----
About the Gedart for the 2 Dutch reports: I already thought about that.
So maybe when I have finally continued with my tree a bit, I will give that a go.

------
GRAD / EDUC. Looked those up in the Gedcom.
You are right.
It seems I need an INDIVIDUAL_ATTRIBUTE_STRUCTURE to describe this, I will look it up in the Gedcom and act accordingly. (I saw I can even have a school addres and such)

------
Addresses:
You are right again, this is how it looks in my gedcom, RESI's all one after the other:
Code: [Select]
1 RESI
2 ADDR Nigellestraat 6
3 CITY Amsterdam
2 DATE FROM 1950 TO 1957
1 RESI
2 ADDR duinweg 79
3 CITY Schoorl
2 DATE FROM 1957 TO 1968
1 RESI
2 ADDR
3 CITY Utrecht
2 DATE FROM 1968 TO 3 SEP 1971
1 RESI
2 ADDR
3 CITY Den Helder
2 DATE 3 SEP 1971

-----
PDF links:
I try to read as much as possible on my screen, saves paper. Thats why I asked.
But its ok, I now know there are links to click on.

As always, keep up the good work Zurga!

Regards,
Mother10


Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: remi0144 on August 18, 2023, 21:07:44
-----
PDF links:
I try to read as much as possible on my screen, saves paper. Thats why I asked.
But its ok, I now know there are links to click on.

As always, keep up the good work Zurga!

Regards,
Mother10

Hello,
Sorry, I don't speak English, this is a translation from DeepL.
My pdf reader under Linux Mint has a function to frame words in a document that have a clickable link.
This software is qpdfview. Unfortunately, it doesn't seem to run on any other OS like Windows, unless I'm mistaken.
It's a must-have.
Rémi
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 18, 2023, 23:32:39
News of the day :
- Display ages of events (if tag AGE exists)
- Display all tags if asked for
- Remove list of properties (like RESI mentioned by Tineke).

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 08:10:24
Sorry, I don't speak English, this is a translation from DeepL.
My pdf reader under Linux Mint has a function to frame words in a document that have a clickable link.
This software is qpdfview. Unfortunately, it doesn't seem to run on any other OS like Windows, unless I'm mistaken.
It's a must-have.
I don't understand why it could be difficult to print a document with hyperlinks in it. Maybe I'm wrong, but this leads me to notice that it's much, much better to have the tag notes at the end of each page instead of having them at the end of the document (the book). This is because when you print your genealogy book resulting from that report, it wouldn't be convenient for a reader to always go to the end of the book to read the tag notes and then return to the previous page, etc. The fact that we now have the tag notes just below the events related to them is a must-have, and it makes readers enjoy their reading.
Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 08:13:21
Sorry, I don't speak English, this is a translation from DeepL.
Maybe but it's great, you're right to post in english. Francois
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 10:51:28
Hello All,

I wanted to get the ages in this report, so I ran the Ages tool first before starting this report.
I can see AGE-tags added in the Gedcom editor of myself, but not for my late husband.
So somehow not each and every individual gets AGE-tags.

So when marriages are described in the report (not just mine, but others too), only the first person in the sentence, gets the age description, but his/her spouse does never.
Why?
What could be the problem?

Thanks,
Tineke
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 11:21:09
Do you have children with that husband? If not, it's logical that you don't have the age at marriage for your husband when you run the report for yourself or one of your children. If you do have children with that husband, run the report for one of your children, and you will see your age at marriage. If you click on the name of your husband, you will see that he is married to you at the age of xxx.

Age is only provided for individuals connected to the ancestors of the person on which you are running the script. Zurga did not intend to include the ages of all individuals mentioned in the report

In my humble opinion, this is logical, unless you request Zurga to add the age of individuals even if they are not active members (?) of your ancestors.
Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 12:24:57
My question was: why are there no AGE-tags, so the output of the AGE-tool, not the report.
Zurga said there could only be ages in the sentences, when a person had AGE-tags.
So I tried to create AGE-tags, for each and every person in my tree with that AGE-tool.
The docs do not mention any restrictions for that tool if I am correct.
That Tool-description in the guide says for all individuals of you genealogy.

My problem is, I see no age tags for my husband, and many others, so I want to know why they are not there.
And yes, we do have children (hence my nickname mother10) ;)

Correction:

The FAM record of my marriage does have an AGE-tag for me(WIFE) AND for my husband(HUSB). So both TAGS are present, but 1 is not in the sentence.
Same for my Father. So I suppose that only the person that is in the same line of the report gets the age printed.
Looks funny when 2 people get married, only 1 of them printed with his/her age..

But if that is the rule, well, that so be it.

Tineke (Mother10)
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 12:51:11
Give me an example, where you want an age tag please ? I will try to understand ?
Second : what editor do you use ? the gedcom one ? cygnus ? Aries ?
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 13:02:58
The FAM record of my marriage does have an AGE-tag for me(WIFE) AND for my husband(HUSB). So both TAGS are present, but 1 is not in the sentence.
Same for my Father. So I suppose that only the person that is in the same line of the report gets the age printed.
Looks funny when 2 people get married, only 1 of them printed with his/her age..
As I mentioned earlier, run the report for one of your children. Then, navigate to the second generation. Once you are there, you will find your husband. Mr. xxxxxx ... married on xxxxx in xxxxxxxxx at the age of 26 years, 11 months, and 2 days to Mother10.

As you can observe, you have the age of your husband but not your own. At this point, click on your name "Mother10" (naturally, it will be your actual name), and you will be directed to your record. There, you will see: Mother10 married on xxxxxx in xxxxxxx at the age of xxxxxxx to Mr. xxxxxxxx. So you will have the age of the second spouse
Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 13:16:19
From my tree:

In this marriage only the first partner (male in this case: Egbert) gets an age description in its text (in yellow), the other partner, his wife Reentje, does not get the age description.
Her age description I would expect at the arrow point.

The FAM record of the marriage contains both TAGs.

Just checked, my remark about AGE tags not present does not seem to be correct, so forget about that.

Then this remark, about only one partner getting an age description, stays.

Tineke
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 13:26:59
Please Tineke, read my previous post and give it a try. Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 13:36:37
Hello All, hello Zurga,

There seems to be 1 small thing I now notice in the sentence, in the situation of a person who is married, and who died. See screenshot.

This is about Antje Koster, married to Geert Stel. And Antje Koster dies at the age of 42 years, 10 months.

I will give the sentence from the screenshot in English, but leave out some parts with xxx:

Antje Koster, born on xxx(daughter of xxx and xxx), married on march 21 1890 in Midwolda at the age of xxx with Geert Stel, died on june 27 1908 in yyy.

You see a comma right behind "Geert Stel" followed by "died on..."
Now it looks a bit as if Geert Stel died, but what is meant is that Antje died.

Maybe put a period behind Geert Stel, and then start a new sentence right after the period, with "She/Antje died at xxxxx".

Or am I "putting salt on every snake" as we say in Dutch. ;)

Mother10
Title: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 13:46:09
There seems to be 1 small thing I now notice in the sentence, in the situation of a person who is married, and who died. See screenshot.

This is about Antje Koster, married to Geert Stel. And Antje Koster dies at the age of 42 years, 10 months.

I will give the sentence from the screenshot in English, but leave out some parts with xxx:

Antje Koster, born on xxx(daughter of xxx and xxx), married on march 21 1890 in Midwolda at the age of xxx with Geert Stel, died on june 27 1908 in yyy.

You see a comma right behind "Geert Stel" followed by "died on..."
Now it looks a bit as if Geert Stel died, but what is meant is that Antje died.

Maybe put a period behind Geert Stel, and then start a new sentence right after the period, with "She/Antje died at xxxxx".

Very interesting. That's a difference between french and dutch. In french, the comma you have behind  Geert Stel, means that the death reported after is the one of Antje Koster, not the one of Geert Stel. In dutch, that's the opposite. Interesting.


Quote
Or am I "putting salt on every snake" as we say in Dutch. ;)
;-) I do not know that. It's funny. In french we say that if you put sallt on the tail of a bird, you can catch it ;-) Not the same meaning, but always about salt :-)
Francois
Title: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 13:47:29
From my tree:

In this marriage only the first partner (male in this case: Egbert) gets an age description in its text (in yellow), the other partner, his wife Reentje, does not get the age description.
Her age description I would expect at the arrow point.

The FAM record of the marriage contains both TAGs.

Just checked, my remark about AGE tags not present does not seem to be correct, so forget about that.

Then this remark, about only one partner getting an age description, stays.

Tineke

yes I found that, but my point was: why not for BOTH persons in a marriage get their age, so in 1 sentence.
Why do I have to jump to see someone elses age when it is a description of 1 and the same event.

As I mentioned in another post, the 2 Dutch reports "Kwartierstaat" and "Parenteel" both have the ages of both persons in a marriage in 1 sentence.
(see other screenshot)

But as I said, that does not seem to be the rule.
So I accept it as a rule then.

Tineke
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 13:51:05
Hello Francois,

Quote
Very interesting. That's a difference between french and dutch. In french, the comma you have behind  Geert Stel, means that the death reported after is the one of Antje Koster, not the one of Geert Stel. In dutch, that's the opposite. Interesting.

When you look at my last post you see an example of the Dutch.
As you can see a lot of info in that small piece, even the parents of the partner and the partners death.
When you look closely, you see more sentences. Separated with periods, so there is no mistake in what the sentence means.

Tineke
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 13:56:16
Yes, I think it's not a big deal to change the comma for a period. In french it will mean the same as actually, and if for dutch users, and maybe english speaking users, it's better to have a period, I support that request.
Title: Re : Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 19, 2023, 14:37:37
yes I found that, but my point was: why not for BOTH persons in a marriage get their age, so in 1 sentence.
Why do I have to jump to see someone else age when it is a description of 1 and the same event.
Because the report doesn't describe couples but individuals.
So the sentence describe the first partner, not the second.
For me there is no logic to put the age of the second partner in the description of the first one.

In your example, you describe the couple : first sentence about Antje, then a sentence about Geert.
Different logic of report, different result.

Zurga
Title: Re: Re : Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 19, 2023, 14:43:12

In your example, you describe the couple : first sentence about Antje, then a sentence about Geert.
Different logic of report, different result.

Zurga

Its ok, as I said that is the rule, and I accept.
Title: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: remi0144 on August 19, 2023, 18:21:12
I don't understand why it could be difficult to print a document with hyperlinks in it.
Francois

Because hyperlinks are often colored, bolded or underlined, and that's not suitable for a printable book.
To see the links visually, you either prefer a report like the Web book, or use the technique I've given, i.e. the pdf reader that highlights them.
Personally, I don't want to see these links highlighted in the report, although they are very useful.

Rémi
Title: Re : Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 18:30:43
I don't understand why it could be difficult to print a document with hyperlinks in it.
Francois

Because hyperlinks are often colored, bolded or underlined, and that's not suitable for a printable book.
To see the links visually, you either prefer a report like the Web book, or use the technique I've given, i.e. the pdf reader that highlights them.
Personally, I don't want to see these links highlighted in the report, although they are very useful.

I agree with you, but currently, there are already hyperlinks on certain names, and those links are not colored or, at least on my computer (running Ubuntu), those links appear in black, just like the text. Francois
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 19, 2023, 18:38:23
Would it be possible to consider changing the first letter of an occupation from uppercase to lowercase, if the person's occupation starts with an uppercase letter? Currently, it reads "He was Farmer." Could we have it as "He was farmer" Is it advisable to do this? thank you. Francois
Title: Re: Re : Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: remi0144 on August 19, 2023, 19:28:25
I agree with you, but currently, there are already hyperlinks on certain names, and those links are not colored or, at least on my computer (running Ubuntu), those links appear in black, just like the text. Francois

We're not talking about the same thing, François. I'm replying to you precisely on the French thread because I'll express myself better and the French should follow too.

Rémi
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 21, 2023, 07:49:35
Hello Zurga, hello All,

Latest test of this morning looks very good in Dutch for my own tree.
So again Zurga, thanks for all the work you did (taking your whole weekend ;)  )

Because my tree does not have all possibilities and things that are changed, I will try to create a Gedcom with all the ins and outs, especially for that.
Will let you know about the results.

Regards,
Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 21, 2023, 17:51:47
Hi,
I've checked the English resource file and the French one. We have an error in the French one that produces incorrect output in the narrative report. In the English resource file, we have "Graduation," and this word has been translated as "Diplôme." This is incorrect, as "Graduation" refers to the ceremony where you receive your diploma. Therefore, the French resource file should be corrected, and once that's done, the output of the narrative report should be adjusted accordingly. This will make the translation for the narrative report more accurate for other languages. Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 25, 2023, 10:31:35
Hi Zurga,

We have a problem with the way short date labels (and some other short labels) are dealt with. I did an update of the Dutch translation, where I changed a couple of these labels into words that had more then those 3 characters.

It was reverted by Frederic, because only 3 characters were allowed there.

Yesterday Harry (the other translator) and I had a couple of discussions on the phone, about how these looked on the Dutch report.
And we both agreed it looked awfull. So together we decided about other words to put there, which had more characters, but would look good on the report.

I understand completely that the longer words would couse trouble on the Ancestris screens.

But there are 2 different point of views here.

1: The Ancestris user.
He knows what the abbreviations mean, is used to them, AND, as a great help, has hints that tell him what their meaning is, in case it is unclear.

2. The report reader.
He wants understandable texts, that are easy to read. And wellknown abbreviations not "invented ones", or, in case an abbreviation is just a few characters shorter than the original word) the original word instead.

Those 2 things collide here.
And probably in more languages.

So i would like to ask if it is possible to solve this.

Either by adding another set of labels, just for reports. (disadvantage: a lot of work)
Or,
By leaving the labels as they are, but when putting them in their respective place in Ancestris itself, not put the whole label in there, but just the first 3 characters.

That last solution would not change a thing for French or English users. But it will give users from another language the possibility of more freedom to find the correct abbreviations or maybe the full-word, in case abbreviation and full-word only differ just a few characters.

Would/could you do that?

Regards,
Tineke
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 25, 2023, 12:48:38
I know it looks awful, the same in French or English.
But your choice to augment theses labels are not the good way to do it.
The good way is to wait that I develop a specific format to allow the complete words.

Please show a little patience on this subject.

Zurga
Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 25, 2023, 12:54:41
Hi Zurga,

That sounds great indeed. Did not know you had that in mind.
And I understand that is a lot of work because it will be all over Ancestris probably.

I'll be patient!

Thanks,
Tineke

Title: Re : Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 25, 2023, 23:55:20
You should see some enhancements tomorrow.
You will have all you want to translate with complete words.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 09:53:45
Hi Zurga,

Very happy with the long words on the report. Still in English but thats because they are still untranslated, i'll change that.

I have the following (2 unknown events):

1 EVEN This is an unknown event
1 EVEN Another unknown event
2 TYPE Land Lease
2 DATE 5 AUG 1988
(examples from gedcom spec somewhere)

----------------------
On the Dutch report i get:

Hij was betrokken bij een gebeurtenis .
Hij was betrokken bij een gebeurtenis op 5 augustus 1988.

As you can see I get no information from the first event, i was expecting to see "This is an unknown event" in stead of that space character before the period, but I could be wrong.
The second line/event just gives the date but not the TYPE.

-------------------
The French report (same gedcomfile) gives me:

, un évènement, l'a concerné.
Land Lease, un évènement, l'a concerné le 5 août 1988.

So a sentance starting with a ,

--------------------
English gives me:

He was involved in some kind of event:.
He was involved in some kind of event: Land Lease on 5 August 1988.

So first line ands on a : which is directly followed by a period. Why is English the only one with :     ? (Because the French sentence should start with the info, while the English ends with it?
What happens with other languages which might have the sequence as in French then?

==============    ====================

Just a question because i remember it has been said, but seems hidden in those many French posts:
What was the reason not to have comma's in between the long date format?
So "at age 36 years 5 months 5 days", en not "at age 36 years, 5 months, 5 days".

-------------

When all my translating for the Dutch report is done, i will check for periods and commas and such.
Also i will try to add more properties and possibilities in my testgedcom.
Pity nobody seems to have some kind of complete V5 testgedcom.
Searched everywhere but could not find any. The ones with kings and such are dedicated to the kings, not meant as a complete test for gedcom. The ones on the gedcom io or something are just tiny ones, no extensive tests.
That would help me a lot in deciding what i had to put where.

And for now a gedcom 7 testfile is nowhere.
Would like to have one, with all ins and outs.

Thanks for your hard work!

Regards,
Tineke
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 26, 2023, 10:19:21
Hi,
Some tests :
1) Some code are missing. Running Ancestris in english (interface language), and ask for output report (reports language) to be in french, it still gives me english when it reports Sources. The word Sources is in french, but birth, death, etc... are still in english.
2) Again two persons living together : Mr John Doe .... lived to Joannah Harris. "Lived to" doesn't make sense. It should be changed IMHO.
3) When someone is unknown as "André DOUX, son of DOUX and , born estimated as 1629". His mother is not known. Would it be possible to add "unknown" as : "André DOUX, son of DOUX and Unknown, born estimated as 1629". A child can't be born without a woman, his/her mother, so whether or not his/her mother is added, it would be a good information to add "unknown", instead of just a blank space. It means that's not a mistake, it's just that we haven't found his mother's name.
Thanks. Francois


Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 10:36:49


Hi,
Some tests :
1) Some code are missing. Running Ancestris in english (interface language), and ask for output report (reports language) to be in french, it still gives me english when it reports Sources. The word Sources is in french, but birth, death, etc... are still in english.

Now I think about sources:
Would it be a good idea to have a list of Repositories too? (if someone wants them?)

Quote
3) When someone is unknown as "André DOUX, son of DOUX and , born estimated as 1629". His mother is not known. Would it be possible to add "unknown" as : "André DOUX, son of DOUX and Unknown, born estimated as 1629". A child can't be born without a woman, his/her mother, so whether or not his/her mother is added, it would be a good information to add "unknown", instead of just a blank space. It means that's not a mistake, it's just that we haven't found his mother's name.
Thanks. Francois

I really also like the Italic in there. When some information is unknown, to have unknown in stead, and not en empty space.
Maybe for other things too?
So I second that.

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 26, 2023, 10:37:33
Just a question because i remember it has been said, but seems hidden in those many French posts:
What was the reason not to have comma's in between the long date format?
So "at age 36 years 5 months 5 days", en not "at age 36 years, 5 months, 5 days".
I made the following proposal :
What about a new parameter as : Should the dates be exact or rounded up or down to the nearest year?  Yes/No.

That way, if a date is "36 years 5 months 5 days", if parameter is set to yes, the date should be written that way. But if the parameter is set to No, the date would be written as "He died at around 36 years old.
If the date is 36 years 6 months 5 days, it should be written as "He died at around 37 years old"
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 26, 2023, 10:45:05
Now I think about sources:
Would it be a good idea to have a list of Repositories too? (if someone wants them?)
Yes, that would be a good idea, as the sources are linked to repository locations, but Zurga already has so much work that I'm not sure if we can ask that of him and if it interests many people. I also noticed in the French forum that someone was asking for a list of professions, similar to what we can find for places, but again, it's a lot of work.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 26, 2023, 10:56:55
When all my translating for the Dutch report is done, i will check for periods and commas and such.
Also i will try to add more properties and possibilities in my testgedcom.
Pity nobody seems to have some kind of complete V5 testgedcom.
Searched everywhere but could not find any. The ones with kings and such are dedicated to the kings, not meant as a complete test for gedcom. The ones on the gedcom io or something are just tiny ones, no extensive tests.
That would help me a lot in deciding what i had to put where.
Someone in the french forum seems to use a test gedcom file for that narrative report. I guess it's remi0144. Maybe you could ask him to send it to you. Even if the sentences are in french, the framework will be in english or dutch or whatever you want.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 11:01:43

Someone in the french forum seems to use a test gedcom file for that narrative report. I guess it's remi0144. Maybe you could ask him to send it to you. Even if the sentences are in french, the framework will be in english or dutch or whatever you want.

Remi? Do you have one?
Would be very gratefull for that.

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 11:07:19
Now I think about sources:
Would it be a good idea to have a list of Repositories too? (if someone wants them?)
Yes, that would be a good idea, as the sources are linked to repository locations, but Zurga already has so much work that I'm not sure if we can ask that of him and if it interests many people. I also noticed in the French forum that someone was asking for a list of professions, similar to what we can find for places, but again, it's a lot of work.

Intended to answer in the French forum, but yes I second that.

Sorry Zurga, in Dutch we say; "Give someone 1 finger and he/she wants the whole hand." :)  :)

Thats for the OCCU tag, maybe EDUC and GRAD are good candidates then also.

But forget about it if not many people are interested.

O and about the date parameter, I second that too.

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 14:34:00
Hi all,

In my TestGedcom I have this:

0 @I000005@ INDI
1 NAME Susanne /Doe/
2 GIVN Susanne
2 SURN Doe
1 SEX F
1 BIRT
2 DATE 3 MAR 2002
2 PLAC , Hoorn, , Hoorn, Noord-Holland, Nederland
3 MAP
4 LATI N52.6425
4 LONG E5.05972
1 DEAT Y

So a confirmed death but with no other information (page 21 Gedcom 5.5.1). The report says:

"Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn."
So without mentioning she died.

A normal death looks like:
"Mark Doe, b. on 2 October 1930 in Leeuwarden, e. between 1998 and 2000 in Hoorn then m. on 30
August 1958 in Leeuwarden at age 27 years 10 months 28 days to Charlot Davies, d. on 27 May 2001
in Alkmaar at age 70 years 7 months 25 days."

So maybe Susanne could be:
"Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn, confirmed dead."
With that part in italic as said in another answer.

The same happens when DEAT is like:

1 DEAT Y
2 PLAC , Hoorn, , Hoorn, Noord-Holland, Nederland
3 MAP
4 LATI N52.6425
4 LONG E5.05972

So in case there is just a place and no date.

-------------------------------

My testgedcom has 3 source Entities.
Only 1 of them gets in the Source index, why?
All 3 sources are named below the individuals they belong to, so Ancestris does see them correctly I suppose.
Screenshot of the one in the index, and another of a missing one from the index.

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 26, 2023, 14:42:10
I have the following (2 unknown events):

1 EVEN This is an unknown event
1 EVEN Another unknown event
2 TYPE Land Lease
2 DATE 5 AUG 1988
(examples from gedcom spec somewhere)

----------------------
On the Dutch report i get:

Hij was betrokken bij een gebeurtenis .
Hij was betrokken bij een gebeurtenis op 5 augustus 1988.

As you can see I get no information from the first event, i was expecting to see "This is an unknown event" in stead of that space character before the period, but I could be wrong.
The second line/event just gives the date but not the TYPE.

-------------------
The French report (same gedcomfile) gives me:

, un évènement, l'a concerné.
Land Lease, un évènement, l'a concerné le 5 août 1988.

So a sentance starting with a ,

--------------------
English gives me:

He was involved in some kind of event:.
He was involved in some kind of event: Land Lease on 5 August 1988.

So first line ands on a : which is directly followed by a period. Why is English the only one with :     ? (Because the French sentence should start with the info, while the English ends with it?
What happens with other languages which might have the sequence as in French then?
The EVEN structure you put is not GEDCOM compliant :
Code: [Select]
n EVEN {1:1}
+1 <<EVENT_DETAIL>> {0:1}
The EVEN tag has no value.
If you want something correct, you should put the following
1 EVEN
2 TYPE This is an unknown event
1 EVEN
2 TYPE Another unknown event, Land Lease
2 DATE 5 AUG 1988

For the text, the french version is the one accepted by the community.
The English one is what it was in the code in 2005.
For the Dutch translation, you can put what you want. To display the TYPE put in the line [OPTIONAL_TYPE]

==============    ====================

Just a question because i remember it has been said, but seems hidden in those many French posts:
What was the reason not to have comma's in between the long date format?
So "at age 36 years 5 months 5 days", en not "at age 36 years, 5 months, 5 days".
The reason is : the module to calculate ages doesn't put commas.
In the report I only display the value of the tag AGE present in the GEDOCM file, I don't change the value or calculate the value.
-------------

When all my translating for the Dutch report is done, i will check for periods and commas and such.
Also i will try to add more properties and possibilities in my testgedcom.
Pity nobody seems to have some kind of complete V5 testgedcom.
Searched everywhere but could not find any. The ones with kings and such are dedicated to the kings, not meant as a complete test for gedcom. The ones on the gedcom io or something are just tiny ones, no extensive tests.
That would help me a lot in deciding what i had to put where.

And for now a gedcom 7 testfile is nowhere.
Would like to have one, with all ins and outs.
You can find some Gedcom 7 files here : https://gedcom.io/tools/
For Gedcom 5, I believe each one uses his own test file, you can find some tests cases here : https://gedcomassessment.com/en/index.htm
But basically their tests are to detect bad compliance and not to extensively test the possibles GEDCOM options.

@Arvernes
Some tests :
1) Some code are missing. Running Ancestris in english (interface language), and ask for output report (reports language) to be in french, it still gives me english when it reports Sources. The word Sources is in french, but birth, death, etc... are still in english.
I will try to get a report value for the tag Name.
2) Again two persons living together : Mr John Doe .... lived to Joannah Harris. "Lived to" doesn't make sense. It should be changed IMHO.
I think "married to" is also not very correct in English.
I will clean the preposition used and put "married", "divorced" and "lived with"
3) When someone is unknown as "André DOUX, son of DOUX and , born estimated as 1629". His mother is not known. Would it be possible to add "unknown" as : "André DOUX, son of DOUX and Unknown, born estimated as 1629". A child can't be born without a woman, his/her mother, so whether or not his/her mother is added, it would be a good information to add "unknown", instead of just a blank space. It means that's not a mistake, it's just that we haven't found his mother's name.
Just put some name in you empty name tag.
Empty name tag are forbidden in GEDCOM.
Remove the individual or name it.
You won't have any empty space.

@Mother10
Now I think about sources:
Would it be a good idea to have a list of Repositories too? (if someone wants them?)
No.
I don't see the narrative benefit of the list of repositories.
If you want the list, you can export the entity table.

Thats for the OCCU tag, maybe EDUC and GRAD are good candidates then also.
Perhaps.

As I already said : This report is not intended to have any piece of information of the GEDCOM put in it.
If you want stats, you have the "GEDCOM Statistics" report.

Please stay focused on the purpose of this report: to give a short biography of each person involved in the ascending or descending genealogy of a named person.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 26, 2023, 14:50:57
So maybe Susanne could be:
"Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn, confirmed dead."
With that part in italic as said in another answer.
And what about : "Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn, died (date unknown)."
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 14:58:50
So maybe Susanne could be:
"Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn, confirmed dead."
With that part in italic as said in another answer.
And what about : "Susanne Doe, daughter of Fred Doe and Susan Taylor, b. on 3 March 2002 in Hoorn, died (date unknown)."

Yeah thats better
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 26, 2023, 16:19:38
Quote
@Arvernes
Citaat van: arvernes op Vandaag om 10:19:21
Some tests :
1) Some code are missing. Running Ancestris in english (interface language), and ask for output report (reports language) to be in french, it still gives me english when it reports Sources. The word Sources is in french, but birth, death, etc... are still in english.

I will try to get a report value for the tag Name.

The Dutch report in an English Ancestris says:
"Table of Contents" that should have been in Dutch.


------------------------------
Also, same as mentioned by Averness, the list of sources, right below a person, with an English Ancestris set to a Dutch report, says:

Code: [Select]
Bronnen :
[Marriage : S977]
[Marriage : S963]
[Marriage : S962]
[Christening : S1006]
[Residence : S1004]
[Residence : S963]

Those should have been Dutch words.

-------------------------------------
Noticed something else:
In my own tree I have children without a birth date, but only a valid baptise date.

That gives me "She was baptised in yy on xxx(date) at the age of <1 day".
When there is no birthdate only baptise date, it may be better to leave out that age part.

And another one "xx, geb. in juni 1795, overl. op 14 juni 1795 in Wedde op de leeftijd van <1 dag.". (no day for the birth, just a month, but a complete death date.
So there might be more other possibilities when dates are not complete (no day itself)

---------------------------
Child with unknown sex at birth (because it died early or something) I get
"SUBJECT werd gedoopt in 1750 op de leeftijd van <1 dag."
So SUBJECT, not he or she. Dont know if that is in a translation somewhere.

Mother10
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 26, 2023, 17:28:07
Quote
@Arvernes
Citaat van: arvernes op Vandaag om 10:19:21
Some tests :
1) Some code are missing. Running Ancestris in english (interface language), and ask for output report (reports language) to be in french, it still gives me english when it reports Sources. The word Sources is in french, but birth, death, etc... are still in english.

I will try to get a report value for the tag Name.

The Dutch report in an English Ancestris says:
"Table of Contents" that should have been in Dutch.
Noted
------------------------------
Also, same as mentioned by Arvernes, the list of sources, right below a person, with an English Ancestris set to a Dutch report, says:

Code: [Select]
Bronnen :
[Marriage : S977]
[Marriage : S963]
[Marriage : S962]
[Christening : S1006]
[Residence : S1004]
[Residence : S963]

Those should have been Dutch words.
If you read sometimes what I wrote, you probably might notice that I will try to correct this type of use of wrong language.
You could think that if I use the correct language in the report, this will be correct in any language.
No need to report twice.
-------------------------------------
Noticed something else:
In my own tree I have children without a birth date, but only a valid baptise date.

That gives me "She was baptised in yy on xxx(date) at the age of <1 day".
When there is no birthdate only baptise date, it may be better to leave out that age part.

And another one "xx, geb. in juni 1795, overl. op 14 juni 1795 in Wedde op de leeftijd van <1 dag.". (no day for the birth, just a month, but a complete death date.
So there might be more other possibilities when dates are not complete (no day itself)
If you read what I wrote earlier, you probably might notice that I have indicated that I use the value calculated by the "Age module".
I don't change any value.
Refer to Frederic who has coded this module.
---------------------------
Child with unknown sex at birth (because it died early or something) I get
"SUBJECT werd gedoopt in 1750 op de leeftijd van <1 dag."
So SUBJECT, not he or she. Dont know if that is in a translation somewhere.
Noted

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 26, 2023, 22:00:14
Enhancement of day :
- Add image on front cover
- Add option to lowercase occupation
- Add occupation index
- Correct language for ToC
- Correct use of gender unknown subject
- Correct language in sources
- Add phrase for death without details
- Allow to display URL images.

It's all for me on this report.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 27, 2023, 07:09:47
- Add image on front cover
Thanks. That gives a great look to the book
Quote
- Add option to lowercase occupation
Good enhancement.
Quote
- Add occupation index
OK
Quote
- Correct language for ToC
fixed
Quote
- Correct use of gender unknown subject
Not tested
Quote
- Correct language in sources
fixed
Quote
- Add phrase for death without details
it seems it works only for tag DEAT Y, not for tag DEAT if empty.
Quote
- Allow to display URL images.
not tested
Thanks for the good work. That report gives now a pretty great result. Francois
Title: Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 27, 2023, 07:43:05
Quote
- Add phrase for death without details
it seems it works only for tag DEAT Y, not for tag DEAT if empty.
Some day you will understand that a empty tag is not GEDCOM compliant.

Code: [Select]
All GEDCOM lines have either a value or a pointer unless the line contains subordinate
GEDCOM lines. The presence of a level number and a tag alone should not be used to assert data
(i.e. 1 FLAG Y not just 1 FLAG to imply that the flag is set).

Zurga
Title: Re : Re : Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 27, 2023, 07:49:38
Quote
- Add phrase for death without details
it seems it works only for tag DEAT Y, not for tag DEAT if empty.
Some day you will understand that a empty tag is not GEDCOM compliant.
Did you read any complaints from me about that ? It was just the result of the test I conducted. Sorry to look so stupid.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 27, 2023, 07:52:12
Should I remember you the previous messages in this thread where you complain about empty space instead of names ?
I don't take in account empty tags, ask this to someone else.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: arvernes on August 27, 2023, 07:58:05
Should I remember you the previous messages in this thread where you complain about empty space instead of names ?
I don't take in account empty tags, ask this to someone else.
Where in that sentence :
Quote
Quote
- Add phrase for death without details
it seems it works only for tag DEAT Y, not for tag DEAT if empty.
you can read a complaint on my side ? If you want to read one, that's ok, get the last word. Francois
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 27, 2023, 11:25:40
Hi all,

I have a NATI tag like this:

1 NATI Nederlander
2 DATE 1 JAN 1965
2 PLAC , Rotterdam, , Rotterdam, Zuid-Holland, Nederland
3 MAP
4 LATI N51.9225
4 LONG E4.47917
2 AGE 6m 26d

The report shows:
"He was in Rotterdam on 1 January 1965 at age 6 months 26 days."

There is no "Nederlander".
Gedcom 551 page 33 says:

n NATI <NATIONAL_OR_TRIBAL_ORIGIN> {1:1} p.56
+1 <<INDIVIDUAL_EVENT_DETAIL>>

NATIONAL_OR_TRIBAL_ORIGIN:= {Size=1:120}
The person's division of national origin or other folk, house, kindred, lineage, or tribal interest. Examples: Irish, Swede, Egyptian Coptic, Sioux Dakota Rosebud, Apache Chiricawa, Navajo Bitter Water, Eastern Cherokee Taliwa Wolf, and so forth.

So the text goes directly behind NATI (with a max of 120), and this is what the Gedcom editor creates.

For all other things done, works great!

Mother10

O, and I wondered, does the forum have any forum rules users have to respect?
I looked but could not find them.
Most forums have some rules somewhere.
But it could be we dont need them.

Otherwise i could mention them on the Dutch forum.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 27, 2023, 13:13:22
Add [1] to have the value of the tag in the label.
So, your translated line should be somehow like :
sentence.NATI=[SUBJECT] was [1][OPTIONAL_PP_P/isLACE][OPTIONAL_PP_DATE][OPTIONAL_PP_AGE].

Adjust to fit better in your language.

Zurga
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: mother10 on August 27, 2023, 13:19:54
Add [1] to have the value of the tag in the label.
So, your translated line should be somehow like :
sentence.NATI=[SUBJECT] was [1][OPTIONAL_PP_P/isLACE][OPTIONAL_PP_DATE][OPTIONAL_PP_AGE].

Adjust to fit better in your language.

Zurga

Ok i did. But it looks like the english original did not have it either.
Title: Re: Narrative lineage of ascendants or .../ Verhalende afstamming voorouders ....
Post by: Zurga on August 27, 2023, 13:28:44
Fixed.

Zurga