On Sun, Oct 28, 2012 at 02:04:53AM +0800, Guo Yixuan wrote: > I just hope to have my name in the correct order on nm.d.o [1]. It's a > Chinese name, where the family name _precedes_ the given name[2], thus I > wish to keep this order in the latinized version. FYI, in Chinese > characters, my name is 郭溢譞, and it also appears in my pubkey uid as > comment. > > The best solution for this problem, IMO, is to have correct family/given name > and the display order in database, something like [...]
Thanks for the bug report. You solution would probably work, but an even better one is to directly store what we actually need: - a full name field - a transliterated full name field - a sortable version of the name: for example, my full name is "Enrico Zini", but in Italy we sort by family name first, so the sortable field would be "Zini, Enrico" - an informal way to address people in emails, like "Dear <name>," That would give: full name: Enrico Zini transliterated: (empty) sortable: Zini, Enrico informal: Enrico full name: 郭溢譞 transliterated: Guo Yixuan sortable: Guo Yixuan informal: Yixuan (I'm not sure this is correct) By default the fields can be initialized combining the existing first, middle and last names, and then one can fix it it when it's not correct, like in your case. However, and that's the reason I didn't try anything like that before, nm.debian.org is used to feed the Debian LDAP database, so it needs to have the same fields. Since we're talking about LDAP, I'm cc-ing debian-admin for comments. I'd be totally in favour of getting rid of the pointless first/middle/last name distinction, but there might be tradeoffs to be made given the existing infrastructure. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <[email protected]>
signature.asc
Description: Digital signature
