Your message dated Wed, 26 Feb 2020 09:59:18 +0100
with message-id <[email protected]>
and subject line Done on the nm.d.o side
has caused the Debian Bug report #691628,
regarding Please put my family name before my given name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
691628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691628
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nm.debian.org
Severity: minor

Dear Front Desk members,

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

family-name   => 'Guo',
given-name    => 'Yixuan',
display-order => family-first

This could also be a solution:

family-name   => 'Guo',
given-name    => 'Yixuan',
full-name     => 'Guo Yixuan'

[1] https://nm.debian.org/public/person/[email protected]
[2] http://en.wikipedia.org/wiki/Chinese_name

Cheers,

Guo Yixuan

--- End Message ---
--- Begin Message ---
Hello,

I have split on the nm.debian.org database the LDAP-related fields from
the user information, and now it's possible to click on "Edit personal
information" on one's own page and set the full name properly.

This won't fix the situation with the Debian LDAP, but at least we're
not propagating the LDAP-enforced division to the rest of the site.

I'm closing this bug on nm's side, while I guess it remains an issue on
the LDAP side.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <[email protected]>

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to