Re: [Tools-discuss] <contact/>: asciiFullname should be latinFullname

[Martin Thomson <[e-mail]>]

I also agree with these fine folks.

There are reasons to show restraint.  And I thought that was what motivated very narrow rules.  For instance, we might not want quotes being anything other than '" because allowing variance leads to inconsistency.  Same for hyphen vs. en-dash and em-dash.  But the way to deal with that is to build tools that fix the issue one way or other.  xml2rfc is already aware of these problems and has some ability to manage that particular problem.  For instance, kramdown applies smart quotes from ", and then xml2rfc undoes that.

For the rest, a tool that highlights characters from outside a narrowly defined range (printable and whitespace ASCII for instance) would do wonders for ensuring that odd stuff doesn't creep in, like a BOM or a bunch of ZWNJ.  Beyond that, allowing people to have their names without having to resort to nasty hacks would be awesome.

On Wed, Oct 7, 2020, at 18:54, Julian Reschke wrote:
> Am 07.10.2020 um 08:51 schrieb Tom Pusateri:
> > ...
> > Another related question:
> >
> > How many times do we have to endure restrictions on UTF-8 characters in a UTF-8 document. Can we please just allow UTF-8 characters anywhere in a document?
> >
> > It’s not like we don’t have multiple levels of an editor process to resolve any issues with incorrect use.
> > ...
> 
> Indeed.
> 
> We shouldn't need a phrase-level "contact" element in the fist place.
> 
> Best regards, Julian
> 
> ___________________________________________________________
> Tools-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to [e-mail]
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to [e-mail]
>