OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] fop/xsltproc, External SVG Issue

Just posting the solution, as there may be other people who need the logo to accompany licensing information.
My original approach was "book->info", and within "info", separate "mediaobject" and "legalnotice" tags, where mediaobject was intended to contain the logo for licensing just prior to legalnotice. The mediaobject was silently dropped.
The solution was to place the mediaobject inside of the legalnotice tag via a "figure" tag. This keeps legalnotice and icon for legalnotice together, while also allowing the icon to not be dropped. Rephrased, I moved mediaobject out of book->info->mediaobject->imageobject->imagedata and into book->info->legalnotice->figure->mediaobject->imageobject->imagedata (svg). This works as expected.
----- Original Message -----
From: Richard Hamilton <hamilton@xmlpress.net>
To: stimits@comcast.net
Cc: docbook-apps@lists.oasis-open.org
Sent: Wed, 22 Jun 2016 17:26:21 -0000 (UTC)
Subject: Re: [docbook-apps] fop/xsltproc, External SVG Issue
Actually, you shouldn't need to rearrange anything. Although the default title page code does not pass through mediaobject by default, you can get the result you want through a title page customization.
I suggest you take a look at the description of titlepage setup in Bob Stayton's book, DocBook XSL, which is available online.
Here is the section: http://sagehill.net/docbookxsl/HTMLTitlePage.html
Title page customization is flexible, but it will probably take some experimentation to get the exact result you want.
Dick Hamilton
XML Press
XML for Technical Communicators
On Jun 22, 2016, at 9:53, stimits@comcast.net wrote:
> 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 <bobs@sagehill.net>
> To: stimits@comcast.net, docbook-apps@lists.oasis-open.org
> Sent: 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 Stayton
> Sagehill Enterprises
> bobs@sagehill.net
> On 6/21/2016 3:34 PM, stimits@comcast.net 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: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]