-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Handle w:instrTex for DOCX to HTML conversion #3389
Comments
It looks like the form is just
So this should be simple to support. |
It's actually more complex than I thought. This whole contraption has to occur in a structure like this:
See http://officeopenxml.com/WPfields.php |
@jgm and @trapias -- just wanted to let you know that, a year later, I finally addressed this. Definitely not a good first issue -- accumulating runs in state, introducing a new module with its own little parsec parser. But there's now a framework for handing further fldChar/instrText directives in docx documents. |
@jkr great, thank you! Will make a test ASAP 👊 |
Great -- if you do create a test document, can you post it? I'd prefer to replace the one that's up there now, but recent versions of Word don't seem to be able to produce links as fields. |
@jkr for sure - cannot assure I can before 10/15 days, but finally will revert to you! |
Hello,
it looks like there's a problem with hyperlinks, when converting from .DOCX to HTML as described in this discussion on Google groups:
I do not know what is the reason that causes DOCX documents to be written with the one or the other tag, but as John suggests in his answer it looks like Pandoc does not recognize the latter format.
The text was updated successfully, but these errors were encountered: