Some email addresses show in an ugly way

[ietf-svn-bot]

resolution_fixed type_cleanup | by housley@vigilsec.com

---

The document page for draft-ietf-6man-rfc4941bis says that comments should be sent to: "=?utf-8?q?Ole_Tr=C3=B8an?= otroan@employees.org". This is probably a fine email address, but it is not bery friendly presentation.

---

Issue migrated from trac:3079 at 2022-03-04 08:00:37 +0000

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

I note that Ole Trøan himself has pasted in the string as shown. The datatracker does appropriate encoding of non-ascii names when sending mail, so there should be no need to paste in an already-encoded string (but it's quite likely that further encoding of that string will happen when trying to use this address). The right thing would be to instead make it "Ole Trøan" otroan@employees.org. I don't know if Ole had any particular reason to input it as he did; whether he wanted to test something or what...

[ietf-svn-bot]

@otroan@employees.org commented

---

Actually it isn't any pasting involved. It's a search field and you pick the shepherd with name/email address from a drop-down list.

Thanks for taking notice!
IETF tools aren't particularly good at anything but 7-bit ascii.
E.g. my name badge has had the letter after the "oslash" capitalized for the last 20 years. ;-)

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Aha. I see. You set the "Shepherd" field, and that in turn caused the notification field (which is where the encoded name occurs) to be set. Right. I've checked the code, and it incorrectly uses the encoded email name+address. I'm fixing this for the next release. Thanks!

[ietf-svn-bot]

@henrik@levkowetz.com changed status from new to closed

[ietf-svn-bot]

@henrik@levkowetz.com changed resolution from `` to fixed

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Fixed in 0fa1500:

Changed the format of email addresses added to the document notifications filed when the document shepherd is set. Fixes issue #3079.