Re: [Tools-discuss] submit and IDNits issue with draft-ietf-avtcore-multi-party-rtt-mix-12

[Gunnar Hellström <[e-mail]>]

Thanks Carsten for good answers.

So, then the only remaining issue is if the submission form can be 
modified to prefer xml and not accept both xml and txt files. Or the 
tool be modified to accept non-ascii in txt files.

(and also for IDnits to not warn for non-ascii as you promised in 
earlier discussions is on its way)

Gunnar

Den 2021-02-11 kl. 10:55, skrev Carsten Bormann:
>> Questions:
> (My) Answers:
>
>> 1. Can this problem be bypassed for now by just submitting the xml file including a reference to RFC 8865?
> Yes.
>
>> 2. Will the submit tool be updated to allow non-ascii contents in txt files, so that others referencing e.g. RFC 8865 will not be stopped by errors in the submission?
> (Don’t know.)
>
>> 3. RFC 7997 recommends to let a non-ascii string be followed by a corresponding ascii string in parenthesis. That will look awkward for this case where the non-ascii is "Hellström" and the evident corresponding string is "Hellstrom". Should the author in RFC 8865 have been "Hellström (Hellstrom)" or is it up to the editor to assess the need for the explaining parenthesis?
> The current state, as hinted at in https://xml2rfc.tools.ietf.org/xml2rfc-doc.html
> is that Latin script is generally allowed in the places where RFC 7991 uses the term ASCII, except in running text (a specification limitation that I hope will soon be addressed); and that non-Latin script requires an ASCII equivalent, so that if somebody is called “毛泽东” the reader gets to know that they could try to remember that name as “Mao Zedong”.
>
> The ö in Hellström is Latin script, as are č and ć in the name Mališa Vučinić, so you can “read” that (even if you have no clue what the difference in pronunciation is going to be :-)
>
> Grüße, Carsten
>
-- 
Gunnar Hellström
GHAccess
[e-mail]