-
Notifications
You must be signed in to change notification settings - Fork 12
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
provide options for how svg icons are included in document #23
Labels
Comments
mattcoarr
added a commit
that referenced
this issue
Mar 5, 2014
…different parameters. supports issue #23
mattcoarr
added a commit
that referenced
this issue
Mar 5, 2014
also now the switch between iconReferenceStyle == "inlineLiteralXml" and iconReferenceStyle == "dataUri" is now working * data urs with base64 encoded svg data are now usable * inlineLiteralXml is the default change also allows the stylesheet parameter to be passed in to the main stylesheet (stix-to-html.xsl) and used in the (now imported) icons.xsl this supports issue #23
mattcoarr
added a commit
that referenced
this issue
Mar 5, 2014
also added parameter iconExternImageBaseUri that allows user to specify a relative or absolute uri to where the svg logo images are stored. supports issue #23
mattcoarr
added a commit
that referenced
this issue
Mar 18, 2014
…ing images inline (the old way) and via data uris (one of the two new options). the paths used to read in the svg xml files needed the base "image/" parent directory. this suppots issue #23
Now fixed. All three modes work as expected. This will be particularly useful if html reports are going to be served from a web server. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
allow three options for including svg logos:
This would have two related benefits. First, if option 2 or 3 is enabled, the number of lines of html in the output would be shorter (the svg files can be long). This makes it easier to scan the html files.
Second, option 3 would make the html output a bit smaller. This supports issue #2.
We could give the user the option to choose between these three methods via a stylesheet parameter. Presumably, the current "inline svg xml" would be the default.
The text was updated successfully, but these errors were encountered: