László Németh
391ea3bcb5
Add new minimum character limit paragraph property to limit hyphenation left to the compound constituent boundaries: com::sun::star::text::ParaHyphenationCompoundMinTrailingChars – With the previous option for the hyphenation right to the constituent boundary, this new option allow to limit or disable hyphenation completely inside the compound constituents, or hyphenate only at constituent boundaries, with or without inside the suffix of the word or constituents; – xmloff: add "no-limit" to loext:hyphenation-compound-push-char-count and loext:hyphenation-compound-push-char-count; – "no-limit" values of this and the *LeadingChars option mean a maximum value. When both *LeadingChars and *TrailingChars got "no-limit", hyphenation before and inside the suffixes are forbidden, i.e. it is allowed only at constituent boundaries; – textflowpage.ui: set max character count to 99, in both options; – fix ParaHyphenationCompoundMinLeadingChars implementation for compound words with multiple constituents, when the middle word(s) are shorter, than the limit (e.g. Hungarian "tűz|kő|pattintás" wasn't hyphenated as "tűzkő-pattintás", only as "tűz-kőpattintás"). Follow-up to commit3a332d9f1c"tdf#158885 cui offapi sw xmloff: fix hyphenation at stem boundary" and commitc899d3608d"tdf#158885 sw: don't hyphenate right after a stem boundary". Change-Id: I0b71562727332217364f9ace85e8ac6ea3abc8b1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/196345 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