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

URI don't add up #290

Closed
ietf-svn-bot opened this issue Apr 16, 2015 · 4 comments
Closed

URI don't add up #290

ietf-svn-bot opened this issue Apr 16, 2015 · 4 comments
Labels

Comments

@ietf-svn-bot
Copy link

owner:henrik@levkowetz.com resolution_fixed type_defect | by miek@miek.nl


So I have this 80-page draft, https://gist.githubusercontent.com/miekg/0251f3e28652fa603a51/raw/7e0a7028506f7d2948e4ad3091f533711bf5f2a4/learninggo.txt

actually this is a book, but I'm testing my conversion to xml2rfc. And the URI section has:

9.2.  URIs

   5f1f8b9ced72dea365b98717219bbeadc86cce74 http://golang.org/doc/

   9ec338d81e4f22a396878fc78da1259c713489a2 fig/array-vs-slice.png

   2bbc538edff6a3cf280a200aa4ef1ad808e4c4f4 fig/stack.png

   49521fd0424a83579db2451037cce9850447f337 fig/reflection.png

   6308729eb85f2102aca374047ed2e09d9c7741bf https://www.debian.org

However the book has URI going up to 7:

   o  "len(array) ## cap(array) m"

                          fig/array-vs-slice.png

                          Array versus slice bd89f3beac4dedc20761c92ea1416d35b8fa9426

                    Figure 1: An array versus a slice.

   Given an array, or another slice, a new slice is created via

I tried to make a shorter example that has the same defect, but I failed. Maybe someone more familiar with the xml2rfc code can comment before I try that.


Issue migrated from trac:290 at 2022-02-05 12:40:44 +0000

@ietf-svn-bot
Copy link
Author

@miek@miek.nl uploaded file learninggo.xml (203.6 KiB)

xml source

@ietf-svn-bot
Copy link
Author

@ietf@augustcellars.com changed status from new to closed

@ietf-svn-bot
Copy link
Author

@ietf@augustcellars.com changed resolution from `` to fixed

@ietf-svn-bot
Copy link
Author

@ietf@augustcellars.com commented


Fixed in f6c0d33:

Fix #290
Fixes include - correcting code to deal with the difference in unicode strings on Python 2.7 vs Python 3.4
Build the abstract when doing the indexing pass so that any references in it will be included both times through
Add the start of a unicode test file.

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