-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Local links to use <<anchor,text>> format #21
Comments
http://stackoverflow.com/a/12244248 I think we can only support this feature if the document has a TOC 😒 |
That's really interesting... but it's a fine workaround, right? If you have a lot of internal links, you could add a TOC before converting. I would find that useful. |
Yes with this workaround I think it will be possible to resolve "link ids" (ie. However it's not possible to create a Table Of Contents. So basically if a TOC is not already present in the document we can't do nothing. |
So we can detect the presence of a toc, and we can detect internal I'm happy to take a swipe at this one if you want. I just haven't looked at On Jul 23, 2016 16:40, "Guillaume Grossetie" notifications@github.com
|
Sure! Then we iterate on children : Code.gs#L50 Each An The Google Apps Scripts documentation is pretty clear and you should find all the information there. When in doubt you can use a Logger to debug: https://developers.google.com/apps-script/reference/base/logger Let me know if you need help 😉 |
Very cool; thanks for the cheat sheet. On Sat, Jul 23, 2016 at 6:21 PM, Guillaume Grossetie <
|
Right now when a hyperlink to a local anchor gets processed, it looks something like this:
This seems to just be a direct copy, but I bet that ID is getting carried with the element being linked to, and we can grab that and use it to form proper local xref. We don't actually use a lot of local links, but these can be a little hard to convert since that hash string doesn't actually appear elsewhere in the converted, so it's not clear just what that local link lined up with.
The text was updated successfully, but these errors were encountered: