Search found 27591 matches
- 25 Apr 2024 13:17
- Forum: Importing
- Topic: Creating an import file from scratch
- Replies: 2
- Views: 59
Re: Creating an import file from scratch
Welcome to the FHUG Richard. A significant part of genealogy data you did not mention is Source Citations that support your family data. i.e. the Birth/Marriage/Death Certificates and Census records that prove the family facts you have recorded. Many users often find it useful to enter all their fam...
- 24 Apr 2024 21:16
- Forum: Sources, Citations & Repositories
- Topic: Creating a concatenated field in SOURCES in Records Window
- Replies: 6
- Views: 124
Re: Creating a concatenated field in SOURCES in Records Window
Yes, if the separator is a comma, then the TextPart(...) function works similarly to the Section(...) function.
TextPart(...) also has extra features for tidying and arranging the comma-separated parts.
TextPart(...) also has extra features for tidying and arranging the comma-separated parts.
- 24 Apr 2024 20:28
- Forum: Sources, Citations & Repositories
- Topic: Creating a concatenated field in SOURCES in Records Window
- Replies: 6
- Views: 124
Re: Creating a concatenated field in SOURCES in Records Window
Ok, you are very close. I think the following may be what you want but there are some caveats. =Text( %SOUR.~NM-Principal:SURNAME_FIRST% . ": " . Section( %SOUR%, 1, "," ) . " " . %SOUR.~DT-Date:YEAR% ) %SOUR.~NM-Principal:SURNAME_FIRST% will display the Surname, a comm...
- 24 Apr 2024 17:55
- Forum: Sources, Citations & Repositories
- Topic: Creating a concatenated field in SOURCES in Records Window
- Replies: 6
- Views: 124
Re: Creating a concatenated field in SOURCES in Records Window
Please confirm whether you would be happy to simply reformat the Source Record Title or not.
- 24 Apr 2024 17:46
- Forum: Plugin Technical Support & Development
- Topic: Possible error in Clean up Surname Capitalisation Plugin
- Replies: 17
- Views: 306
Re: Possible error in Clean up Surname Capitalisation Plugin
To add a Record Id to the final Result Set ... About line 95 add a table variable to hold the Record Id: tblRecord = {} tblRec_Id = {} About line 115 save the Record Id in the table: table.insert(tblRecord,pi:Clone()) table.insert(tblRec_Id,fhGetRecordId(pi)) About line 128 display Record Id in the ...
- 24 Apr 2024 15:05
- Forum: Reports, Books & Websites
- Topic: Ancestors by Generation
- Replies: 6
- Views: 186
Re: Ancestors by Generation
Yes, {individual} experienced {label} ... is the default Sentence Template for a new custom Event or one without a definition.
- 24 Apr 2024 14:11
- Forum: Plugin Technical Support & Development
- Topic: Possible error in Clean up Surname Capitalisation Plugin
- Replies: 17
- Views: 306
Re: Possible error in Clean up Surname Capitalisation Plugin
Just to be clear, the extra symbols and diacritic letters supported by ANSI coding are only: € ‚ ƒ „ … † ‡ ˆ ‰ ‹ Æ æ Œ œ ‘ ’ “ ” • – — ™ › ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ × ÷ Þ þ ß Ð ð nbsp À à Á á  â à ã Ä ä Å å Ç ç È è É é Ê ê Ë ë Ì ì Í í Î î Ï ï Ñ ñ Ò ò Ó ó Ô ô Õ õ ...
- 24 Apr 2024 11:09
- Forum: Plugin Technical Support & Development
- Topic: Possible error in Clean up Surname Capitalisation Plugin
- Replies: 17
- Views: 306
Re: Possible error in Clean up Surname Capitalisation Plugin
Ok, the following two changes should be sufficient, unless your Surnames use foreign language characters. Near line number 16 add three lines after iup.SetGlobal("CUSTOMQUITMESSAGE","YES") to cope with UTF-8 require("iuplua"); iup.SetGlobal("CUSTOMQUITMESSAGE"...
- 24 Apr 2024 10:43
- Forum: Plugin Technical Support & Development
- Topic: Possible error in Clean up Surname Capitalisation Plugin
- Replies: 17
- Views: 306
Re: Possible error in Clean up Surname Capitalisation Plugin
John, you can edit the plugin yourself to make any necessary changes.
One of us could advise what changes to make once you are familiar with the editing process.
Alternatively, you must wait until Jane notices this thread and updates the plugin in the Plugin Store.
One of us could advise what changes to make once you are familiar with the editing process.
Alternatively, you must wait until Jane notices this thread and updates the plugin in the Plugin Store.
- 24 Apr 2024 10:11
- Forum: Plugin Technical Support & Development
- Topic: Possible error in Clean up Surname Capitalisation Plugin
- Replies: 17
- Views: 306
Re: Possible error in Clean up Surname Capitalisation Plugin
FYI: The plugin is using iup.GetText(...) which displays a modal dialog to edit multiline text. The idea is that the user reviews and corrects each surname listed. However, in Lua the default maxsize is 10240 characters, so I believe the dialog is being truncated. So it is currently not possible to ...
- 24 Apr 2024 09:39
- Forum: Reports, Books & Websites
- Topic: Ancestors by Generation
- Replies: 6
- Views: 186
Re: Ancestors by Generation
I have moved this from the Diagrams & Charts forum to the Reports, Books & Websites forum which is more appropriate. The explanation for that narrative sentence is that the Fact Type definition for the General Event is missing or needs refining. Use Tools > Fact Types... and then if possible...
- 22 Apr 2024 19:41
- Forum: Plugin Technical Support & Development
- Topic: Name capitalisation and parts check
- Replies: 11
- Views: 817
Re: Name capitalisation and parts check
The 'safe' plugin script solution is to cater for every :match(...) operation possibly returning nil . Don't assume that such a match will always be successful, i.e. use defensive programming techniques. Similar techniques should be applied to all other operations to avoid unexpected failures. In th...
- 22 Apr 2024 19:37
- Forum: Plugin Technical Support & Development
- Topic: Name capitalisation and parts check
- Replies: 11
- Views: 817
Re: Name capitalisation and parts check
Yes, that is the same cause for the error.
The NSFX = POLLARD/ which is the trailing part of the NAME field and includes the slash /
So when the 'suffix' POLLARD/ is removed from Ella Loretta /POLLARD/ it leaves Ella Loretta / which does not contain two slashes and that causes the fault.
The NSFX = POLLARD/ which is the trailing part of the NAME field and includes the slash /
So when the 'suffix' POLLARD/ is removed from Ella Loretta /POLLARD/ it leaves Ella Loretta / which does not contain two slashes and that causes the fault.
- 22 Apr 2024 09:36
- Forum: Plugin Technical Support & Development
- Topic: Questionable name capitalisation
- Replies: 14
- Views: 1911
Re: Questionable name capitalisation
I discovered that fault arises under the following (unusual) conditions:
Name (INDI.NAME): Ian Steve /Munro/ Junior
Name Suffix (INDI.NAME.NSFX): Munro/ Junior
i.e. The Named Suffix field holds the trailing section of the Name field including a slash /
Name (INDI.NAME): Ian Steve /Munro/ Junior
Name Suffix (INDI.NAME.NSFX): Munro/ Junior
i.e. The Named Suffix field holds the trailing section of the Name field including a slash /
- 22 Apr 2024 09:04
- Forum: Sources, Citations & Repositories
- Topic: Report sources not showing some fields
- Replies: 11
- Views: 799
Re: Report sources not showing some fields
Yes, that is a good find from 2+ years ago!
- 21 Apr 2024 21:33
- Forum: Sources, Citations & Repositories
- Topic: Report sources not showing some fields
- Replies: 11
- Views: 799
Re: Report sources not showing some fields
Yes, I think that is the only manual method available and must be applied one Citation at a time.
To make a large number of changes in bulk will require a custom plugin to be written.
To make a large number of changes in bulk will require a custom plugin to be written.
- 21 Apr 2024 21:22
- Forum: Diagrams & Charts
- Topic: Married cousins
- Replies: 1
- Views: 151
Re: Married cousins
I think the following is the explanation but without seeing the diagram it is difficult to be certain. When cousins marry they bridge across generations so their relatives have two relationships to the other members of the family tree. The duplications illustrate where such people fit into their two...
- 20 Apr 2024 23:09
- Forum: Reports, Books & Websites
- Topic: Publish a Narrative Report for the Paternal Line only of my ancestors
- Replies: 6
- Views: 973
Re: Publish a Narrative Report for the Paternal Line only of my ancestors
You could create a copy of your master Project and delete the maternal line of ancestors.
Then the report will only include the paternal line.
Then the report will only include the paternal line.
- 20 Apr 2024 19:01
- Forum: General Usage
- Topic: Internet data matches
- Replies: 2
- Views: 162
Re: Internet data matches
The choice is yours. In Internet > Internet Data Matches... the Settings have the following options for both FMP and MH: 1) Enabled for all Projects except those with 3) selected 2) Disabled for all Projects 3) Disable for this project only The hints are only active for the people shown in the curre...
- 20 Apr 2024 16:24
- Forum: Diagrams & Charts
- Topic: Displaying Icons for more than 1 Record Flag
- Replies: 2
- Views: 147
Re: Displaying Icons for more than 1 Record Flag
Yes, you must use Condition > Expressions instead of Condition > Record Flag
Use the << Insert Data Ref... button to add Individual > Flags one at a time, e.g. %INDI._FLGS.__LIVING%
Then the order of the Conditions determines the order of the icons.
Use the << Insert Data Ref... button to add Individual > Flags one at a time, e.g. %INDI._FLGS.__LIVING%
Then the order of the Conditions determines the order of the icons.
- 18 Apr 2024 19:06
- Forum: Sources, Citations & Repositories
- Topic: Citation Specific Details in Queries
- Replies: 8
- Views: 295
Re: Citation Specific Details in Queries
That will refer to whatever happens to be the 1st Templated metafield in each Citation.
To refer to them by name see the Help for Understanding Data References and scroll down to Data References And Metafields as I explained earlier.
To refer to them by name see the Help for Understanding Data References and scroll down to Data References And Metafields as I explained earlier.
- 18 Apr 2024 15:51
- Forum: Sources, Citations & Repositories
- Topic: Citation Specific Details in Queries
- Replies: 8
- Views: 295
Re: Citation Specific Details in Queries
They had to be Templated Sources because Citation Detail and Reference are not Generic fields.
BTW: Once you create a Query it is immediately saved. You would have to specifically delete it.
You can use any existing Query to interrogate the Fields DRA without affecting the Query.
BTW: Once you create a Query it is immediately saved. You would have to specifically delete it.
You can use any existing Query to interrogate the Fields DRA without affecting the Query.
- 18 Apr 2024 15:11
- Forum: Sources, Citations & Repositories
- Topic: Citation Specific Details in Queries
- Replies: 8
- Views: 295
Re: Citation Specific Details in Queries
Unfortunately, the Query > Columns tab > Fields pane does not support Templated Named Metafields. Please refer to the Help for Understanding Data References and scroll down to Data References And Metafields . There it explains the data reference structure for metafields. e.g. %FACT.SOUR[1].~TX-REFER...
- 18 Apr 2024 14:54
- Forum: Diagrams & Charts
- Topic: Standardized Place in Diagram
- Replies: 2
- Views: 238
Re: Standardized Place in Diagram
%FAMS.MARR[1].PLAC>STAN% is almost a perfectly correct Data Reference for the Standardized field. %CUR~FAMS>MARR.PLAC>STAN% is what you should use for the Marriage Standardized place. However, it is not allowed in the position you have used in a =FactText(...) function, so is ignored. The =FactText...
- 17 Apr 2024 19:40
- Forum: Research
- Topic: 1881,1891,1901 CENSUS BIRTHS DIFFERENT
- Replies: 7
- Views: 432
Re: 1881,1891,1901 CENSUS BIRTHS DIFFERENT
It might help if you could post screenshots of the Marriage Certificate and 1881 Census. See the FHUG Knowledge Base > Forum Usage under Attachments and Taking Screenshots for how to do that. Are you looking in Census records for a William about the right age with father John and mother Jane? Try th...