Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Jun 28, 2018

We have been shipping xep-daps.xml files for a few years with our
stylesheets now but never actually used them. This commit aims to change
that, because:

  • using the XEP configuration delivered with the stylesheets, we
    can make sure we actually use the right fonts and that those
    fonts are actually installed
  • we can redefine generic categories like "sans"/"serif" based on the
    stylesheets we are using and their font dependencies
  • we can strip down the xep-daps.xml delivered with DAPS to a
    minimum

Note that because of a tiny XML validation issue in suse2013's
xep-daps.xml, the new default is incompatible with all
suse-xsl-stylesheets packages until 2.0.12. :(

Also, before you say that there is no real issue here today: The xep-daps.xml configuration shipped with DAPS itself for example currently does not support our Korean fonts. The only reason we never noticed is that we normally build Korean documents with FOP and not XEP.

We have been shipping xep-daps.xml files for a few years with our
stylesheets now but never actually used them. This commit aims to change
that, because:

* using the XEP configuration delivered with the stylesheets, we
  can make sure we actually use the right fonts and that those
  fonts are actually installed
* we can redefine generic categories like "sans"/"serif" based on the
  stylesheets we are using and their font dependencies
* we can strip down the xep-daps.xml delivered with DAPS to a
  minimum

Note that because of a tiny XML validation issue in suse2013's
xep-daps.xml, the new default is incompatible with all
suse-xsl-stylesheets packages until 2.0.12. :(
@ghost ghost requested a review from fsundermeyer June 28, 2018 18:34
@fsundermeyer fsundermeyer merged commit 4fa094d into develop Jul 12, 2018
@fsundermeyer fsundermeyer deleted the feature/stylesheet-xep-daps branch July 30, 2018 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant