Quote:
Originally Posted by DiapDealer
My plan is to leave it entirely up to the user through Mammoth's style mappings and the users's own css templates. 
I'm not really envisioning this plugin being used by user A to convert user B, C, D, and E's docx files automagically. I envision it being used by a writer/user who's adapted a standard for styling all their docx documents. That way, they create a custom Mammoth style-map (or a few) and an associated stylesheet. Once they have that in place, they can focus on creating their Word/LibreOffice documents. The style-map will take care of mapping all standard and custom docx styles/headings to specific html/class-names (with associated css). |
Sounds reasonable to me. That approach is what we do, using writer2latex.jar, though of course in the case of converting user B, C, D, and E's files, I have to re-style them with our (standardized) custom styles. Also, all direct formatting for bold, italic, etc. within a paragraph is converted to custom character styles, so instead of getting <b> and </b>, we get a <span class="bold"> instead. (not necessary, but it makes it easier to work on the epub down the line.)
Quote:
|
In other words ... documents will be created that conform with a pre-existing style-map/css, rather than creating a style-map/css to accommodate each particular document (though the latter is still doable provided the user doesn't mind the extra work).
|
Indeed. Though the former is much easier than the latter, so that's the way I'd go.
"Begin with the end in mind." Although it's been my experience that talented authors are
not necessarily also talented book designers, no matter what many of them assume.
