You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My name, in the Unicode format, is 홍용민, and this is conformant to the Korean name format of FamilyName+FirstName without space.
(Quoting Wikipedia)
When a Korean name is written in Hangul, there is no space between the surname and the given name.
However when I set this as my Full Name (Unicode), Public Profile behaves weird, saying "has no RFCs as of 2024-11-12.". If I add space between FamilyName and FirstName (making it 홍 용민, it becomes "홍 has no RFCs as of 2024-11-12.". So I think it is assuming space to differentiate firstname and lastname (in US/Western European terms), which is probably the wrong assumption.
We have a collection of issues forming around mal-assumptions made when dissecting names. Apologies that you are running into this. We'll look at incremental improvement, but in the long run I believe we should simply stop trying to break names into pieces.
Also please make sure the ascii (should say roman script) version of your name is configured in a way that makes sense. (The IETF does its work in English, and for non-roman scripts, name mentions in places like references are required to carry a roman script equivalent).
I tend to use Caps Lock on my family name, to signify it's not the First Name but a Last Name (and I usually insist on using FamilyName FirstName format even in roman scripts), but sure, modified to usual way of FirstName LastName.
Describe the issue
My name, in the Unicode format, is
홍용민
, and this is conformant to the Korean name format of FamilyName+FirstName without space.However when I set this as my
Full Name (Unicode)
, Public Profile behaves weird, saying "has no RFCs as of 2024-11-12.". If I add space between FamilyName and FirstName (making it홍 용민
, it becomes "홍 has no RFCs as of 2024-11-12.". So I think it is assuming space to differentiate firstname and lastname (in US/Western European terms), which is probably the wrong assumption.Code of Conduct
The text was updated successfully, but these errors were encountered: