Question Surnames full capitalization

I regularly import Gedcom from different sources and sometimes surnames are fully capitalized, sometimes not.
As a matter of consistency, I try to keep all surnames fully capitalized.

It would be very handy if as an additional "Data fix" it could be possible to "Capitalize all surnames", as unless mistaken I don't think webtrees allows automating this tasks?

You can change the display, rather than change the data.

Control panel -> Custom CSS and JS.
Add the following CSS:

The suggestion of Greg is much better than capitalizing the names. They should be written in the data in upper and lower case as usual. McNamara is ok, MCNAMARA is not ok for me.

Hermann is correct. On page 54 GEDCOM 5.5.1 explicity says: Capitalize the name of a person or place in the conventional manner— capitalize the first letter of each part and lowercase the other letters, unless conventional usage is otherwise. For example: McMurray.

Changing all surnames to all uppercase like in MCMURRAY would elevate an error to the new standard.

@Greg, what about implementing a data fix that allows an admin to correct the all uppercase surnames - providing the admin with a list of "surname=uppercase(surname)" and corresponding checkboxes so that surnames like MCMURRAY could be excluded from the bulk change and handled manually.

You can "fix" a single name using the search/replace datafix. e.g. "/SMITH/" => '/Smith/'.

(A more advance search would only do this on lines beginning "1 NAME")

But I can see complications trying to convert all names automatically.

We cannot convert certain letters to lowercase. For example, see en.wikipedia.org/wiki/Dotted_and_dotless_I

yann64 wrote:

It would be very handy if as an additional "Data fix" it could be possible to "Capitalize all surnames", as unless mistaken I don't think webtrees allows automating this tasks?

If you would like to find the records with capitalized surnames you could use a RegEx like
(2 SURN )([A-Z ]*$)

Bogie wrote:

If you would like to find the records with capitalized surnames you could use a RegEx like
(2 SURN )([A-Z ]*$)

That doesn’t work if, like me, you delete the completely redundant clutter of SURN (and every other subrecord of NAME except NICK and AKA).

It was only meant as a means for finding surnames all capitalized which was brought up by yann64.

What are you looking for?

fisharebest wrote:

… But I can see complications trying to convert all names automatically.

We cannot convert certain letters to lowercase. For example, see en.wikipedia.org/wiki/Dotted_and_dotless_I

Related: I recently encountered a large quantity of Greek text where a search function could not find word I knew were there. Eventually figured out every word that should have stated with one of the Greek letters ΕΥΙΟΚΗΑΖΧΒΝΜ instead started with the look-alike ASCII letter!

The problem with the Turkish "Iiıİİ ıs a flaw ın Unicode. They use the ASCII value for Ii which means that a capitalization routine would have to look at context to decide what to do.

They should have done what they did with Greek. Using different code points for glyphs that look the same allows this to work:

Sorry for reviving this old thread.

Here is the compromise I implemented on CSS: This way, we have a clear difference between first-names and surnames in languages where first-names can be used as surnames (like French).

yann64 wrote:

Sorry for reviving this old thread.

Here is the compromise I implemented on CSS:

Code:

<style> .SURN { text-transform: bolder } </style>

This way, we have a clear difference between first-names and surnames in languages where first-names can be used as surnames (like French).

I'll do you one better. Try this for bold and italics.

You could even give them a color if you wanted to like this.

In the clouds theme, text-transform: bolder had no visible effect.

font-weight: bold; (without italics) was just barely visible.

The same with the webtrees theme. With the webtrees theme there was no deference in the bold.

If you use one of those themes you could always use another color for the surnames like this.

For those that don't color codes you can do a web search for "color hex codes" and find lots of sites that list the codes.
Codes examples are like this for red #ff0000 for white #ffffff for black #000000. Always put a # before that numbers.