-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
Numbered lists where the start number is not 1 #27
Comments
Unfortunately not. If there's a sensible way to implement this, then pull requests are welcome. |
Just to note, I resolved this with some really hairy parsing using Beautiful soup, so wouldn't need a Mammoth fix at this time. |
In case it's useful, attached is a text document to illustrate. |
Just to note - we're living without this feature just fine. Feel free to close. |
I have the same need. I tried to add
So, in
But if this line executes:
HTML writer puts I think, this addition corrupt default style map. What can i do with it? Or it is totally wrong way and I need to take a look on some other things? Thanks. |
Id be interested in this feature too! Getting the number of lists (and what I need in my case is footnotes and references) from word, seems to follow what I understand to be mammoths philosophy of getting the content from word (but not necessarily the style), the specific number in a footnote or list seem to be a content thing! I tried to do this with the transform api but I don't think I can. Is there any lower level way to access the content of the word document in mammoth? I'd like to figure out what number they started at |
Hi there,
We have some legacy documents, where the authors have started a numbered list at "1", then entered a bulleted list, table, then another numbered list item where the number is set to '2'. When parsing with Mammoth, this second numbered list item is set to "1".
I tried not setting freshness ...
p[style-name='Numbered List'] => ol > li
But no luck.
Is there a way to persist the numbering from the word document please?
thanks!
The text was updated successfully, but these errors were encountered: