Yuriko N. wrote:
I am not in a hurry for an answer, but would appreciate if we can receive your
updated comments for the following,
so that we can announce to our company users of XXE about recommended settings
when creating web helps.
We had some problem in keeping SVGs for webhelps, but have technically solved
it by referring to your
mailing-list archive information (adding definition for svg folder in advance).
But then we find that there are problems that we need to solve when viewing the
SVGs from browsers.
(Such as some characters not showing, char strings within svg not included in
webhelp text search result and so on.)
So we are wondering if keeping your original setting so that svg is converted
to png is better.
I checked your opinion at 2009 time frame in mailing-list archive as follows. 7
years has passed since then
but do you still have same opinion that, generally speaking, even at current
2017 it's better to automatically convert SVGs to PNGs
for html/webhelps (Which means to let go of the idea about search-able texts
and magnify-able details of pictures)?
You have two ways to add SVG graphics to your DITA documents.
Method 1)
---------
By reference, example:
<image href="logo.svg"/>
Method 2)
---------
By embedding the SVG element using a <svg-container> wrapper (This is a
DITA 1.3 feature; see
http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part2-tech-content/langRef/technicalContent/svg-container.html).
This is explained in: "7. Rich media content",
http://www.xmlmind.com/xmleditor/_distrib/doc/dita/media.html
Attached sample document "tsvg.dita" shows you these two methods.
Method 1)
---------
- Out of the box, when converting the DITA document to HTML-based
formats (like Web Help), the SVG file is automatically converted to PNG.
- The text content of the *external* SVG file is of course, not indexed
by our Web Help Compiler.
Method 2)
---------
- When converting the DITA document to HTML-based formats (like Web
Help), the embedded SVG is simply copied to the generated HTML pages.
- The text content of the embedded SVG is indexed by our Web Help
Compiler (that is, appear in the "Search" pane of the generated Web
Help). This is a BUG and should not happen. SVG files are supposed
contain to images (MIME type=image/svg+xml), not prose.
--> If, using Method 1), you prefer to reference SVG files in your DITA
documents and don't want them to be automatically converted to PNG, then
please proceed as follows:
a) Open your DITA document.
b) Select Options → Customize Configuration → Preprocessing Options.
c) Add "svg," to the list contained in the "Copy images to" field. See
attached screenshot.
Reference: "8. Preprocessing options",
http://www.xmlmind.com/xmleditor/_distrib/doc/dita/preprocess_options.html
May be we'll make this the default in the future, now that *all* modern
browsers have no problem displaying SVG images.
Meanwhile, you have seen how simple it is to change this yourself.
--> My conclusion: you have the choice and whatever is your choice, it's
quite easy to implement it using XXE.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
"topic.dtd">
<topic id="tsvg">
<title>Tests SVG</title>
<body>
<p>Tests SVG.</p>
<fig>
<title>This figure <i>points</i> to an external SVG file:
<filepath>logo.svg</filepath></title>
<image href="logo.svg"/>
<p>More tests.</p>
</fig>
<fig>
<title>This figure <i>embeds</i> SVG graphics:</title>
<svg-container>
<svg:svg height="260.125" id="svg2" version="1.1" width="569.66071"
xmlns:svg="http://www.w3.org/2000/svg";>
<svg:defs id="defs4"/>
<svg:g id="layer1" transform="translate(-79.4375,-162.40179)">
<svg:rect height="132.85715" id="rect2991"
style="fill:#f5ff0f;fill-opacity:1;stroke:#000000;stroke-width:4;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
width="558.57141" x="81.428574" y="208.07646"/>
<svg:path d="m 524.28573,232.36218 -51.23079,-20.20617 -45.68888,30.7475 3.38603,-54.96742 -43.36126,-33.9512 53.32347,-13.76557 18.89015,-51.730503 29.56968,46.459833 55.03601,1.98 -35.04839,42.47932 z"
id="path3761"
style="fill:#ffd70f;fill-opacity:1;stroke:#000000;stroke-width:4;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
transform="translate(62.857143,175.71428)"/>
<svg:text id="text2985"
style="font-size:30.07068443px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
transform="scale(0.99543943,1.0045815)" x="102.13028"
y="246.95938" xml:space="preserve"><svg:tspan
id="tspan2987" x="102.13028" y="246.95938">The quick brown fox jumped</svg:tspan><svg:tspan
id="tspan2989" x="102.13028" y="284.54773">over the lazy dog.</svg:tspan></svg:text>
<svg:path d="m 588.57142,200.93362 -15.22457,-9.41277 -16.38505,7.20539 4.24742,-17.38812 -11.91599,-13.35653 17.84962,-1.33368 9.02056,-15.46018 6.78425,16.56386 17.49101,3.80161 -13.65673,11.57072 z"
id="path3763"
style="fill:#ff900f;fill-opacity:1;stroke:#000000;stroke-width:4;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
transform="translate(44.285714,15.714286)"/>
</svg:g>
</svg:svg>
</svg-container>
</fig>
</body>
</topic>
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
