[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[www-devel] [ANN] libepubgen 0.1.1 has been released


libepubgen is an EPUB generator for librevenge.

List of changes:

- Avoid <div> inside <p> or <span>.
- Avoid writin vertical-align attribute without a value.
- Fix generation of invalid XHTML when there is a link starting at the
beginning of a footnote.
- Handle relative width for images.
- Fixed layout: write chapter names to improve navigation.
- Support writing mode.
- Start a new HTML file at every page span in addition to the splits
induced by the chosen split method. This is to ensure that specified
writing mode works correctly, as it is HTML <body> attribute.
- Improve tests.
- Add a basic support for ruby.
- Configure: disable treating of compiler warnings as errors by
default.
- Various minor fixes and code cleanups.

The main contributors have been Miklos Vajna <vmiklos@collabora.co.uk>
and Mark Hung <marklh9@gmail.com>.

Home page: https://sourceforge.net/projects/libepubgen/
Download from: https://sourceforge.net/projects/libepubgen/files/libepubgen-0.1.1/

D.

--
To unsubscribe e-mail to: devel+unsubscribe@documentliberation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentliberation.org/www/devel/
Privacy Policy: https://www.documentfoundation.org/privacy

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.