J Palotay. Thank you for your observations about the difficulties involved in aiming for some level of orthographic standardisation.
A few thoughts on this:
1. Just because effort is involved possibly even involving frustration, this is not uncommon in any worthwhile area of human endeavour.
2. My observations are not seeking perfection, but improvements to make WikiTree more useful by being more standardised at the initial entry level and reserving variants for their proper place, i.e. the place where they can be best addressed, which is the notes.
3. It is unlikely that in any of the 461 instances I noted, Freidrich better reflects the individual concerned’s identity, historical or for present-day research purposes or living descendants, than standard Friedrich. Why? Because the former breaks basic rules of German established over half a millennium ago as another poster pointed out.
4. This brings me to another consideration raised by you. The appearance of people under other guises (mostly spellings since these are what have come down to us) in other languages, dialects, regions, and cultures. These are either for the notes or possibly for multiple listings as separate but linked initial entry points to the database. This is particularly useful and obvious when dealing with widely known historical figures such as St Stephen, the first Christian king of Hungary, whose name appears in Hungarian (naturally enough), but also in English, as well as in possibly all other European languages, and doubtless others as well.
It would be useful the case of many immigrant ancestors to other cultures to list their name(s) in the country and/or culture of origin as well as destination, and possibly also F transit between the two. Consider the case of a German born in Russia whose given name was Vincenz in his mother tongue but found in Russian records as Vikenty when transliterated from the Cyrillic to the Roman alphabet (one of several possible renderings because there are several conventions for transliteration just in English, which vary from from language to language), but written in a passport created for his emigration in both Russian and French as the Russian form and as Vincent, which happens to match the form in English in both America and in the United Kingdom and its offshoots. But our fellow settles in the Bronx and is called Vince by his new neighbours some of whom speak none of the languages mentioned as their first language. This is written down by his Polish neighbour as Winz because that’s how it sounds to him and how he chooses to write it in his mixed knowledge of Polish and English. He keeps the W of Polish which says English ‘v’, and the ‘z’ represented by English ‘ce’, but doesn’t employ a hooked vowel which he might in Polish for a n-sound preceding a consonant, possibly because he recalls that in Polish, St Vincent is familiar Wincenty. Don’t get me started on Magyar as I will probably make a hash of Juhasz which unlike Polish pronounces ‘sz’ as ‘s’ not ‘sh’.
What should be done with entries in other scripts? I looked at the list of new honor [sic] code signatories a day or so ago, and spotting some with what appeared to me to be a Chinese name, generated his or her tree. It was entered almost entirely in Chinese characters. I was none the wiser. Wouldn’t it be delightful to have an automated system that allowed me to view this in Pinyin or Wade-Giles, or some other system of transliteration into the Roman alphabet? Now that would be helpful but would preserve the integrity of the linguistic reality of the people recorded.
With the immigrant Vincenz, Vikenty, Vince, one could employ an option which it might be possible to create: an ability to toggle between languages one could designate for the profile or make optional for all profiles: multiple language name profiles or entries.
With the technology this is possible. Indeed one could allow for the appearance of minority or alternate designations for folk, such as St Bede for Roman Catholics or those wishing to see the Roman Catholic naming designation for someone known to a wider audience by his older and still valid Anglican (and other) form, The Venerable Bede.
WikiTree needs to be culturally sensitive too. The nonsense of H.M. Camilla R. Mountbatten-Windsor KG (etc.) for the profile name of H.M. The Queen Consort is a complete WikiTree neologism and a solecism. It contains a dog’s breakfast of specious naming conventions and American usage. The style H.M. is correct, but then it is wrongly combined with her first Christian name followed by an Americanism, her middle name represented by an initial followed by a full stop. Then the supposed married surname is misrepresented as though Her late Majesty Queen Elizabeth II’s 1960 ruling that the name of the Royal Family is Windsor has never occurred and didn’t still obtain (it dies per the Royal Family’s website). Exception are only for members of the Royal House apart from the King and Queen Consort who do not already enjoy the style of H.R.H. and the rank of Prince or Princess of the United Kingdom of Great Britain and Northern Ireland, or who require a surname for the purposes of a certificate such as a marriage certificate as in the case of Princess Anne (as was) on the occasion of her 1973 marriage to Capt. Mark Phillips. The King wed Mrs Camilla Rosemary Parker Bowles (not Parker-Bowles as her former husband’s and father-in-law’s WikiTree profiles read yesterday when last I checked) as H.R.H. The Prince Charles, Prince of Wales, not as H.R.H. Charles P. A. G. Windsor KG (etc.), much less as Mountbatten-Windsor. Until 1917 the Royal Family had no surname, just a dynastic or house name set off by a preposition, of in English, von (or more conventionally v.) in German. WikiTree makes a hash of this and other culture’s and people’s naming conventions, insensitively and needlessly shoe-horning them into a one-size fits all template, while errantly insisting on a silly rule about names as first instanced in documents. Talk about topsy-turvy priorities.
Regards,
Upton