I am not replying to the most recent post, but to the one by Louis.
The first paragraph seems to be about the Help Afrikaans page. Since it is a Wiki page, those points have a greater chance of being edited into the page if posted there as public comments.
The intended logical meaning of Point 4 is that there should be one rule for a transcription and another for a database name. I.e. one should NOT copy from the transcription and paste it in the name field.
When you transcribe, you try to render the handwritten document as accurately as your skill can make it. Therefore transcriptions belong in the biography where any WIki genealogist can edit them, since nowadays, with UTF-8, much closer renderings than before are possible. For example, Rijnsbùrgh is a transcription that was closest when grave accents on selected vowels were available, but we now have breve accents on anything and can do Ry̆nsbŭrgh, which is much closer to the handwriting.
When you enter a database name (LNAB or FNAB) you want WikiTree to be able to find that profile when some reasonable approximation of the name is entered. For that purpose, Rijnsburgh is best, because "ij" is a well-known way of representing the Dutch long y in print, and the fact that the name definitely was not spelt Rensburg on that occasion is respected.
You are right about ASCII, I most definitely do mean that, but note my phrasing: A conscious effort be made to represent… I don't mean ASCII only MUST be used, I mean when it is deviated from, it is for a cogent reason, such as that the "common and correct spelling" of the name at the time required it.
Finally, PPP. It is a tool designed to resolve conflict, not a stamp of quality for a beautifully finished product. I would be among the first to argue that WIkiTree should have such a stamp and that project leaders should have the privilege of bestowing it (in fact, I am willing to start a general G2G on it). But read the requirements for PPP: it is a disciplinary measure first and foremost.
Project protection should be used only when profiles need protection — because they are commonly-shared, frequently-duplicated, subject to confusion, etc.
There must be some sort of controversy or duplication problem, or reasonable expectation that there will be. (My emphasis.)