Re: [docbook-apps] DocBook XSL 1.78.1 copyright status

[David Jackson]

A copyright date does NOT change  in individual modules simply because a
new release has been issued.
The copyright date would be changed in individual supplied code modules to
include a year e.g. hyphenated such as 2010-2103  if minor changes occurred
to the module during those intervening years.
If on the other hand major changes were made that warranted the need to set
a new baseline for a copyright, that is when you would use a comma
delimited date such as 2010- 2012, 2013



On Mon, Sep 22, 2014 at 9:06 AM, Jirka Kosek  wrote:

> On 22.9.2014 16:59, Andy Hatton wrote:
> > The distribution includes the COPYING file, which includes various
> > copyright statements.
>
> These copyright statements are not much useful, what's important is very
> liberal licence statement below them.
>
> > The copyrights run up to 2012, but 1.78.1 was released in 2013 (I
> > think). The same statements are included in the current snapshot
> > distribution.
> >
> > Is this just an oversight, or has the copyright situation changed after
> > 2012?
>
> Nothing changes, simply no one dared to update dates. Next release will
> fix this and will state:
>
> Copyright (C) 2005-2014 The DocBook Project
>
> (with very high chance that in 2015 we forgot to update again :-)
>
> Jirka
>
> --
> --
>   Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
> --
>Professional XML consulting and training services
>   DocBook customization, custom XSLT/XSL-FO document processing
> --
>  OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
> --
> Bringing you XML Prague conferencehttp://xmlprague.cz
> --
>
>

Re: [docbook-apps] DocBook XSL 1.78.1 copyright status

[Jirka Kosek]

On 22.9.2014 16:59, Andy Hatton wrote:
> The distribution includes the COPYING file, which includes various
> copyright statements.

These copyright statements are not much useful, what's important is very
liberal licence statement below them.

> The copyrights run up to 2012, but 1.78.1 was released in 2013 (I
> think). The same statements are included in the current snapshot
> distribution.
> 
> Is this just an oversight, or has the copyright situation changed after
> 2012?

Nothing changes, simply no one dared to update dates. Next release will
fix this and will state:

Copyright (C) 2005-2014 The DocBook Project

(with very high chance that in 2015 we forgot to update again :-)

Jirka

-- 
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
   Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
--
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--



signature.asc
Description: OpenPGP digital signature

[docbook-apps] DocBook XSL 1.78.1 copyright status

[Andy Hatton]

Hi,

I have been asked to investigate/verify the copyright status for the 
DocBook 1.78.1 stylesheets.


The distribution includes the COPYING file, which includes various 
copyright statements.


The copyrights run up to 2012, but 1.78.1 was released in 2013 (I 
think). The same statements are included in the current snapshot 
distribution.


Is this just an oversight, or has the copyright situation changed after 
2012?


Thanks

--
~~~
Andy Hatton

-
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] Problems customizing WebHelp and HTML output

[Kasun Gajasinghe]

Hi Janice,

How do you feed these customizations to the docbkx plugin? May be there is
additional configurations you need to do in the docbkx maven plugin?

On Mon, Sep 22, 2014 at 1:38 PM, Janice Manwiller  wrote:

> Still relatively new to DocBook.
>
> In the doc set that I inherited, there are XSL files marked for FO (PDF),
> HTML, and WebHelp. Our doc build uses the Maven docbkx plugin to generate
> our documents.
>
> I've been able use information from the DocBook XSL reference to make
> changes to the FO file and see the results in the PDF output. These changes
> include:
>
> - Removing table and figure numbers
> - Removing the lists of tables and figures
> - Updating the cross-reference text to remove "the section called"
>
> However, any changes I make in the HTML or WebHelp XSL files seem to be
> ignored. I've been able to update the CSS file to make changes to the look
> and feel of the output, but not any changes to the basic transformation.
>
> For example, I added this chunk to the FO stylesheet to handle removing
> the table and figure numbers and updating the cross-reference text:
>
> 
>   
>   http://docbook.sourceforge.net/xmlns/l10n/1.0";>
> 
>   
> 
> 
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
> 
>   
>
>   
>   
>   
>   
>   
>
>
> However, adding the same chunk to the WebHelp XSL file has no effect on
> the WebHelp output.
>
> As another example, our HTML output still has section numbers. I added the
> following to the HTML stylesheet:
>
> 
>
>
> But that had no effect either - the section numbers were still there.
>
> Am I missing something? Is there a difference in the transformation
> configuration for online output vs. PDF output?
>
> Thanks,
>
> Janice
>



-- 
~~~***'***~~~
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com,
*linked-in: *http://lk.linkedin.com/in/gajasinghe
*blog: **http://blog.kasunbg.org* 


*twitter: **http://twitter.com/kasunbg* 

Re: [docbook-apps] Olinking to section does not provide section number

[Erik Rask]

I actually solved it myself, sorry to have disturbed. The solution, 
if anyone has run into the same issue, is below.

- Original Message -
> When I use an olink to a chapter, I get the labelnumber element correctly
> represented. When I olink to a section, I do not, and I get the message
> "Request for label of unexpected element: olink". I've tried setting the
> xrefstyle with both "template:%n %t" and "select:labelnumber title" to no
> avail.
> 
> Is there a parameter I'm missing here, or is xsltproc not able to deduce
> labelnumber from section?
> 

Turns out that I was using the stock XSL to collect xrefs and write the target 
db file,
since I had that copy pasted from 
http://www.sagehill.net/docbookxsl/Olinking.html,
but I use a customization layer to write output, which has section.autolabel 
set to 1. 

Using the customization layer also for the xref collection/targetdb writing 
step fixed it.

BR /Erik

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

[docbook-apps] Problems customizing WebHelp and HTML output

[Janice Manwiller]

Still relatively new to DocBook.

In the doc set that I inherited, there are XSL files marked for FO (PDF),
HTML, and WebHelp. Our doc build uses the Maven docbkx plugin to generate
our documents.

I've been able use information from the DocBook XSL reference to make
changes to the FO file and see the results in the PDF output. These changes
include:

- Removing table and figure numbers
- Removing the lists of tables and figures
- Updating the cross-reference text to remove "the section called"

However, any changes I make in the HTML or WebHelp XSL files seem to be
ignored. I've been able to update the CSS file to make changes to the look
and feel of the output, but not any changes to the basic transformation.

For example, I added this chunk to the FO stylesheet to handle removing the
table and figure numbers and updating the cross-reference text:


  
  http://docbook.sourceforge.net/xmlns/l10n/1.0";>

  



  
  

  
  

  
  

  
  

  

  

  
  
  
  
  


However, adding the same chunk to the WebHelp XSL file has no effect on the
WebHelp output.

As another example, our HTML output still has section numbers. I added the
following to the HTML stylesheet:




But that had no effect either - the section numbers were still there.

Am I missing something? Is there a difference in the transformation
configuration for online output vs. PDF output?

Thanks,

Janice

[docbook-apps] Olinking to section does not provide section number

[Erik Rask]

When I use an olink to a chapter, I get the labelnumber element correctly 
represented. When I olink to a section, I do not, and I get the message 
"Request for label of unexpected element: olink". I've tried setting the 
xrefstyle with both "template:%n %t" and "select:labelnumber title" to no avail.

Is there a parameter I'm missing here, or is xsltproc not able to deduce 
labelnumber from section?

BR
Erik Rask
--
Technical Communication Team Lead
Procera Networks



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