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

[Alexandre Petrescu <[e-mail]>]

Le 10/03/2020 à 16:10, Julian Reschke a écrit :
> 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?

I have tried to write people's names in the Ack section.  "ä" became 
"ae".  Japanese characters got un-understandable - scrambled in a 
strange way.

Then, from private feedback, I tried to put <contact fullname="Ole Trøan 
(Ole Troan)."/> in the Ack section.

The xml2rfc.tools.ietf.org complains this:
Error: Unable to validate the XML document: INPUT
  <string>: Line 1439: Element contact is not declared in t list of 
possible children
  <string>: Line 1440: No declaration for element contact
  <string>: Line 1440: No declaration for attribute fullname of element 
contact

The xml file is local on my Windows 10 computer but is shared on a 
github repository with an application called "Github Desktop".

>>> 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.

I tend to agree with that.

I tried testing xml2rfc with a local file, or with the same file stored 
through github.  The result is the same, independently whether is on 
github or not on github.  The error is the following:

Source:
>       <t>
> 	Ole Trøan, 神明達哉 (TATUYA Jinmei), Jérôme Härri.  It
> 	     would be great if xml2rfc could compile these characters
> 	     ok.  People's names are probably the most important thing
> 	     in an I-D.
>       </t>

Compilation results in:
> 
>    Ole Troean, &#31070;&#26126;&#36948;&#21705; (TATUYA Jinmei), Jerome
>    Haerri.  It would be great if xml2rfc could compile these characters
>    ok.  People's names are probably the most important thing in an I-D.

That is why I think I agree with you.  I was wrong saying github has an 
error in accents.  It might be the problem is xml2rfc, actually.

> 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.

Thank you for the explanation.  I dont really understand it fully, but 
it looks understandable.

For my part, it would be great if accents were ok in the Ack section.

(I have other complaints to xml2rfc, like xml2rfc.tools.ietf.org's 
*.txt.pdf output file names, about which I got suggested to register to 
tools-discuss email list and suggest it there; one day).

Alex

> 
> Best regards, Julian