Re: [Tools-discuss] idnits 2.16.02 counts line length using bytes and not characters (but xml2rfc 2.34.0 line-wraps counting chars, not bytes)

[Henrik Levkowetz <[e-mail]>]

Hi Daniel,

Below:

On 2019-11-05 17:01, Henrik Levkowetz wrote:
> Hi Daniel,
> 
> On 2019-11-05 13:34, Daniel Kahn Gillmor wrote:
>> On Mon 2019-11-04 22:07:00 +0100, Henrik Levkowetz wrote:
>> 
>>> Agreed.  A rewrite of idnits which will do better in this respect is
>>> in progress.
>> 
>> great, thanks!
>> 
>> By the way, the incluson of UTF-8 characters has been really helpful for
>> this specific draft, as it permits pretty diagrams of MIME structure
>> that would be tedious to explain in text, or harder to follow visually
>> if we left out edges between parent and child nodes.
>> 
>> I really appreciate the work that goes into modernizing the IETF toolchain
>> to permit these improvements.
>> 
>> My only regret is that the htmlizer on tools.ietf.org seems to work from
>> the uploaded .txt variant, rather than building the html directly from
>> the .xml source.  "xml2rfc --html --v3" produces a document that is
>> *much* nicer to read (and better structured from an HTML point of view)
>> than the htmlized txt source.
>> 
>> Is there any plan to generate the HTML from the uploaded xml in this way
>> for future documents?
> 
> If you submit v3 XML, HTML is already being generated from the XML.
> 
> Right at the moment, it looks like the net (or wider area?) that
> datatracker.ietf.org lives on is unreachable (I see this for multiple
> machines in the same geographic area) but when it's reachable again,
> you should see a link to the generated html on the datatracker page
> for the document, and you should also find it next to the .txt and
> .xml files in the repository:
> 
>   http://www.ietf.org/id/draft-autocrypt-lamps-protected-headers.html

Mmm.  That lacked the necessary version number, so was incorrect.  I also
see that the XML file is not pure v3, so HTML won't be generated by the
submission tool.

If you run the current XML file through 'xml2rfc --v2v3 ...' you should get
a pure v3 file you can use for future work.


Best regards,

	Henrik