calros wrote:I think I created this name. The problem is: the character (mandarin) is very rare, so rare that our DB transliterator has not it in its character map. So it cannot be "transliterated" and it has not an "alternate form", so I cannot fix it.
Characters contain no such property of being "mandarin". Simplified characters are also used in places where Cantonese is spoken (i.e., Guangdong), and traditional characters are used in places where Mandarin is spoken (i.e., Taiwan).
As for how to handle this character, just like any other, I suggest following this procedure (that I have already outlined numerous times elsewhere):
Do you see the character in here?
http://hkmdb.com/phpbb/viewtopic.php?t=42330
No, you do not....so what does that tell you?
That tells you it's NOT in the Big5 character set.
Therefore it is almost certainly not a traditional character. (And indeed if you look at the GB character set, it IS in there).
What Chinese character set does this site use? Big5 (Traditional characters).
What Chinese character set does this site not (yet) do? GB (Simplified characters).
When you enter a GB character into the Big5 field, what do you expect the system to do? Read your mind?
At this point the best thing to do is attempt a GB->Big5 conversion. Well, this is a very rare case where that will not work, as there is no Big5 analog.
Now the problem is doing the romanization. Well, that's yet another reason why I added the transliteration override feature. So on this page, in the Cantonese and Mandarin romanization fields, IF AND ONLY IF you know how the person's name is pronounced, then enter the appropriate romanization(s) for this person:
http://hkmdb.com/db/people/edit/basic/e ... y_set=big5
(which I have already done)
That then leaves the only remaining issue of the broken/incorrect gif image...which I will eventually be replacing, since most modern systems/OS/browsers can handle 2 byte characters properly.
If all else fails, contact me and I can usually fix the problem.