-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better xsltparam handling #263
Comments
I've created the Gist |
See related issue #65 |
fsundermeyer
added a commit
that referenced
this issue
Jul 1, 2015
fsundermeyer
added a commit
that referenced
this issue
Jul 2, 2015
Stable release DAPS 2.1: - added support for webhelp - added support for <xi:include ... parse="text"> (issue #71) - handling of passing XSLT parameters on the command line has been improved (issue #263) - improved handling of doxcuments that do not need to be profiled - daps_autobuild: changed the order of builds to increase performance - Bugfix package-src: removed extraneous text - Bugfix daps_autobuild: in case no rebuild was necessary, rsync deleted the previous results - Bugfix DB4 -> DB5 migration: Fixed various issues in the migration stylesheet
fsundermeyer
added a commit
that referenced
this issue
Jul 2, 2015
Stable release DAPS 2.1: - added support for webhelp - added support for <xi:include ... parse="text"> (issue #71) - handling of passing XSLT parameters on the command line has been improved (issue #263) - improved handling of doxcuments that do not need to be profiled - daps_autobuild: changed the order of builds to increase performance - Bugfix package-src: removed extraneous text - Bugfix daps_autobuild: in case no rebuild was necessary, rsync deleted the previous results - Bugfix DB4 -> DB5 migration: Fixed various issues in the migration stylesheet
The command line part is solved with commit 343d992 |
Wasn't closed automatically ("Fixes" should be followed by a hash character, followed by the issue number). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rather than using
we should implement somethin more intuitive like
For the DC files it would be
XSLTPARAM="key=value key2=value2"
PARAM="key=value"
The text was updated successfully, but these errors were encountered: