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

Annex cross-references require update #176

Closed
bradh opened this issue Dec 4, 2015 · 3 comments
Closed

Annex cross-references require update #176

bradh opened this issue Dec 4, 2015 · 3 comments
Assignees
Milestone

Comments

@bradh
Copy link
Contributor

@bradh bradh commented Dec 4, 2015

There are numerous cross-referencing issues for Annexes, including the ATS and parts of the new Annex F content that still refer to old Annexes (e.g. Requirement 86).

@jyutzler jyutzler self-assigned this Dec 4, 2015
@jyutzler jyutzler added this to the 1.0.2 milestone Dec 4, 2015
jyutzler added a commit to jyutzler/geopackage that referenced this issue Dec 4, 2015
@jyutzler
Copy link
Contributor

@jyutzler jyutzler commented Dec 4, 2015

I attempted to fix this with #177. It might not be perfect but it should be a lot better. I think there were also some stale references that had nothing to do with #132.

@pepijnve
Copy link
Contributor

@pepijnve pepijnve commented Dec 5, 2015

@jyutzler it might be worthwhile to make these real asciidoc cross-references. That way they should stay up to date as long as you use stable anchor ids (i.e., not the autogenerated ones). I started the process of doing that (things like tables and figures are already done for instance), but never got round to the ATS.

@jyutzler
Copy link
Contributor

@jyutzler jyutzler commented Dec 5, 2015

@pepijnve I hear you but it isn't a good use of my time to do all of these. My head hurts just trying to think of a convention to uniquely name each reference. (There are at least 100.) I may still do this, but literally if I have time to kill.

@jyutzler jyutzler closed this Dec 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants