Re: [Ietf-and-github] [Last-Call] Genart last call review of draft-ietf-git-using-github-04

[Julian Reschke <[e-mail]>]

On 10.03.2020 15:50, Alexandre Petrescu wrote:
>
>
> Le 10/03/2020 à 15:36, Julian Reschke a écrit :
>> On 10.03.2020 06:50, Martin Thomson wrote:
>>> ... Yes.  The whole charset thing is difficult, but if you use
>>> UTF-8 and Unicode you will find that things just work.  In most
>>> cases, you don't even have to make an effort to do so because
>>> modern software has largely left the baggage of the past behind.
>>> We've recently added the real names of contributors to the QUIC
>>> specs and it just worked. ...
>>
>> Well.
>>
>> That's a stretch. AFAIU, you used an experimental feature in xml2rfv
>> ("<contact>"), which is not even documented yet, and which might
>> change in the future.
>
> I need perfect accents in the Ack section, not in the list of Authors or
> Contributors.  Often Ack'ed people make more significant contrib or
> similar.
>
> <contact> does not work in the Ack section, I just tried.

It's supposed to work there. What *exactly* did you try?

>> Things would be easier if xml2rfc did not insist on having non-ASCII
>> characters only appear within certain markup constructs. In that case
>> it really would be a case of "it just works".
>
> Do you mean that me not being able to use ö in Ack section is a mistake
> of xml2rfc, and not a mistake of github?

github has nothing to do with that.

The developer of xml2rfc has chosen to restrict non-ASCII characters
further than defined in RFC 7991, essentially allowing them only in
artwork/sourcecode and a few new special constructs. The intent of RFC
7991 was to just allow them everywhere, and let the RFC Production
Center deal with overuse.

Best regards, Julian