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

terminology: carriage retrun being added before xref term {{notation}} #175

Closed
ReesePlews opened this issue Nov 13, 2022 · 7 comments
Closed

Comments

@ReesePlews
Copy link

looks like this is happening in both html and ms-word output...

Operation on an {{hyperspace object}}.

renders as
Spatial_Web_Protocol_Architecture_and_Governance_-_2022-11-13_20_48_49

grammar error has been corrected;

@ronaldtse
Copy link

Thanks @ReesePlews , this has been fixed in #176 which will be released in 2 weeks.

@ronaldtse
Copy link

This is how it looks like in the updated version (using Git gems). Thanks!

Screen Shot 2022-11-15 at 10 01 30 AM

@ReesePlews
Copy link
Author

@ronaldtse thank you for checking this. i wonder why the xref in {{hyperspace object}} is not being linked? it could be an issue in my file, i will check.

@opoudjis
Copy link
Contributor

opoudjis commented Nov 15, 2022

@ronaldtse thank you for checking this. i wonder why the xref in {{hyperspace object}} is not being linked? it could be an issue in my file, i will check.

The term was not defined at all in the document I looked at. As the introductory paragraph says, the IEEE Standards Dictionary is assumed to hold for terms not defined in the document, so I don't insert an error message for the missing term in the document (I do for other SDOs); but I do include the missing term in the error log.

So "hyperspace object" isn't cross-referenced because the document I saw gave nowhere to link it to.

@opoudjis
Copy link
Contributor

Thanks @ReesePlews , this has been fixed in #176 which will be released in 2 weeks.

1 week in fact, as long as the release process doesn't blow up...

@ReesePlews
Copy link
Author

@opoudjis i see the issue now about the {{hyperspace object}} not being a defined term; sorry i did not pick up on that earlier; but thank you for the update;

@opoudjis
Copy link
Contributor

Like I say, we're in a bind, because we can't insert a "THIS IS A MISSING TERM" in the IEEE document: you can reference missing terms if they're in the IEEE Standards Dictionary.

We do report missing terms in the error log. The problem is, we report lots of things, most of which are false alarms.

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

No branches or pull requests

3 participants