-
Notifications
You must be signed in to change notification settings - Fork 38
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
xml2rfc 2.3.11 and format %i. #94
Comments
@miek@miek.nl commented Hmm, this didn't come over right. I don't like the 5 spaces afer typesetting the roman numeral. It should be possible to use something like 'format %2i' or the like? So one can specify the amount of spacing. Even then, it looks like a bit too much. IOW I like the v1 behavior better. |
@henrik@levkowetz.com commented I knew this might be a controversial change, and I did consider adding in a field width You mention only the i., ii. case, but I wonder if you in real life usage, when looking
compared with
will still prefer the version with variable text start position... |
@henrik@levkowetz.com changed priority from |
@henrik@levkowetz.com changed component from |
@miek@miek.nl commented Yeah, but now it looks:
|
@henrik@levkowetz.com commented Ahh... :-) That's an Oops, indeed. |
@henrik@levkowetz.com edited the issue description |
@henrik@levkowetz.com commented Edited description to make the original point obvious (it was lost due to html swallowing whitespace, at first) |
@henrik@levkowetz.com commented From 6d11289: Updated tests to show flaw in rendering of lists using roman numerals with surrounding characters, see issue #94. |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from `` to |
@henrik@levkowetz.com commented Fixed in 2cdbb66: Reworked code to render roman numerals in lists, to place whitespace correctly in justification field. Fixes issue #94. |
resolution_fixed
type_defect
| by miek@miek.nlThanks for you work, I'm using the svn version atm to see what has changed, between 2.3.10 and 2.3.11.
I noticed the following:
-> 2.3.10 (text output):
In 2.3.11:
-> 2.3.11 (text output):
Issue migrated from trac:94 at 2022-02-05 12:27:50 +0000
The text was updated successfully, but these errors were encountered: