Re: [docbook] duplicate dcterms:date

[Peter Lavin]

Hi Peter,

I recently came across this problem when I used both pubdate and
copyright/year. Here's what Bob Stayton had to say:

Currently *date* and copyright/year are mutually exclusive for the *date*
metadata, so if you change your pubdate element to a *date* element in the
info, then it will output a single *date* in the opf.

Search the list for pubdate and you'll find the complete discussion.

Hope that works for you.


On 5 September 2014 06:00, Peter Fleck peterfl...@gmail.com wrote:

  Hi all,

 I'm getting duplicate dcterms:date in the epub3 package.opf

 meta property=dcterms:date2012/meta
 dc:date2012/dc:date
 meta property=dcterms:date2012/meta
 dc:date2012/dc:date

 The validator at http://validator.idpf.org/ gives me this.

   ERROR OEBPS/package.opf 20 14 element dc:date not allowed here;
 expected the element end-tag or element dc:contributor, dc:coverage,
 dc:creator, dc:description, dc:format, dc:identifier,
 dc:language, dc:publisher, dc:relation, dc:rights, dc:source,
 dc:subject, dc:title, dc:type, link or meta
 I'm just wondering if anyone else is getting this or if it is a bug in my
 stylesheet.
 I'm using docbook-xsl-ns-1.78.1 stylesheets.

 Thanks,

 Peter




-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

[docbook-apps] invalid EPUB file when using a glossary

[Peter Lavin]

HI,

I'm attempting to validate an EPUB 3 file that contains a glossary and I'm
seeing the following error for each glossary entry:

ERROR: book.epub/OEBPS/db.gloss.xhtml(22,48): element a not allowed here;
expected element dd or dt

I'm using Epubcheck Version 3.0.1 and my style sheets are 1.78.1
(docbook-xsl-ns).

An example of the HTML that raises the error follows:

dl
dt id=db.gloss.jsonspan class=glossterm epub:type=glossterm/
(abbr class=acronymJSON/abbr)/dt
a id=idp1493040 class=indexterm/
dd class=glossdef epub:type=glossdef
  p/
/dd
...
/dl

Attempting to validate this HTML at the W3C site throws the following error:

Line 22, Column 46: XHTML element a not allowed as child of XHTML element
dl in this context. (Suppressing further errors from this subtree.)
a id=idp1493040 class=indexterm/

Am I correct in assuming that this style sheet generates invalid HTML?
If so, how can this be fixed?

Thanks.

-- 

Peter Lavin
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

Re: [docbook-apps] invalid EPUB file when using a glossary

[Peter Lavin]

Hi Bob,

Sorry, didn't reply to all first time.

Attached is a truncated version of the glossary.

It's xincluded as the child of a book.

Thanks.


On 30 July 2014 21:32, Bob Stayton b...@sagehill.net wrote:

 Hi Peter,
 Can you post the DocBook input that generated that output?

 Bob Stayton
 Sagehill Enterprises
 b...@sagehill.net

 On 7/30/2014 4:04 PM, Peter Lavin wrote:

 HI,

 I'm attempting to validate an EPUB 3 file that contains a glossary and
 I'm seeing the following error for each glossary entry:

 ERROR: book.epub/OEBPS/db.gloss.xhtml(22,48): element a not allowed
 here; expected element dd or dt

 I'm using Epubcheck Version 3.0.1 and my style sheets are 1.78.1
 (docbook-xsl-ns).

 An example of the HTML that raises the error follows:

 dl
 dt id=db.gloss.jsonspan class=glossterm epub:type=glossterm/
 (abbr class=acronymJSON/abbr)/dt
 a id=idp1493040 class=indexterm/
 dd class=glossdef epub:type=glossdef
p/
 /dd
 ...
 /dl

 Attempting to validate this HTML at the W3C site throws the following
 error:

 Line 22, Column 46: XHTML element a not allowed as child of XHTML
 element dl in this context. (Suppressing further errors from this
 subtree.)
  a id=idp1493040 class=indexterm/
 Am I correct in assuming that this style sheet generates invalid HTML?
 If so, how can this be fixed?

 Thanks.

 --

 Peter Lavin
 Skype: peter.lavin
 (GMT -05:00 Canada/US Eastern)




-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)
!DOCTYPE glossary
[
!ENTITY % all.entities SYSTEM all-entities.ent
%all.entities;
]
glossary xmlns=http://docbook.org/ns/docbook;
  xmlns:xi=http://www.w3.org/2001/XInclude; xmlns:xl=http://www.w3.org/1999/xlink; version=5.0
   xml:id=db.gloss

  info

titleGlossary/title

  /info

!-- Add an id for items with acronyms so that an acronym entry can be
created. --

  !--glossentry xml:id=db.gloss.

glossterm/glossterm

acronym/acronym

indexterm
  primary/primary
/indexterm

glossdef
  para/para
/glossdef

  /glossentry--

  glossentry xml:id=db.gloss.css

glosstermCascading Style Sheets/glossterm

acronymCSS/acronym

indexterm
  primaryCascading Style Sheets/primary
/indexterm

glossdef
  para.../para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.epub

glosstermEPUB (3.0)/glossterm

indexterm
  primaryEPUB/primary
/indexterm

glossdef
  para
The EPUB specification is an industry standard for defining how
an ebook is packaged as a single file. Some ebook vendors,
Google, Apple and Kobo, for example, require that any books
submitted for sale must conform to this standard. There are
DocBook style sheets for creating files compliant with EPUB 3.0.
See also xref linkend=db.gloss.idpf/.
  /para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.idpf

glosstermInternational Digital Publishing Forum/glossterm

acronymIDPF/acronym

indexterm
  primaryInternational Digital Publishing Forum/primary
/indexterm

glossdef
  para
The IDPF is a standards organization dedicated to the
development and promotion of electronic publishing and content
consumption. This organization is responsible for defining the
xref linkend=db.gloss.epub/ standard
  /para
  para
For more information see
link xl:href=http://idpf.org/about-us;International Digital
Publishing Forum/link.
  /para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.json

glosstermJavaScript Object Notation/glossterm

acronymJSON/acronym

indexterm
  primaryJSON/primary
/indexterm

glossdef
  para
JavaScript Object Notation is ...
  /para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.ocf

glosstermOpen Container Format/glossterm

acronymOCF/acronym

indexterm
  primaryOpen Container Format (OCF)/primary
/indexterm

glossdef
  para
The file format and process that defines the resources that make
up one or more EPUB publications. This standard was created by
the xref linkend=db.gloss.idpf/ and facilitates the
distribution of ebooks in a single-file format.
  /para
  para
For more information see
link xl:href=http://www.idpf.org/epub/30/spec/epub30-ocf.html;EPUB
Open Container Format (OCF) 3.0/link.
  /para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.pandoc

glosstermPandoc/glossterm

indexterm
  primarypandoc/primary
/indexterm

glossdef
  para/para
/glossdef

  /glossentry

  glossentry xml:id=db.gloss.profile

glosstermProfiling/glossterm

indexterm
  primaryprofiling/primary
/indexterm

glossdef
  para
One of the advantages of using DocBook

Re: [docbook-apps] invalid EPUB file when using a glossary

[Peter Lavin]

Thanks very much.


On 31 July 2014 13:26, Bob Stayton b...@sagehill.net wrote:

 Hi Peter,
 Yes, this is a bug.  The DocBook schema allows an indexterm element
 between glossterm and glossdef, but those map to dt and dd, respectively,
 and they don't allow anything in between.  The updated template (attached)
 puts the indexterm in the dt element.  I'll check this change into the SVN
 repo for the next release.

 Bob Stayton
 Sagehill Enterprises
 b...@sagehill.net

 On 7/30/2014 4:04 PM, Peter Lavin wrote:

 HI,

 I'm attempting to validate an EPUB 3 file that contains a glossary and
 I'm seeing the following error for each glossary entry:

 ERROR: book.epub/OEBPS/db.gloss.xhtml(22,48): element a not allowed
 here; expected element dd or dt

 I'm using Epubcheck Version 3.0.1 and my style sheets are 1.78.1
 (docbook-xsl-ns).

 An example of the HTML that raises the error follows:

 dl
 dt id=db.gloss.jsonspan class=glossterm epub:type=glossterm/
 (abbr class=acronymJSON/abbr)/dt
 a id=idp1493040 class=indexterm/
 dd class=glossdef epub:type=glossdef
p/
 /dd
 ...
 /dl

 Attempting to validate this HTML at the W3C site throws the following
 error:

 Line 22, Column 46: XHTML element a not allowed as child of XHTML
 element dl in this context. (Suppressing further errors from this
 subtree.)
  a id=idp1493040 class=indexterm/
 Am I correct in assuming that this style sheet generates invalid HTML?
 If so, how can this be fixed?

 Thanks.

 --

 Peter Lavin
 Skype: peter.lavin
 (GMT -05:00 Canada/US Eastern)




-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

[docbook-apps] two date entries in EPUB package.opf file

[Peter Lavin]

Hi,

I'm using the the 1.78.1-ns style sheets to create an EPUB.

Within the book.info tag I want to include both a copyright.year tag and a
pubdate tag--publication dates are quite distinct from copyright years.

When validating using Epubcheck Version 3.0.1 I get the following error:

ERROR: docbook.epub/OEBPS/package.opf(19,14): element dc:date not allowed
here

Two date entries are created in the package.opf file, one resulting from
the pubdate tag and one from the copyright.year tag.

meta property=dcterms:date2014-09-01/meta
dc:date2014-09-01/dc:date
meta property=dcterms:date2014/meta
dc:date2014/dc:date

This seems to violate the EPUB requirement that there be only one DCMES
date element. This is easy enough to fix after the fact but I don't see an
easy workaround. Any suggestions?

Thanks.

-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

Re: [docbook-apps] two date entries in EPUB package.opf file

[Peter Lavin]

Thanks Bob. It validates just fine now.


On 11 August 2014 17:21, Bob Stayton b...@sagehill.net wrote:

 Hi Peter,
 Yes, the dates still are not handled quite correctly.  Currently the date
 can come from date, pubdate, or copyright/year.  There should be a
 single template that selects one based on a priority,  which I presume
 would be pubdate, date, then copyright/year.  I'll log this as a bug.

 Currently date and copyright/year are mutually exclusive for the date
 metadata, so if you change your pubdate element to a date element in the
 info, then it will output a single date in the opf.

 Bob Stayton
 Sagehill Enterprises
 b...@sagehill.net

 On 8/11/2014 9:53 AM, Peter Lavin wrote:

 Hi,

 I'm using the the 1.78.1-ns style sheets to create an EPUB.

 Within the book.info http://book.info tag I want to include both a
 copyright.year tag and a pubdate tag--publication dates are quite
 distinct from copyright years.

 When validating using Epubcheck Version 3.0.1 I get the following error:

 ERROR: docbook.epub/OEBPS/package.opf(19,14): element dc:date not
 allowed here

 Two date entries are created in the package.opf file, one resulting from
 the pubdate tag and one from the copyright.year tag.

 meta property=dcterms:date2014-09-01/meta
 dc:date2014-09-01/dc:date
 meta property=dcterms:date2014/meta
 dc:date2014/dc:date
 This seems to violate the EPUB requirement that there be only one DCMES
 date element. This is easy enough to fix after the fact but I don't see
 an easy workaround. Any suggestions?

 Thanks.

 --

 Peter Lavin
 Telephone:  1 416 461 4991
 Mobile:1 416 882 9194
 Skype: peter.lavin
 (GMT -05:00 Canada/US Eastern)




-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

Re: [docbook-apps] Multiple biblioid's extra itemref in epub3 spine

[Peter Lavin]

Hi Peter,

I think you should be using the profile.xsl style sheet under the
profile directory rather than epub3/profile-chunk.xsl. Then apply your
epub transformation against the file output by profiling.


On 5 September 2014 10:58, Peter Fleck peterfl...@gmail.com wrote:

  Hi all.

 I'm probably doing something silly but here's my problem:
 I use the *docbook-xsl-ns-1.78.1/epub3/profile-chunk.xsl* style sheet in
 a custom layer and call

 Either --stringparam  profile.condition epub
 or --stringparam  profile.condition mobi

 And it picks the correct *biblioid* below for use in either the epub or a
 second epub for kindlegen.

 biblioid class=other otherclass=mobi
 condition=mobi978---7-/biblioid
 biblioid class=other otherclass=epub
 condition=epub978---8-/biblioid
 biblioid class=other otherclass=print
 condition=print9789-/biblioid

 My problems is that which ever comes second (ie mobi or epub) adds an
 extra itemref to the spine in the package.opf. This gives an error like -

   ERROR OEBPS/package.opf 62 37 item with id 'id-idp1288160' not found
 I can delete these manually but I have an automated script so would prefer
 a different solution.
 My guess is my Docbook is wrong.

 Thanks for your help,

 Peter




-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

Re: [docbook-apps] docbook - docx

[Peter Lavin]

Hi Fredrik,

pandoc does a decent job of converting DocBook to .docx.

See:

http://johnmacfarlane.net/pandoc/  and for a detailed review,

http://www.objectorientedphp.com/articles/pandoc.html

Peter

On 23 January 2015 at 08:45, Fredrik Unger f...@tree.se wrote:

 Hi,

 I am looking into generating reports that has to be Word 2010.

 Now I am able to get reasonable results with a simple test file using
 python-docx, currently just writing the report in python.

 My plan would be :
 - Generate/write docbook file
 - Create docx file with styles as template in Word 2010
 - Translate docbook - docx using python-docx building a
   small python library

 This gives me the freedom to generate the reports in docbook xml using
 the tools in python, xml, templates etc.

 My current document contains, text, tables, images which all are supported
 in python-docx.

 Are there any better alternatives to this approach ?


 Thanks,

 Fredrik Unger

 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] any problems with DocBook XSL 1.79.0?

[Peter Lavin]

You are exactly right. I'm importing the non-namespaced version.
Sorry for the "noise".

--
Excuse brevity. Sent from mobile device.
On Oct 22, 2015 1:46 PM, "Bob Stayton" <b...@sagehill.net> wrote:

> Hi Peter,
> I misunderstood the problem. I assumed that you were processing an
> admonition element that was not a note or warning, in which case your
> customization would generate a blank value for background-color.
>
> Looking more closely at your FO output, it seems you are getting an empty
> attribute value for the note element.  But I'm not able to duplicate that
> problem.  When I copy your note element to a sample DocBook 5 document, and
> your customization to a simple namespaced customization XSL, I get the
> correct colors for note and warning.
>
> The fact that you are getting the other custom properties such as border
> indicates that the attribute-set is working.  But it seems the d:note and
> d:warning element names are not matching in your process but they are in
> mine.
>
> Are you sure you are importing the namespaced version of the DocBook
> stylesheet?  If not, you will get a warning that it is stripping the
> namespace, the stylesheet will convert the DB5 content to DB4 before
> proceeding, and then the d:note won't match the converted element. That's
> the only thing I can think of.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 10/21/2015 6:18 PM, Peter Lavin wrote:
>
>> In 1.78.1 this customization applies the right background-color and no
>> error is thrown. By adding an 'otherwise' clause and using 1.79.0 the
>> SEVERE error becomes a warning:
>>
>> WARNING: background-color="inherit" on fo:block, but no explicit value
>> found on the parent FO.
>>
>> However, the background color is _not_ applied as it was in 1.78.1.
>>
>> On 21 October 2015 at 19:57, Bob Stayton <b...@sagehill.net> wrote:
>>
>>> Hi Peter,
>>> I don't think that's a problem specific to 1.79.0, because that should
>>> not
>>> work in 1.78.1 either.  In your customization, when you do an xsl:choose
>>> for
>>> an attribute in an attribute-set, there must be a fallback value in an
>>> xsl:otherwise clause, like:
>>>
>>> inherit
>>>
>>> FOP is rejecting the empty attribute value.
>>>
>>> Bob Stayton
>>> Sagehill Enterprises
>>> b...@sagehill.net
>>>
>>> On 10/21/2015 4:43 PM, Peter Lavin wrote:
>>>
>>>>
>>>> Hi Bob,
>>>>
>>>> Here's a problem with the background-color of admons that I ran into
>>>> while trying to create a PDF using FOP 1.1. This error does not occur
>>>> when using 1.78.1.
>>>>
>>>> The error message:
>>>>
>>>> Oct 21, 2015 7:21:56 PM org.apache.fop.events.LoggingEventListener
>>>> processEvent
>>>> SEVERE: Invalid property value encountered in background-color="":
>>>> org.apache.fop.fo.expr.PropertyException:
>>>> file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
>>>> defined ; property:'background-color' (See position 2859:397)
>>>> org.apache.fop.fo.expr.PropertyException:
>>>> file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
>>>> defined ; property:'background-color' ...
>>>>
>>>> Here's a fo file excerpt:
>>>>
>>>> >>> space-before.minimum="0.8em"
>>>> space-before.maximum="1.2em" space-after.optimum="1em"
>>>> space-after.minimum="0.8em"
>>>> space-after.maximum="1.2em" padding=".1in"
>>>> padding-top=".1in" margin="0.05in"
>>>> font-style="italic" border-top="0.5pt solid grey"
>>>> border-bottom="1pt solid grey"
>>>> background-color="" margin-left="0.25in"
>>>> margin-right="0.25in">
>>>> >>> font-size="12pt" font-weight="bold"
>>>>   hyphenate="true">Note
>>>> 
>>>>   >>> space-before.minimum="0.8em"
>>>> space-before.maximum="1.2em"
>>>>   >
>>>>   It is tidier to import resources into the project
>>>>   >>>   font-size="

Re: [docbook-apps] any problems with DocBook XSL 1.79.0?

[Peter Lavin]

In 1.78.1 this customization applies the right background-color and no
error is thrown. By adding an 'otherwise' clause and using 1.79.0 the
SEVERE error becomes a warning:

WARNING: background-color="inherit" on fo:block, but no explicit value
found on the parent FO.

However, the background color is _not_ applied as it was in 1.78.1.

On 21 October 2015 at 19:57, Bob Stayton <b...@sagehill.net> wrote:
> Hi Peter,
> I don't think that's a problem specific to 1.79.0, because that should not
> work in 1.78.1 either.  In your customization, when you do an xsl:choose for
> an attribute in an attribute-set, there must be a fallback value in an
> xsl:otherwise clause, like:
>
> inherit
>
> FOP is rejecting the empty attribute value.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 10/21/2015 4:43 PM, Peter Lavin wrote:
>>
>> Hi Bob,
>>
>> Here's a problem with the background-color of admons that I ran into
>> while trying to create a PDF using FOP 1.1. This error does not occur
>> when using 1.78.1.
>>
>> The error message:
>>
>> Oct 21, 2015 7:21:56 PM org.apache.fop.events.LoggingEventListener
>> processEvent
>> SEVERE: Invalid property value encountered in background-color="":
>> org.apache.fop.fo.expr.PropertyException:
>> file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
>> defined ; property:'background-color' (See position 2859:397)
>> org.apache.fop.fo.expr.PropertyException:
>> file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
>> defined ; property:'background-color' ...
>>
>> Here's a fo file excerpt:
>>
>> > space-before.minimum="0.8em"
>>space-before.maximum="1.2em" space-after.optimum="1em"
>> space-after.minimum="0.8em"
>>space-after.maximum="1.2em" padding=".1in"
>> padding-top=".1in" margin="0.05in"
>>font-style="italic" border-top="0.5pt solid grey"
>> border-bottom="1pt solid grey"
>>background-color="" margin-left="0.25in" margin-right="0.25in">
>>> font-size="12pt" font-weight="bold"
>>  hyphenate="true">Note
>>
>>  > space-before.minimum="0.8em"
>>space-before.maximum="1.2em"
>>  >
>>  It is tidier to import resources into the project
>>  >  font-size="10pt" font-family="monospace"
>>  >Content/Resources folder. If you choose
>>  this option any links to images, CSS files, or JavaScript files
>>  will be adjusted to point to the resources in the
>>  >  font-size="10pt" font-family="monospace"
>>>Content/Resources folder.
>>
>>
>>  
>>
>> Here's the DocBook source code:
>>
>>  
>>
>>  It is tidier to import resources into the project
>>  Content/Resources folder. If you choose
>>  this option any links to images, CSS files, or JavaScript files
>>  will be adjusted to point to the resources in the
>>  Content/Resources folder.
>>
>>  
>>
>> Here's the customization override of the fo/docbook.xsl file:
>>
>>
>>  1em
>>  0.8em
>>  1.2em
>>  1em
>>  0.8em
>>  1.2em
>>  .1in
>>  .1in
>>  0.05in
>>  
>>  italic
>>  0.5pt solid grey
>>  1pt solid grey
>>  
>>  
>>
>>#edf9ff
>>#fff1dc
>>
>>  
>>
>>
>> If you need more information let me know.
>>
>> And thanks very much for all the work you've done on DocBook--it's
>> greatly appreciated.
>>
>> On 21 October 2015 at 18:35, Bob Stayton <b...@sagehill.net> wrote:
>>>
>>> It has been about a week since candidate DocBook XSL 1.79.0 was released,
>>> and it has been downloaded about 150 times.  Has anyone who has tried it
>>> run
>>> into any problems yet?  If so, please let me know so they can be fixed
>>> for
>>> the 1.79.1 release.
>>>
>>> --
>>> Bob Stayton
>>> Sagehill Enterprises
>>> b...@sagehill.net
>>>
>>> -
>>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>>>
>>
>>
>>
>



-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] any problems with DocBook XSL 1.79.0?

[Peter Lavin]

Hi Bob,

Here's a problem with the background-color of admons that I ran into
while trying to create a PDF using FOP 1.1. This error does not occur
when using 1.78.1.

The error message:

Oct 21, 2015 7:21:56 PM org.apache.fop.events.LoggingEventListener processEvent
SEVERE: Invalid property value encountered in background-color="":
org.apache.fop.fo.expr.PropertyException:
file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
defined ; property:'background-color' (See position 2859:397)
org.apache.fop.fo.expr.PropertyException:
file:/Users/peter/writing/flare/flare.fo:2740:39: No conversion
defined ; property:'background-color' ...

Here's a fo file excerpt:


  Note
  

It is tidier to import resources into the project
Content/Resources folder. If you choose
this option any links to images, CSS files, or JavaScript files
will be adjusted to point to the resources in the
Content/Resources folder.
  
  


Here's the DocBook source code:


  
It is tidier to import resources into the project
Content/Resources folder. If you choose
this option any links to images, CSS files, or JavaScript files
will be adjusted to point to the resources in the
Content/Resources folder.
  


Here's the customization override of the fo/docbook.xsl file:

  
1em
0.8em
1.2em
1em
0.8em
1.2em
.1in
.1in
0.05in

italic
0.5pt solid grey
1pt solid grey


  
  #edf9ff
  #fff1dc
  

  

If you need more information let me know.

And thanks very much for all the work you've done on DocBook--it's
greatly appreciated.

On 21 October 2015 at 18:35, Bob Stayton <b...@sagehill.net> wrote:
> It has been about a week since candidate DocBook XSL 1.79.0 was released,
> and it has been downloaded about 150 times.  Has anyone who has tried it run
> into any problems yet?  If so, please let me know so they can be fixed for
> the 1.79.1 release.
>
> --
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Correct usage of the copyright tag

[Peter Lavin]

That should be 'ranges'.

--
Excuse brevity. Sent from mobile device.
On Nov 2, 2015 10:05 AM, "Peter Lavin" <lavin.pe...@gmail.com> wrote:

> If you want to show the years as a range, set the 'make.year.tanhes'
> parameter to a non-zero value.
>
> --
> Excuse brevity. Sent from mobile device.
> On Nov 2, 2015 9:57 AM, "Lars Vogel" <lars.vo...@gmail.com> wrote:
>
>> Hi,
>>
>> what is the "correct" way of using the copyright tag for multiple years?
>>
>> I used to use the following:
>>
>> 
>> 2007
>> 2008
>> 2009
>> 2010
>> 2011
>> 2012
>> 2013
>> 2014
>> 2015
>> Someone
>> 
>>
>> But that results in the PDF output to:
>>
>> Copyright © 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 Someone
>>
>> Should I only write the following?
>>
>> 
>> 2007 - 2015
>> Someone
>> 
>>
>> Best regards, Lars
>>
>>
>>

Re: [docbook-apps] Correct usage of the copyright tag

[Peter Lavin]

If you want to show the years as a range, set the 'make.year.tanhes'
parameter to a non-zero value.

--
Excuse brevity. Sent from mobile device.
On Nov 2, 2015 9:57 AM, "Lars Vogel"  wrote:

> Hi,
>
> what is the "correct" way of using the copyright tag for multiple years?
>
> I used to use the following:
>
> 
> 2007
> 2008
> 2009
> 2010
> 2011
> 2012
> 2013
> 2014
> 2015
> Someone
> 
>
> But that results in the PDF output to:
>
> Copyright © 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 Someone
>
> Should I only write the following?
>
> 
> 2007 - 2015
> Someone
> 
>
> Best regards, Lars
>
>
>

Re: [docbook] ePub problems on Android devices

[Peter Lavin]

Hi Flavia,

I've used DocBook to produce EPUB 3.0 files and opened them on Android
phones (Nexus 4 and Nexus 5) and on a Nexus 7 tablet using both Google
Books and the Aldiko reader without experiencing any issues. Tables
are problematic on any device especially smaller ones often requiring
that you limit the number of columns. I haven't embedded media files
in ebooks so can't speak to that issue.

Many ereaders don't fully support CSS 3--and that has been my
experience with Aldiko--so that may possibly be an issue.

Hope that helps.

On 10 September 2015 at 16:53, Flavia Majlis
<flavia.maj...@mail.mcgill.ca> wrote:
> Hello,
> I am using DocBook to create ePub files. The ePub can be viewed perfectly on
> iOS devices (iPhone 6 and iPad, with iBooks) but I could not find an ePub
> reader that would format the ePub document properly on the Android device.
> We tried many ePub readers, but they would either not be able to format the
> tables properly, or they would not play the videos from the ePub file... Any
> ideas?
> Thank you so much!
> Flavia
>
> --
> Flavia Majlis,
> MSc, Computer Science, McGill University
> BFA, Photography, Concordia University
>
> www.flaviamajlis.com
> cabinetphoto.org
> www.simlog.com
>
> 1.514.909.6101



-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org

Re: [docbook] ePub problems on Android devices

[Peter Lavin]

I don't believe you can embed media in PDF files--but I'm no expert on PDF.

--
Excuse brevity. Sent from mobile device.
On Sep 11, 2015 9:17 AM, "Flavia Majlis" <flavia.maj...@mail.mcgill.ca>
wrote:

> Thank you for your help, Peter. Since we have pretty large tables to
> display, we thought that maybe a pdf file would be a solution. The tables
> are indeed displayed perfectly in the pdf output in the tablets, but I was
> not able to embed videos into the pdf documents using DocBook.
> Is there any way to embed media for pdf output using DocBook?
> Thank you!
> Flavia
>
> On Thu, Sep 10, 2015 at 5:36 PM, Peter Lavin <lavin.pe...@gmail.com>
> wrote:
>
>> Hi Flavia,
>>
>> I've used DocBook to produce EPUB 3.0 files and opened them on Android
>> phones (Nexus 4 and Nexus 5) and on a Nexus 7 tablet using both Google
>> Books and the Aldiko reader without experiencing any issues. Tables
>> are problematic on any device especially smaller ones often requiring
>> that you limit the number of columns. I haven't embedded media files
>> in ebooks so can't speak to that issue.
>>
>> Many ereaders don't fully support CSS 3--and that has been my
>> experience with Aldiko--so that may possibly be an issue.
>>
>> Hope that helps.
>>
>> On 10 September 2015 at 16:53, Flavia Majlis
>> <flavia.maj...@mail.mcgill.ca> wrote:
>> > Hello,
>> > I am using DocBook to create ePub files. The ePub can be viewed
>> perfectly on
>> > iOS devices (iPhone 6 and iPad, with iBooks) but I could not find an
>> ePub
>> > reader that would format the ePub document properly on the Android
>> device.
>> > We tried many ePub readers, but they would either not be able to format
>> the
>> > tables properly, or they would not play the videos from the ePub
>> file... Any
>> > ideas?
>> > Thank you so much!
>> > Flavia
>> >
>> > --
>> > Flavia Majlis,
>> > MSc, Computer Science, McGill University
>> > BFA, Photography, Concordia University
>> >
>> > www.flaviamajlis.com
>> > cabinetphoto.org
>> > www.simlog.com
>> >
>> > 1.514.909.6101
>>
>>
>>
>> --
>>
>> Peter Lavin
>> Telephone:  1 416 461 4991
>> Mobile:1 416 882 9194
>> Skype: peter.lavin
>> (GMT -05:00 Canada/US Eastern)
>>
>
>
>
> --
> Flavia Majlis,
> MSc, Computer Science, McGill University
> BFA, Photography, Concordia University
>
> www.flaviamajlis.com
> cabinetphoto.org
> www.simlog.com
>
> 1.514.909.6101
>

Re: [docbook-apps] Madcap Flare to Docbook conversion

[Peter Lavin]

I’m not sure if I understand exactly what you are asking but here goes.

Use herold from dbdoclet.org to convert HTML to DocBook. [sales pitch] You
might find "DocBook for Writers" useful when doing this kind of conversion.
It's available as an EPUB from Google or as a MOBI from Amazon.

Do you have access to Flare HTML output files? If so, use these files
rather than the "raw" Flare files. The raw files will probably contain
proprietary tags such as "" but the output files will have
converted these to standard HTML that herold can process.

There is no DocBook equivalent to a Flare TOC file. The structure of a
DocBook document is used to create a table of contents. How are your
programming skills? Assuming that your Flare TOC entries point only at
files (rather than other TOC files or Flare bookmarks) you could transform
the Flare TOC to a DocBook file with Xincludes referencing each file
created by herold. The root element of your main DocBook file will depend
upon what parameter you use with the herold option,
"--docbook-root-element".

--
Excuse brevity. Sent from a mobile device.
Hi List!

I am wondering, does anyone have any experience with transforming Madcap
Flare to Docbook? I mean not within Flare – rather a transformation that
takes a Madcap flare Toc file as input. The only reference I could find to
Madcap on this list was a short conversation from 2006 (
http://markmail.org/search/?q=madcap+flare=list%3Aorg.oasis-open.lists.docbook#query:madcap%20flare%20list%3Aorg.oasis-open.lists.docbook+page:1+mid:a5szwhwjtaaeoo6j+state:results
).
The interview referenced there seems not available anymore.

Any ideas?

Thanks!
/frank


Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se

[docbook-apps] PHP processing instructions

[Peter Lavin]

Hi,

I'm using the 1.79.1 onechunk.xsl transformation style sheets with PHP
processing instructions. If I use the HTML onechunk.xsl file in my
customization level, a "?" is required immediately before the closing
processing instruction tag. For example:


//PHP code here
?

This produces the correct opening and closing PHP tags. ()

If I use the _XHTML_ onechunk.xsl file and a terminating "?" the
output is as follows:



Note the duplicate "?". Is this expected?

Thanks.

-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook] Generic GUI component element

[Peter Lavin]

Using only guilabel sounds sensible to me.

I've used DocBook for years and only ever found a need for guibutton,
guimenu and guilabel.

--
Excuse brevity. Sent from mobile device.
On Feb 4, 2016 8:51 AM, "Anders Svensson"  wrote:

> Hi,
>
> I'm wondering what would be the recommended best practice for a GUI
> component element in DocBook?
>
> I know there are a number of different elements for GUI components, like
> guilabel, guiicon, guibutton, etc. The problem is, it's too specific. In
> most cases I see there is a wish to mark up GUI components to tag them
> semantically, but usually just one generic GUI component element rather
> than specifying exactly what kind of GUI component.
>
> But I'm having trouble finding such an element, and I suspect there just
> isn't one. In the use cases I'm referring to it will be considered too
> laborious to have to specify exactly if it is a button or an icon, etc.
>
> So what would be the recommended practice for marking up any kind of GUI
> element, whether a button, icon or whatever? The best I can think of is if
> you still don't need the specific variants is to select "guilabel" as the
> most generically named one, and probably the one there is the least use for
> even if you were to use it in its specific meaning.
>
> Is that a good idea or does anyone have any other suggestions? (Apart from
> something like a phrase with role="guicomponent" or the like, which I know
> would always be a generic option)
>
> Kind regards,
>
> Anders Svensson
>
> CEO, Paligo
>
> Anders Svensson | Paligo AB | anders.svens...@paligo.se
> Sankt Eriksgatan 117 | 113 43 Stockholm | Phone: +46 70 815 99 02
> www.paligo.se
>
>
> T he truly user-friendly CMS for technical
> documentation 
>
>

Re: [docbook-apps] WebHelp search - anybody working on improving?

[Peter Lavin]

Current versions of Lucene are capable of finding single words or
phrases and can use various operators such as 'AND', 'NOT' etc. (See
https://lucene.apache.org/core/2_9_4/queryparsersyntax.html.) So the
search packaged with Webhelp is either an old version of Lucene or not
Lucene at all. Other search capabilities packaged with documentation
tools seem to suffer from the same limitations, the search used by
Sphinx (http://www.sphinx-doc.org/) for example.

I have used Apache Solr--a web wrapper for Lucene--with DocBook HTML
and PHP output and been very pleased with the result. But you're
right, people expect  Google-like behaviour and results and it's
difficult to get them to use the syntax required for sophisticated
Solr searches.

My 2 cents worth,

Peter

On 10 November 2016 at 09:07, Janice Manwiller <jan...@sqrrl.com> wrote:
> Actually, it looks like I get the same results with or without the quotes.
> I'm not sure the quotes are enforcing phrase searching.
>
> The results list for either source connectors or "source connectors" is
> divided into the following sections:
>
> Results for: connectors, source
> Results for: source
> Results for: connectors
>
> Janice
>
> On Thu, Nov 10, 2016 at 8:41 AM, Barton Wright <ordin...@gmail.com> wrote:
>>
>> Of course, using quotes around “source connectors” does enforce phrase
>> searching. But you’re right that having that become more automatic as in
>> Google searches would be wonderful.
>>
>> As I remember DocBook WebHelp ends up with Apache Lucene as its search
>> engine, and Lucene is quite good. But, alas, the world has gotten very used
>> to Dr. Google.
>>
>> On Nov 10, 2016, at 7:09 AM, Camille Bégnis <cami...@neodoc.biz> wrote:
>>
>> We've been facing the issue too, and any tip will be appreciated.
>>
>> The issue is that people are used to Google Search, and doing that on the
>> client side is not easy ;-)
>>
>> Cheers,
>>
>> NeoDoc
>> Camille Bégnis
>> Gérant
>> cami...@neodoc.fr
>> Tél: 04.42.52.24.20
>> http://www.neodoc.fr/
>> 789, rue de la gare
>> F-13770 Venelles
>>
>> Le 10/11/2016 à 13:02, Janice Manwiller a écrit :
>>
>> I use DocBook source with the docbkx Maven plugin to generate PDFs,
>> WebHelp, and some HTML.
>>
>> The WebHelp search is a source of frustration, mostly because it does not
>> support phrase searches. So if you search for "source connectors", it looks
>> for topics that have either the word source or the word connectors. While
>> topics that contain both words do bubble to the top, the search does not
>> specifically look for the phrase "source connectors", where both words are
>> together in that order.
>>
>> Has there been any effort to improve the search? Has anyone else
>> implemented a custom search that supports phrase searches?
>>
>> Thanks,
>>
>> Janice
>>
>> --
>> Janice Manwiller
>> Principal Technical Writer
>> Sqrrl Data, Inc.
>> www.sqrrl.com | @SqrrlData
>>
>>
>>
>
>
>
> --
> Janice Manwiller
> Principal Technical Writer
> Sqrrl Data, Inc.
> www.sqrrl.com | @SqrrlData



-- 

Peter Lavin
Telephone:  1 416 461 4991
Mobile:1 416 882 9194
Skype: peter.lavin
(GMT -05:00 Canada/US Eastern)

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org