László Németh
62aecba14c
Balance word spacing within the consecutive lines to get uniform grayness and less rivers for better readability, enabled by the new paragraph property com::sun::star::text::ParaComposer and the following developments: * Add Paragraph Composer checkbox on Alignment pane of the paragraph formatting dialog window (not default yet); * Implement paragraph composer: big word spacing of a line is decreased by shifting the last word from the previous line, only if the word spacing is better, than before, and the increased word spacing in the previous line doesn't exceed the Maximum word spacing (limited paragraph composer); * When Maximum word spacing is not greater than the Desired word spacing, shifting of the last word is not limited by the Maximum word spacing (unlimited paragraph composer) * Add loext:paragraph-composer attribute, as LibreOffice ODF extension; * Add ODF unit tests for the limited and not limited paragraph composer. Note: "Smart justify" line breaking algorithm chooses space shrinking (limited by Minimum word spacing) only if shifting the last word isn't better based on the desired word spacing. This was still a greedy line breaking algorithm, resulting big word spacing in the lines before a longer word. The paragraph composer shifts the last word (or the first part of the hyphenated last word) from the previous line to decrease big word spacing in the actual line. Note: balancing very big word spacing in narrow consecutive lines can result vertical rivers. To avoid this, use limited paragraph composer by setting maximum word spacing. Follow-up to "smart justify", word spacing, letter spacing and glyph scaling developments. Selected commits: commit529755f091"tdf#166113 sw smart justify: adjust algorithm for interoperability", commit7d08767b89"tdf#130088 "tdf#119908 smart justify: fix DOCX line count + compat opt.", commit7d6696757d"tdf#159923 sw cui offapi xmloff: add custom word spacing", commit5a48070f59"tdf#126154 sw offapi xmloff cui: add min/max word spacing", commitf83a04c510"tdf#167648 cui offapi xmloff sw: add DTP-feature maximum letter spacing", commit3c53797210"tdf#167648 sw letter spacing: implement minimum letter spacing", commit45ec7bd761"tdf#168251 cui offapi xmloff sw glyph scaling: extend UNO/UX/ODF". Change-Id: I727caad70536c86be524bc9d9b52bc71208c202a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/203288 Reviewed-by: László Németh <nemeth@numbertext.org> Tested-by: Jenkins
Schemas for Validating ODF Files
Schemas that can be used for validating ODF files
subdirs:
mathml2: W3C MathML 2.0 XML Schema (needed for Math embedded objects)odf1.0,odf1.1,odf1.2: official OASIS RelaxNG schemasodf1.3: current OASIS draft ODF 1.3 RelaxNG schemalibreoffice: draft ODF schema, with additional LO extensions
The extension schema in libreoffice/ is used by all unit tests if
--with-export-validation is given, which is the default.
Notably this means that if you add a new feature to the ODF filters and you add the required unit test for the new feature, then most likely the test will fail with a complaint from the validator; in this case the schema needs to be updated to contain the new elements and attributes.
The extension schema uses the RelaxNG "include" feature to refer to the ODF
schema; this means that it only contains those parts of the schema that
actually need to be changed - this works well in many cases because the ODF
schema is quite well structured with many named patterns, but unfortunately
there are a few places where that isn't the case and large chunks needed to be
copied to override them.
In the easy case, to add an attribute you just want to search for the
corresponding element, which will have a "foo-attlist" named pattern, and then
add another attribute like this:
<rng:define name="draw-enhanced-geometry-attlist" combine="interleave"> rng:optional <rng:attribute name="drawooo:sub-view-size"> <rng:ref name="string"/> </rng:attribute> </rng:optional> </rng:define>
Currently only the features that are actually exported in the unit tests have been added to the schema; there is still some work to do here to add everything; the crashtesting script also does ODF validation of all files and now also uses the custom schema.
Unfortunately it turned out that there are a lot of extensions already for which no proposal exists [1], and in many cases not even an entry on the Wiki [2], so clearly something like this extension schema is needed.
[1] git grep TODO schema/libreoffice