Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple defects in the cli #37

Closed
ietf-svn-bot opened this issue Feb 15, 2012 · 4 comments
Closed

multiple defects in the cli #37

ietf-svn-bot opened this issue Feb 15, 2012 · 4 comments
Labels

Comments

@ietf-svn-bot
Copy link

owner:jbothun@concentricsky.com resolution_fixed type_defect | by miek@miek.nl


Hello,

I just started playing with xml2rfc version 2, to see how
it works wrt version 1 and pandoc2rfc. Version two seems
to work OK, and creates a nice looking text file. I made
the following observations.

It seems the Roman list style isn't supported anymore --
this was a hidden feature in xml2rfc version 1:

 WARNING: No %c or %d found in list format string: format %i.

Or uppercase:

 WARNING: No %c or %d found in list format string: format %I.

Also non Roman uppercase letters don't work anymore:

 WARNING: No %c or %d found in list format string: format %C.

I would consider that a bug.

Also, lines like:

 <?xml version='1.0' encoding='UTF-8'?>

Halfway through the document, make the parsing fail. xml2rfc(1) handles
this OK (just skips it, I assume?) These lines are easily created when
cutting and pasting a reference into your doc.

That's a feature, caused by using a proper XML parser.

xml2rfc(1) uses two parameters on the command line:

 xml2rfc<infile>.xml<outfile>.txt

xml2rfc(2) discards the second one and writes.txt

I'm not a fan of xml2rfc(1)'s behavior, but making xml2rfc(2)
behave different makes upgrading harder...

I don't think it makes a big difference; most people do not run local versions anyway right now.

Things like:

 <section title="section" anchor="section">
 <xref target="section"/>.

are expanded to "Section 2.1" in xml2rfc(1) and to see "[section]"
in xml2rfc(2).

That's a bug.

xml2rfc(1) add two spaces after a end-of-sentence dot, xml2rfc(2) one:

 1: "back" section of an RFC.  The easiest way is to create a template
 2: "back" section of an RFC. The easiest way is to create a template XML

That's a bug.

In hanging paragraphs the same happens, two spaces for xml2rfc(1) and one
space for xml2rfc(2).

grtz,
Miek Gieben


Issue migrated from trac:37 at 2022-02-05 12:24:06 +0000

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com commented


From Alice 2012-04-18:

AFAICT, the only one remaining from Miek's list:

  • lost some functionality of customized lists. e.g. list style="format %C", "format %I", "format %i" don't work. (I have confirmed these.)
    Ones that Miek listed that appear to have been fixed:
  • xref with target of section anchor has wrong text output.
  • two spaces after period.

@ietf-svn-bot
Copy link
Author

@jbothun@concentricsky.com commented


Fixed at 597

@ietf-svn-bot
Copy link
Author

@jbothun@concentricsky.com changed status from new to closed

@ietf-svn-bot
Copy link
Author

@jbothun@concentricsky.com changed resolution from `` to fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant