Re: [xml2rfc] Tables in XML V3 - A downgrade

[Anders Rundgren <[e-mail]>]

Hi Julian,

On 2019-09-14 07:25, Julian Reschke wrote:
> On 14.09.2019 07:08, Anders Rundgren wrote:
>> On 2019-09-13 18:45, Julian Reschke wrote:
>>> On 13.09.2019 17:25, Anders Rundgren wrote:
>>>> ...
>>>> Well, RFC 7997 only talks about Unicode in author-provided data which is
>>>> not the case here.
>>>> The same goes for bullets lists.
>>>> ...
>>>
>>> I think we need to look at the role of the plain text output in the
>>> future. The original plan was to make it as bare as possible, not even
>>> paginated. Not sure why we deviated from that.
>>
>> Paginated RfcMarkup is rather reducing readability and browsers can
>> print fairly well these days.
> 
> Print plain text?

I just thought that pagination was intended for that purpose.
If not pagination has no purpose.

> 
>> RfcMarkup seems to be the current standard for communicating RFC.
>>
>> Making HTML the standard probably requires more work and PIs.  XHTML is
>> deprecated.
> 
> The "standard" is XML, in that the XML document is normative. HTML will
> be generated from it.

Sure, XML is the standard for creating RFC, I was rather referring
to links to published RFCs used everywhere.

HTML is currently NOT generated for V3 submissions.

> I don't get your point about PIs, nor the one about XHTML.


Since you as an author would like your precious text to be rendered
as good as possible, I guess that SVG would not be a part of RfcMarkup
making "line-art" variants a necessity.

PIs could be used to keep the XML intact.

XHTML is a deprecated W3C standard currently used by RFCs.  It is not
a problem but switching to HTML5 is preferable.

> 
>> New problems:
>> ------------
>> BTW, my recent XML V3 submission did not generate an HTML version at all!
>> My previous XML V2 submissions did this automatically.
>>
>> The HTML output for Web tool doesn't produce any output. It says it
>> doesn't find the file :-(
>> The URL input began to fail:
>> https://raw.githubusercontent.com/cyberphone/ietf-json-canon/gh-pages/xmlv3/draft-rundgren-json-canonicalization-scheme.xml
> 
> My local install of xml2rfc dies with a stack trace, one issue is the
> use of
> <https://greenbytes.de/tech/webdav/rfc7991.html#element.dl.attribute.spacing>
> which has been removed/changed but not yet documented in rfc7991bis.
> 
> Even after removing those, xml2rfc dies with:
> 
>> Traceback (most recent call last):
>>    File "/bin/xml2rfc", line 10, in <module>
>>      sys.exit(main())
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/run.py", line 595, in main
>>      writer.write(filename)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 253, in write
>>      html_tree = self.html_tree()
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 231, in html_tree
>>      html_tree = self.render(None, self.root)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 309, in render
>>      res = func(h, x)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 625, in render_rfc
>>      self.render(body, c)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 309, in render
>>      res = func(h, x)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 1546, in render_front
>>      entry(dl, 'Workgroup', wg.text)
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 1511, in entry
>>      dl.append( build.dd(*values, classes=cls))
>>    File "/usr/lib/python2.7/site-packages/xml2rfc/writers/html.py", line 93, in __call__
>>      elem = super(ClassElementMaker, self).__call__(tag, *children, **attrib)
>>    File "src/lxml/builder.py", line 226, in lxml.builder.ElementMaker.__call__
>> TypeError: bad argument type: NoneType(None)
> 
> You should submit a bug report.
> 
> Best regards, Julian
> 
> 
> 
>