Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml

[Henrik Levkowetz <[e-mail]>]

Hi Megan,

On 2017-11-02 15:18, Megan Ferguson wrote:
> Hi Henrik,
> 
> Input file: draft-ietf-nfsv4-xattrs-06
> Version: 1.3.0 (we still need to update to 1.3.1)
> Issue: Table markup in xml
> Files available:
> https://www.rfc-editor.org/rfc/v3test/draft-ietf-nfsv4-xattrs-06.original
> https://www.rfc-editor.org/rfc/v3test/draft-ietf-nfsv4-xattrs-06.txt
> https://www.rfc-editor.org/rfc/v3test/draft-ietf-nfsv4-xattrs-06.xml
> 
> Note: I didn’t include a diff as the text output is the same as the
> .original version.

Ack, right.

> Section 8.4.5. includes a table that is marked up in xml a bit
> differently than we expected.
> 
> The text output is the same when using the current version of
> xml2rfc, but instead of creating a continuous comma-separated list in
> <c> tags, it has generated <c> tags for each line.

Hmm, right.

> We are concerned
> about how this table would be handled by v3 as well as other formats
> (html for example). To try to work around, we added blank lines above
> and below and tried separating the entries using +— lines between
> them (to no avail). Is there another way to make this table work
> (other than copying the figure in as <artwork>)?

I see the problem.  I'm not sure there's a way for the converter to know
for sure whether the lines should be part of one single cell, or should
be separate cells (the way it's done now).

Handling this as <artwork/> would not be good.  It's possible that the
only really good handling would be to manually remove all the extra
<c> and </c> tags from the xml.

I'll see if I can tweak id2xml somehow, though.


Best regards,

	Henrik