|
|
|
|
Customers
FamilyTrees.GenoPro.com
Important Contributors
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, June 10, 2025
Posts: 214,
Visits: 3,623
|
Often happens to acquire the data in different ways, case-sensitive. This happens particularly in the fields: " first name", "Middle name" and "Last Name". You can think of a function to make uniform the three fields, following the acquisition, through a general choice between "ALL CAPS" or "Only Initial Caps", regardless of how the data have been acquired?
Thank you for your attention and patience.
Vittorino Lepore
"Se non porti almeno una soluzione, anche tu fai parte del problema" or "If you don't bring at least a solution, even you're a part of the problem"
|
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 10:55 PM
Posts: 1,590,
Visits: 32,102
|
Options at present are to export to a spreadsheet to make case changes.
Also you can use Find & Replace in the table column eg change LEPORE to Lepore.
Useful for a large amount of data (eg from gedcom) but agree that as a feature it is one I have often missed.
However I often leave gedcom data in caps as an indication that it is secondary data and needs to be checked
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 10:52 AM
Posts: 3,436,
Visits: 26,607
|
This is indeed a common problem. I have had to do this the long way in the past using Find & Replace - not much fun!"Only Initial Caps" is a little tricky because of all the exceptions e.g. Scottish/Irish/Celtic? Mac & Mc prefix and prepositions de da du di von van etc. However I have found a Perl script that seems to cover much of it. I will see if I can convert it to Javascript and include it in the Toolkit. No Javascript Macro feature in GenoPro as yet to allow it to be actioned more directly.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 10:55 PM
Posts: 1,590,
Visits: 32,102
|
As a matter of interest, how does it deal with Macintosh?
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 10:52 AM
Posts: 3,436,
Visits: 26,607
|
I have haven't run the code as yet, but it appears anything beginning with 'macin' is set to 'Macin' so Macintosh, and incidently Mackintosh, which appear to be the norm but also Macintyre where I find that MacIntyre is more common, although Macintyre does occur.I will only convert when the name is all upper case so that any existing variations are preserved. There also will be an option to convert Names to upper case.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
Important Contributors
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, June 10, 2025
Posts: 214,
Visits: 3,623
|
My problem is not aesthetic, but I would avoid the unnecessary duplication of surnames in the file toc_individuals.htm. For this same reason, we should eliminate all the "blank" end of text of all fields. Also These "blank" causes unnecessary duplication of Surnames and Places. The problem is not present in files of 2-300 individuals, but only in very large files,
acquired by different people and at different times!
"Se non porti almeno una soluzione, anche tu fai parte del problema" or "If you don't bring at least a solution, even you're a part of the problem"
Edited: Thursday, February 5, 2009 by
vlepore
|