Quote:
Originally Posted by quinta@ebf.cz
Negative. Every empty paragraph (with imported style) is imported incorrectly.
After applying BeckyEbook's patch things looks better.
|
Yes. I know that now. That's why I asked her to submit her change to DOCXImport's code repository. Her fix will make it into the next version of the plugin.
Quote:
Originally Posted by quinta@ebf.cz
Some question: Is there possibility to simply import _every_ style used in source document? Without need of explicitly creating list of styles (for style map). E.g. by using wildcards in style map... or somehow.
Code:
p.* => p.*
r.* => span.*
|
No there's not. At least not via this plugin anyway. You could ask the developer of the Mammath python library (this plugin is merely a wrapper around that library) if he could incorporate it. But being familiar with the structure of his library, I'm not sure that's feasible. The very unstable "transforms" feature of mammoth might prove useful in some way, but I've no plans to incorporate that into this plugin.
I'll be honest... I never envisioned this plugin being used for one user to convert
other users' docx documents. It was primarily aimed at authors/creators who already had a standard Word style setup they used to create their documents in Word and could create a mammoth style map to accommodate that framework. Once it was initially set up, it would all just work (with occasional tweaks needed here and there). But this plugin isn't for anyone who's looking for that initial map creation phase to be done
for them.
A conversion process that can "smartly" convert unknown word style names (unknown to the user) into semantically correct, class-matched html that can be easily styled via css may be possible, but it's not likely going to happen with Mammoth.