PB compound name about vesta_classic_laf HOT 7 CLOSED

This is by design because there are individuals (both my parents are actually among them, that's mainly why I changed this ;-) ) with a compound name where the preferred name is only the last part of the compound name.

See comment in code here.

In Vesta, you can either use two asteriskes (bit ugly because the hyphen isn't underlined in that case, maybe I should change that), or unicode 2011 'Non-Breaking Hyphen' instead of a standard hyphen.

from vesta_classic_laf.

but why webtrees have no problem ?

from vesta_classic_laf.

It's no easy to find and replace unicode 2011 'Non-Breaking Hyphen' instead of a standard hyphen when you are more than 10000 name.
I thinks a lot of french people don't want to modify the gedcom

from vesta_classic_laf.

It depends on what you consider to be 'the problem'. Webtrees originally had a problem here (see below).

In general, the semantics of the asterisk aren't well-defined (this is non-standard GEDCOM anyway).

Webtrees now supports an alternative solution, namely to use unicode 200C 'Zero Width Non-Joiner' in case you want to 'split up' the compond name for a common name. See this issue.
This is unfortunate because it is kind of the inverse of my solution.

from vesta_classic_laf.

It's no easy to find and replace

It's a single 'find-and-replace' operation, regardless of whether you have 10 or 10000 occurrences. (Of course you shouldn't do it manually)

But let me think about this a bit, I'll probably align with webtrees here and remove the Vesta adjustment.

from vesta_classic_laf.

Fixed in latest release (now works in the same way as in webtrees itself).

from vesta_classic_laf.

Test Ok
Thanks

from vesta_classic_laf.