Yuriko N. wrote:
Thank you for your response.
Sorry,I think I did not make my stand point clear enough.
I was not trying to write that we want words contained in SVG graphics to be
"indexed".
Let me try once more.
I am not saying we want words contained in SVG graphics to be "indexed".
(I double checked with my users and they say that they understand your policy
for XXE that only
text strings in prose are targeted for indexing in web help)
OK.
But even if not indexed,
they want the words contained in SVG graphics whether embedded or referenced to
be CNTL-A CNTL-C selectable individual strings
so that each string can to be picked and used for copy-and-paste or to be easy
to jump to by using web browser's search feature.
Understood now. You mean the Web browser's "Find in Page" (Ctrl+F)
feature, NOT our Web Help's "Search" tab.
(This is in contrast with png graphics for which words contained in those
graphics cannot be used for cut-and-paste)
But when we check use case 2)a) and use case 2)b), we find that we can select
individual strings within svg for use case 2)b)
but not for use case 2)a).
When we try to select words contained in SVG graphics for use case 2)a) by
using CNTL-A or mouse pointer, the whole graphic is selected
as if the graphic is a png type instead of a svg type.
So we are wondering why individual strings for use case 2)a) cannot be
selected, even though 2)a) and 2)b) are almost the same thing.
So the question is:
Why does use case 2)a) and use case 2)b) act differently as explained above,
even though these two are almost the same thing ?
If possible, we want use case 2)a) and 2)b) to act in the same way and the
words contained in SVG graphics
to be CNTL-A CNTL-C selectable individual strings for both use cases.
You are right. I made a mistake. 2)a) and 2)b) are definitely NOT the
same thing.
Method 2)b):
---
<svg-container><svgref href="media/graphic.svg"/></svg-container>
---
is in fact equivalent to method 3):
---
<svg-container>
<svg:svg height="64.710144" version="1.1"
viewBox="0 0 104.28986 51.768115" width="130.36232"
xmlns:svg="http://www.w3.org/2000/svg";>
...
</svg:svg>
</svg-container>
---
In other words, <svgref href=""/> may be used to *embed* SVG graphics in
the generated XHTML pages.
This is mandated by the DITA 1.3 spec:
---
Processors SHOULD process the SVG as though the <svg> element had
occurred directly in the content of the containing <svg-container> element.
---
http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part2-tech-content/langRef/technicalContent/svgref.html
This is also crystal clear in the implementation:
XXE_install_dir/addon/config/dita/xsl/xhtml/svg.xsl
--> Therefore in order to achieve what you want you must tell your users
to use method 2)b) or method 3) and NOT method 2)a)
[FYI, method 2)a) is:
---
<image href="linktest.svg"/>
---
]
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
