Hi roger64,
Thanks for your feedback.
As the plugin didn't generate much interest and was primarily designed for experienced Writer2LaTeX users who usually have the technical skills to modify/replace the default config and css files and the very simple Python plugin wrapper code, I'm somewhat reluctant to add a proper GUI, but I might add plugin prefs support that'll allow the user to modify some of the default settings.
Quote:
Originally Posted by roger64
1. - Choice between EPUB2 and EPUB3 is now difficult for the average user.
|
I
might add this as plugin preference settings. However, as I've mentioned before, it's usually not a good idea to use an alpha version in a production setting.
Quote:
Originally Posted by roger64
2. - There are two major configuration files interesting the user: config.css and epub.css. However we can imagine there could exist several files of this kind [...]
|
AFAIK, most Writer2LaTeX users use only one set of config/css files. IMHO, having a proper GUI for config/css file selection would be a nice-to-have feature, however, it's not essential.
Quote:
Originally Posted by roger64
When I wish to incorporate fonts, up to now the plugin allows me to insert only some @font-face declarations in epub.css. It would be good to be able to also designate and import in the EPUB the content of a "Resource" folder with fonts and the com.apple.ibooks.display-options.xml file.
|
Both are features that aren't natively supported by Writer2LaTeX and adding the
com.apple.ibooks.display-options.xml file is only needed for iBooks epub3 books, which aren't that well supported outside of iBooks.
Besides there's also dedicated
AddiBooksXML plugin by DiapDealer.
I
might add a user font path to the plugin prefs settings and automatically add all fonts in that folder to the epub.
Quote:
Originally Posted by roger64
cm to em:
|
If you specify your own stylesheet, it shouldn't have any cm values in it and using Writer2LaTeX without a custom stylesheet isn't recommended anyway. I.e., don't expect support for this feature.
Quote:
Originally Posted by roger64
xhtml files
|
AFAIK, the epub3 standard supports both xhtml and html files and only requires that each type have the proper extension and file type declaration. I.e. it does
not require XHTML files nor XHTML file extensions for HTML(5) files.
Besides it's not possible to rename files with plugins without breaking links. (Only the GUI rename feature will properly update links.)