Hi,
 
This is indeed inside of a book->info element...so a question remains as to the 
proper way to rearrange this.
 
In answer to other questions, all permissions and access are 100% verified 
correct. It appears suppression of mediaobject inside of book->info is the 
cause.
 
The particular SVG image is the logo for the Creative Commons BY-SA License, 
and the license is inside of the book->info block...perhaps this is not the 
correct place for the license. Typically the logo would be shown along with the 
written text of the license, it is a sort of "branding" for the license (there 
are several variants on the license, this image helps to quickly identify this 
variant of the license).
 
It seems that this is a case of where it would be welcomed to have validation 
fail for mediaobject inside of book->info block, instead of ignoring the 
mediaobject without saying why. In fairness, I do see a "minor" note from my 
reference material on docbook5 saying:
"Suppressed. Many of the elements in this wrapper may be used in presentation, 
but they are not generally printed as part of the formatting of the wrapper. 
The wrapper merely serves to identify where they occur."
 
My source of information on this tag is from here:
http://docbook.org/tdg51/en/html/
  http://docbook.org/tdg51/en/html/book.html
    http://docbook.org/tdg51/en/html/titleforbidden.info.html
      http://docbook.org/tdg51/en/html/mediaobject.html
        http://docbook.org/tdg51/en/html/imagedata.html
          http://docbook.org/tdg51/en/html/imagedata.svg.html
 
The reason I call it a "minor" note is that there is no way from the 
documentation to predict which parts of the info will be suppressed...the 
license text itself is being printed, so it seems reasonable that the license 
logo would go with the text.
 
Is there a different recommendation on where a book should place copyright? Is 
the info tag the wrong place for this? It's unclear where the license should be 
if not in info.
 
Thanks!
 
----- Original Message -----From: Bob Stayton <[email protected]>To: 
[email protected], [email protected]: Tue, 21 Jun 2016 
23:11:37 -0000 (UTC)Subject: Re: [docbook-apps] fop/xsltproc, External SVG Issue
 
Hi,I can't quite tell from your example, but is that mediaobject inside the 
book's info element? If so, then that's why it isn't showing up. By default, 
the stylesheet only outputs certain elements from the book info element, and 
mediaobject isn't one of them. Titlepages are generally individualistic, 
meaning they need some customization to match the author's expectations, so the 
stylesheets provide a mechanism to easily customize the titlepages. Let me know 
if that's the issue here.
 
As a test to see if the SVG itself is working, you could copy and paste the 
mediaobject element into a section, where it will be acted upon and should work.
 
Bob StaytonSagehill [email protected]
 
On 6/21/2016 3:34 PM, [email protected] wrote:> Hi,>> I'm struggling to embed 
SVG into a docbook5 document. I don't know if> this is an issue of how I'm 
coding, or if this is an issue with the> tools being used...any advice on 
solving this is welcomed.>> I am using xsltproc with docbook5 docbook.xsl to 
produce a ".fo" file> (Linux o/s), with the original XML validated error free 
under both> xmllint and jing. I am thing using fop to create a number of 
output> formats from the ".fo" file...ps, pdf, rtf. The section of code with 
the> svg being added refers to an external file, and in no case does any> error 
or warning ever show up. Here's the sample code:> <!DOCTYPE book [> <!ENTITY 
version "0.1 unreleased">> ]>>> <book xmlns="http://docbook.org/ns/docbook";> 
xmlns:xi="http://www.w3.org/2001/XInclude"; version="5.0">> <info>> ...snip...> 
<mediaobject>> <imageobject>> *<imagedata align="left" format="svg"> 
fileref="/somewhere/content/by-sa.svg"/>*> </imageobject>> <textobject>> 
<phrase>CC BY-SA License</phrase>> </textobject>> <caption>> <para>This 
document is licensed under Creative Commons> BY-SA License</para>> </caption>> 
</mediaobject>> ...snip...>> I have tried the fileref using full path, relative 
path, so on. There is> never a complaint, the svg file itself displays and 
apparently is valid> under a number of svg apps, and everything else shows up 
as expected. I> have even tried intentionally making a very impossible and 
invalid file> path, I cannot get a complaint from any of the tools. Am I using 
the XML> wrong, or are my tools missing something under valid code?>> Thanks!
 
---------------------------------------------------------------------To 
unsubscribe, e-mail: [email protected] 
additional commands, e-mail: [email protected]

Reply via email to