Re: [docbook] Re: [docbook-apps] proposed additions to DocBook for programming languages

[Stefan Seefeld]

Salut Thibaut,

On 2019-04-29 5:38 p.m., Thibaut Cuvelier wrote:

Hi Stefan,

The two tag sets serve a similar purpose, but are very different in 
their implementation: the Boost-based set looks like an equivalent to 
refentry & co. (the base item is an API/library), while the one I 
proposed on GitHub is rather based on the synopses (the base item is 
either a class, an enumeration, a macro, or a namespace — the closest 
item to Boost root).
Also, the Boost extension adds many many tags (77) ithout being 
similar to what already exists in DocBook, while mine tries to use 
fewer tags (18, 15 with a generic synopsisinfo) and to mimic the 
existing semantics.
The final difference I see is that the Boost extension is really 
revolving around C++ (with concepts like headers, which are not 
present in that many languages), while I tried to be as 
language-agnostic as possible while being able to model as many things 
as possible.
Just to highlight a few differences between both :). Actually, I had a 
look at BoostBook before choosing to design something else.


I'm not going to argue on technical grounds for either side. However, I 
think it would be a big mistake to underestimate the importance of a 
community that is using a given technology, and thus is willing to help 
maintain it.


BoostBuild is fully implemented and is part of the documentation 
toolchain used by many Boost components. Thus, when I mentored the 
project to migrate to DocBook 5 and eventually merge it into DocBook 
"mainstream", my hope was to enable the wider DocBook community to use 
it, making the tool and the project easier to maintain and evolve. This 
isn't a project to be taken on by a single person.


Cordially,

Stefan
--

  ...ich hab' noch einen Koffer in Berlin...

[docbook-apps] Re: [docbook] Re: [docbook-apps] proposed additions to DocBook for programming languages

[Stefan Seefeld]

Salut Thibaut,

On 2019-04-29 5:38 p.m., Thibaut Cuvelier wrote:

Hi Stefan,

The two tag sets serve a similar purpose, but are very different in 
their implementation: the Boost-based set looks like an equivalent to 
refentry & co. (the base item is an API/library), while the one I 
proposed on GitHub is rather based on the synopses (the base item is 
either a class, an enumeration, a macro, or a namespace — the closest 
item to Boost root).
Also, the Boost extension adds many many tags (77) ithout being 
similar to what already exists in DocBook, while mine tries to use 
fewer tags (18, 15 with a generic synopsisinfo) and to mimic the 
existing semantics.
The final difference I see is that the Boost extension is really 
revolving around C++ (with concepts like headers, which are not 
present in that many languages), while I tried to be as 
language-agnostic as possible while being able to model as many things 
as possible.
Just to highlight a few differences between both :). Actually, I had a 
look at BoostBook before choosing to design something else.


I'm not going to argue on technical grounds for either side. However, I 
think it would be a big mistake to underestimate the importance of a 
community that is using a given technology, and thus is willing to help 
maintain it.


BoostBuild is fully implemented and is part of the documentation 
toolchain used by many Boost components. Thus, when I mentored the 
project to migrate to DocBook 5 and eventually merge it into DocBook 
"mainstream", my hope was to enable the wider DocBook community to use 
it, making the tool and the project easier to maintain and evolve. This 
isn't a project to be taken on by a single person.


Cordially,

Stefan
--

  ...ich hab' noch einen Koffer in Berlin...

Re: [docbook-apps] docbook namespaced stylesheets

[Stefan Seefeld]

On 2018-06-06 02:42 PM, Niels Müller Larsen wrote:

I finally got around to it. Downloaded the new namespaced stylesheets 
1.79.2 from github and ran them with my normal updated toolchain. Just 
works.


Wonderful, thanks for letting us know ! So all we need to do is produce 
a new release from github. :-)



Stefan

--

  ...ich hab' noch einen Koffer in Berlin...

Re: [docbook-apps] Parameter reference source

[Stefan Seefeld]

On 16.02.2018 12:14, Peter Desjardins wrote:
> Hi!
>
> It seems that the parameter reference site is down:
> http://docbook.sourceforge.net/release/xsl/1.75.2/doc/param.html.
>
> Does anyone know where the source for that reference is?

As we have migrated away from sourceforge (to github), I was expecting
the answer to be "somewhere under http://cdn.docbook.org/;, however I
can't it find it anywhere there, and indeed, the build logic doesn't
seem to build docs at all.

Did we miss building (and publishing) the docs in the new CI setup ?


Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...

Re: [docbook-apps] GitHub XSL issues

[Stefan Seefeld]

On 08/21/2017 05:31 PM, Jan Tosovsky wrote:
> Dear All,
>
> I am facing issue already reported and even fixed via pull request, but it
> is still waiting for integrating.
>
> https://github.com/docbook/xslt10-stylesheets/issues/32
>
> I've already fixed it for myself, but I have several related questions:
>
> (1) what is the official repository for XSL stylesheets - is it already
> GitHub or still SourceForge?

It's github.
> (2) are GitHub 'Issues' a new official tracker for XSL issues? I am asking
> especially when seeing '0 closed' so far.

It is. We transitioned quite a while ago, but nothing else has happened
since then, I'm afraid.

> (3) are pull requests appreciated contribution (seeing '14 open', some of
> them almost 1 year old)

I believe they are. At this point I think we are mostly lacking some
shared vision for how to move forward. (It isn't entirely clear who is
maintaining the project, for example.)

(As always, I'd be happy to help, but don't feel authorized to do much
else, including approving PRs or deciding a release plan.)

> Thanks for clarification,
>
> Jan

Best,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] does not number...

[Stefan Seefeld]

On 17.02.2017 13:26, Bob Stayton wrote:

[...]
>
> Since you are using DocBook 5, I assume you are using the namespaced
> version of the stylesheets, the one with "ns" in the directory name. 
> If not, I suggest you do so as it will be more efficient.

(Minor correction: the above is true for versions 1.79.1 and below.
Starting with version 1.79.2, the namespaced version of the stylesheets
doesn't use the "ns" suffix in the directory name any longer. Instead,
the no-namespace version contains "nons".)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook XSL 1.79.2 released

[Stefan Seefeld]

On 15.12.2016 20:14, deannel...@aol.com wrote:
> Good questions ;-)
>  
> I downloaded the file "docbook-xsl-nons-1.79.2.zip" from
> https://github.com/docbook/xslt10-stylesheets/releases
>  
> I have a template that pulls the docbook xsl version ($VERSION)
> variable out and displays it (along with other info).
>  
> ---
>   
> DocBook XSL VERSION is: 
>  
> 
> XSLT Version:   select="system-property( 'xsl:version' ) "/>
>XSLT Processor:   select="system-property( 'xsl:vendor' ) "/>
>   
> ---
>  
> This $VERSION is coming from the distribution. It looks like it is
> from VERSION.xsl:
>  
> 
>  
> and  then fm:version is set
>  
>   snapshot

I'm not sure how meaningful that is. In fact, I'm not sure the
VERSION.xsl file should actually be part of a package. (It is right now
being used by the build process, but as I have been working hard to
simplify that, I'm actually considering to get rid of that file. There
is a lot of obsolete logic in it.

(I can reproduce your findings, though: the 'nons' VERSION.xsl file
reports 'snapshot', while the one from the namespace package reports
'1.79.2'. I'm confident that the stylesheets correspond to the correct
version, though, so I recommend to disregard the content of the
VERSION.xsl file. (We may want to think about some other way to
represent package metadata, if that is important. But I'd definitely
argue against using an XSL file to carry that. :-) )

Meanwhile, feel free to submit an issue about 'snapshot' being reported
in VERSION.xsl, so we can make sure the error either gets fixed or the
file removed from future releases.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook XSL 1.79.2 released

[Stefan Seefeld]

On 15.12.2016 19:37, deannel...@aol.com wrote:
> Stefan,
> Sorry about the mislead. It is actually is the $VERSION that is
> "snapshot". I am also using the nons version,
> I don't know where $VERSION is actually generated - maybe version.xsl?
> I think it is formatted from something else, buty I may be wrong.
Same question: in what location do you see that value of $VERSION ? (And
are you sure you are looking at package files from the 1.79.2 release,
not a more recent snapshot build ?)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook XSL 1.79.2 released

[Stefan Seefeld]

On 15.12.2016 19:10, deannel...@aol.com wrote:
> Stefan,
>  
> The dbxslversion PI on this version still says "snapshot" not "1.79.2".
>  
> Is that part of the release process that got missed in the conversion
> to github?

No idea. Can you point me to the exact location where that PI appears ?
I'll try to track down where that is coming from.

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook XSL 1.79.2 released

[Stefan Seefeld]

I'm proud to announce the availability of the 1.79.2 release of the
DocBook XSL stylesheets.

While this is a minor release only (with no new feature additions), it
is a major milestone anyhow, which we have been working towards for a
year: We have migrated the source repository from subversion
(sourceforge.net) to git (github.com), with all the associated
infrastructure (from issue tracking to continued integration).

While there are no new features in this release, there are a few
user-visible changes to note:

* Packages will no longer be available from sourceforge.net, but rather
from http://cdn.docbook.org/. (Specifically, the new release files can
be found in https://github.com/docbook/xslt10-stylesheets/releases)

* Online stylesheets are also served from http://cdn.docbook.org/, e.g.
http://cdn.docbook.org/release/xsl/1.79.2/

* As before, we provide two sets of stylesheets, with and without
namespace support (for DocBook versions >=5, as well as for DocBook
versions 4). However, instead of using the special suffix "ns" to
identify the namespace-enabled stylesheets, we now use "nons" to refer
to the stylesheets without namespace support. This implies that the
"docbook-xsl-" packages (as well as the online stylesheets at
http://cdn.docbook.org/release/xsl/) refer to the namespace-enabled
stylesheets !


Any other changes are accidental and likely due to bugs, and should be
reported (https://github.com/docbook/xslt10-stylesheets/issues).


With this important milestone reached, we can now concentrate our effort
on bug fixes and feature additions that flow into the next major release
(1.80) sometime in the (hopefully not so distant) future.

Best,

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Automatically detecting which PDFs are affected by changes in a DocBook Git commit

[Stefan Seefeld]

On 26.10.2016 11:04, Bergfrid Skaara wrote:
> Hi,
>
> We use Git to version control our modular DocBook XML code base. I´d
> like to enforce stricter change management than what simply inspecting
> the Git log manually offers. Specifically, I want to trace each
> modular DocBook XML fie that has been changed up to the PDFs that will
> be changed as a result.
>
> Tracing the ancestor files through a sequence of xi:includes is
> trivial. My challenges are:
>
> 1. Profiling. I need to trace ancestor elements taking profiling into
> consideration.
> 2. Entities. We use entities extensively for both aliases and reused
> text. Is there a way to track effects of changed entities without
> starting with a brute force search of all DocBook XML files using that
> entity?
>
> Are there any tools, standalone or add-ons to oXygen, that support
> this or similar behavior, or am I better off writing my own script? In
> case of script, which option is better: XSLT or any scripting language
> facilitating text parsing?

I'm not quite sure what you mean by "change management", and what it is
that you want to enforce, and neither what exactly you want to trace.

Generating a PDF from XML sources typically requires some build logic,
so I think the best you can do is use that very build logic and then
compare (or validate) the generated PDF (or any intermediate formats,
such as FO). That can easily be done in a CI environment (such as
Travis-CI), so you can fully automate that such that the same process is
executed for each push.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Re: Slides with Docbook

[Stefan Seefeld]

On 10.11.2015 15:48, Norman Walsh wrote:
> camille  writes:
>> that's really great news. We are interested in contributing to it, is it
>> available anywhere yet?
> No, not quite. I'll see if I can get it out this week or next, though
> after three weeks on the road, I expect to be well and truly swamped
> with my day job for a bit.

I would *really* like to clean up and keep working on the slides support
in the xslt-1.0 repo, but unfortunately that doesn't quite work (build)
yet on github. :-)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Slides with Docbook

[Stefan Seefeld]

On 29.10.2015 05:46, camille wrote:
> Hello,
>
> we've been successfully generating S5 slides
> (http://meyerweb.com/eric/tools/s5/) from DocBook.
> It's very basic (one slide per section in an article) but works for
> simple needs.

Support for S5 has been integrated (together with some other backends a
few years ago) into the XSL distribution. You can find an example
document in
https://github.com/docbook/xslt10-stylesheets/tree/master/xsl/slides/doc.
(This needs some cleanup but unfortunately right now the entire XSL
stylesheets build system is broken, so I'm unable to work on this.
Hopefully that will be resolved soon.)

 Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Re: How to Contribute to the DocBook Project on GitHub?

[Stefan Seefeld]

On 23.10.2015 06:30, Norman Walsh wrote:
> Stefan Seefeld <ste...@seefeld.name> writes:
>> The more important (IMHO) questions are about the infrastructure needed
>> to support this:
>>
>> * A working build system
> I've moved to gradle for the repos I'm doing active work on. Other
> repos can make their own choices.

I think any build system is fine as long as it works at least for the
developers. The easier it is to build, the better are the chances of
others contributing.

And as far as I can tell, the most important repos (in terms of active
use) are 'docbook' and 'xslt10-stylesheets'. Unfortunately they don't
yet build, or at least, don't have up-to-date instructions on how to
build (and thus contribute).

>> * CI support (travis-ci ?)
> Travis CI is the way to go, I think. Again, I think I've got it setup
> for the repos I'm actively working on.


Thanks for working on this !

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] How to Contribute to the DocBook Project on GitHub?

[Stefan Seefeld]

On 19.10.2015 08:36, Thomas Schraitle wrote:
> Hi fellow DocBookers,
>
> thanks to the release of the new DocBook XSL stylesheets and the
> move from SourceForge to GitHub. Great to see this!
>
> Well, as the move to GitHub is still ongoing, I would like to shed some
> light on two questions:
>
>  1. How to contribute?
>  2. Which branching model does DocBook follows?

I imagine we could start by submitting pull requests. The maintainer can
then decide to give write permission to trusted developers to share the
work whenever seems appropriate.

As far as branches are concerned, I think the simpler the better. I
would definitely not start with something requiring any extensions. Just
use a "master" / "develop" split (or even "master" / "stable" if
development happens on master).

The more important (IMHO) questions are about the infrastructure needed
to support this:

* A working build system
* CI support (travis-ci ?)

With that working the state of a branch can easily be checked, and even
pull requests could be automatically built and tested. Once this is in
place, branching and merging, and by extension contributing patches
becomes quite simple indeed.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] DocBook XSL 1.79.0 release is available

[Stefan Seefeld]

On 16.10.2015 02:10, Thomas Schraitle wrote:
> Hi,
>
> On Thu, 15 Oct 2015 19:25:51 -0400
> Stefan Seefeld <ste...@seefeld.name> wrote:
>
>> [... GitHub ...]
>> DocBook as organization 
> Stefan, I fear your claim isn't completely right. :) Technically,
> DocBook isn't an organisation on GitHub, it's just a normal user named
> "DocBook". :)

I stand corrected. :-)

>
> Shouldn't this be migrated to an organization instead of having a normal
> user? According to https://help.github.com/articles/about-organizations/
>
>   About organizations
>   Organizations are great for businesses and large open-source projects
>   that need multiple owners and administrators, grouped together with
>   teams that determine affinity and repository permissions. 
>
> I'm not sure if this definition of "large open-source project" would fit
> for a (hypothetical) DocBook organization. However, maybe it would be
> beneficial to have one as it allows more fine-grained repository
> permissions? Not sure if that's a good thing for DocBook.
>
> Just my thoughts. :))

Yes, I fully agree to the above.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook XSL 1.79.0 release is available

[Stefan Seefeld]

Hi Lars,

On 15.10.2015 19:14, Lars Vogel wrote:
> Hi Bob,
>
> thanks a bunch. I'm happy to hear about the move to Github.
>
> I missed that announcement. What is the current state of that move and
> the new repository location?

While I'm not Bob, I think I may answer that question :-) :
DocBook as organization is on github here: https://github.com/docbook
The stylesheets are here: https://github.com/docbook/xslt10-stylesheets

Note that things are still somewhat in flux; for example, the build
system on the migrated repo doesn't quite work yet. Hopefully that will
be fixed soon, so we can start contributing patches.

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] How to use classsynopsis and friends

[Stefan Seefeld]

On 06.10.2015 16:52, maxwell wrote:
> On 2015-10-05 22:48, Stefan Seefeld wrote:
>> there was a project as part of Boost (http://boost.org) to augment
>> DocBook with a more complete vocabulary for API documentation, which
>> ultimately became "BoostBook"
>> (http://www.boost.org/doc/libs/1_59_0/doc/html/boostbook.html).
>> This has been ported back to DocBook 5 as an "API" extension, but at
>> this point is still only available in a branch. (I intend to merge it to
>> master soon.)
>
> It's too late now, I'm sure, but as a user of DocBook for purposes
> other than software documentation (we use it for grammars), DocBook
> seems bloated with all these tags for software (the aforementioned
>  being a perfect example).  In our customization, we
> remove all those tags, and add in the ones we need for literate
> programming and for linguistics, using a namespace prefix for our tags.

...which is the reason the aforementioned API vocabulary is an
extension, using its own namespace. No-one proposes to merge it into
DocBook, so only those who need it will have to deal with it.

>
> It always seemed to me like DocBook could have had a much simpler
> model, by putting the software- and hardware-specific tags into a
> separate namespace.  That would make it easier for other potential
> users to wade through the remaining elements and decide which of them
> they really need.  Obviously that couldn't have happened until DB5,
> and it's probably too late now.  I suppose the next best thing would
> be to compile a list of tags that are core DB (meaning about text in
> general), and/or a list of software- and hardware-specific tags, which
> would make it easier for potential users.

Yes, at this point it's not possible to remove all the original synopsis
elements, so we'll have to live with them. But if users switch to the
API extension (if it turns out to be useful to anyone outside a small
community, that is), these elements may indeed be forgotten as a
historic accident.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] How to use classsynopsis and friends

[Stefan Seefeld]

On 06.10.2015 00:35, Aristedes Maniatis wrote:
> On 6/10/2015 1:48pm, Stefan Seefeld wrote:
>> I once ran into similar questions...I believe the goal for all those
>> *synopsis elements is to act as a refinement for the synopsis element,
>> i.e. to let you create a synopsis with substructure. These elements are
>> *not* meant to be mixed with text.
> I guess I'm just not understanding a fundamental concept in docbook then. I 
> had always assumed docbook was a pure documentation schema and not intended 
> to model real world concepts. When I look at 
> http://www.docbook.org/tdg/en/html/synopsis.html it appears more like a way 
> for a UI designer to model an interface than for a documentation person to 
> describe it to a user. (That is, designed for its structure rather than its 
> ability to generate html/pdf or other output).

Sometimes you want to format code in your documentation. The synopses
elements allow you to do that in a structured way.  alone
could be thought of as a specialization of the  element, but with
some special semantics attached. The other synopsis elements just
provide some sub-structure for synopsis, as would be useful if the
formatted code was to be pretty-printed (function argument highlighting,
etc.)

I just found that this entire sub-vocabulary was quite incomplete, and
the formatting often even buggy, so I preferred to just use the 'raw'
.
>> However, like you, I also came to the conclusion that they are very
>> limited, so I abandoned their use in my own documentation. However,
>> there was a project as part of Boost (http://boost.org) to augment
>> DocBook with a more complete vocabulary for API documentation, which
>> ultimately became "BoostBook"
>> (http://www.boost.org/doc/libs/1_59_0/doc/html/boostbook.html).
>> This has been ported back to DocBook 5 as an "API" extension, but at
>> this point is still only available in a branch. (I intend to merge it to
>> master soon.)
> That looks really interesting. I poked around a bit, but in its currently 
> BoostBook state it looks like too much work to build and incorporate into our 
> workflow.

Right.

>  Is the branch something I can easily play with? Or do I need to wait for 
> this to land in 5.2?

That depends on how familiar you are with XML schemas and stylesheets.
(And I also am not sure about the current state; I haven't touched this
in a couple of years.)
The API schema is here:
https://github.com/docbook/xslt10-stylesheets/blob/api/docbook/relaxng/api/src/api.rnc
And the stylesheets here:
https://github.com/docbook/xslt10-stylesheets/tree/api/xsl/api

>
> I've never used an API extension.

(As I mentioned, I'm planning on merging the above into master, adding
some documentation on how to use them. If all goes well, we may even
switch the Boost documentation process to use that. But please don't
hold your breath... :-) )

>> In the meantime, I suggest to use 'synopsis' only.
> Even that seems a little cumbersome. By default all the elements there 
> preserve whitespace, so I'll be struggling a little to render html out of it 
> without overriding all the default html XSLT and removing  and  
> elements from the output.
I'm not sure I understand.  is a verbatim environment,
preserving the original formatting (in particular whitespace).

> Perhaps my solution will be to not use  itself but instead to use 
> many of its children like  and  and , etc 
> but embedded inside more old fashioned ,  and  
> elements. That should give me some nice structured output I can target with 
> css, without needing to hack away at the xslt other than some minor things.

You may indeed be misunderstanding the intended use of , as
there is nothing "old-fashioned" about  etc.; rather, the two
are supposed to be used in conjunction. You typically embed a 
*into* a section.
(See https://github.com/vsip/specs/blob/master/vsipl%2B%2B/signal.xml
for an example, and
http://portals.omg.org/hpec/files/specs/vsiplxx/signal.xhtml and
http://www.omg.org/spec/VSIPL++/1.2/PDF/ for how this may be formatted.)

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] How to use classsynopsis and friends

[Stefan Seefeld]

Hi Aristedes,

On 05.10.2015 22:39, Aristedes Maniatis wrote:
> I'm confused about the purpose of classsynopsis, methodsynopsis and all the 
> related elements. The documentation acknowledges that they are a mixture of 
> modelling and documentation. But I'm hitting my head against a wall trying to 
> use them for either.
>
> As a model, they are clearly lacking many concepts inherent to something like 
> javadoc. But that's OK, because I don't want a 1:1 mapping back to my code... 
> I just want a nice way to output documentation. In my case, I'm modifying 
> groovydoc output to spit out docbook instead of html, which gives me more 
> options to tie into an existing docbook documentation workflow.
>
> But as a documentation structure classsynopsis is also very lacking. It 
> cannot contain common structural elements like  or  so 
> I'm very limited in formatting documentation elements. My docs contain lists, 
> ulinks, xref and code samples ().
>
> Should I just discard classsynopsis and friends as a well intentioned but 
> ultimately dead-end bit of docbook, and go back to boring old sections, lists 
> and other structures which are more expressive but have no semantic concepts 
> of parameters, return types and more? Or am I missing the point of some other 
> way to handle this?
>
> By Google I've found zero examples of other people using classsynopsis.

I once ran into similar questions...I believe the goal for all those
*synopsis elements is to act as a refinement for the synopsis element,
i.e. to let you create a synopsis with substructure. These elements are
*not* meant to be mixed with text.

However, like you, I also came to the conclusion that they are very
limited, so I abandoned their use in my own documentation. However,
there was a project as part of Boost (http://boost.org) to augment
DocBook with a more complete vocabulary for API documentation, which
ultimately became "BoostBook"
(http://www.boost.org/doc/libs/1_59_0/doc/html/boostbook.html).
This has been ported back to DocBook 5 as an "API" extension, but at
this point is still only available in a branch. (I intend to merge it to
master soon.)

In the meantime, I suggest to use 'synopsis' only.

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] Show off what you've done with Docbook

[Stefan Seefeld]

On 09/11/2015 12:56 PM, Katie Welles wrote:
> Have any of you PDF + HTML output with Docbook? If anyone has such a project 
> and will be willing to show it off, send some URLs!

I have been using DocBook to document APIs for a long time. Most
recently I have been working on a C and C++ standard backed by the
Object Management Group (which imposes its own formatting rules). The
results can be seen in http://portals.omg.org/hpec/content/specifications

(The sources for these, together with the custom stylesheets are in
https://github.com/vsip/specs.


> As an aside: Have any of you used asciidoc? 

I have not. I have used a variety of other languages (markdown, ReST,
etc.) to add API documentation into source code, and extract and
translate that to DocBook. In particular, the Boost.org project
(http://boost.org) uses a DocBook extension called BoostBook with
additional markup for C++ APIs. (A few years ago I mentored a GSoC
student to rebase that work over DocBook 5. That's unfortunately not
entirely finished. I hope to be able to complete this eventually, once
the DocBook repo migrates to github and gets cleaned up a little.)

Regards,
Stefan



-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Google Summer of Code 2015 -- Last call for participants

[Stefan Seefeld]

On 10/02/15 08:47 PM, Steve Ball wrote:
 Hi All,

 My current project is to implement the DocBook roundtripping subsystem in a 
 Web browser, using Saxon-CE. However, I feel it needs to be more advanced 
 before getting a student to work on it. Happy to be convinced otherwise…

Interesting idea. I think that, quite independent from GSoC, it would be
very useful to keep project ideas as well as projects that are actively
being worked on documented somewhere (on the DocBook wiki, perhaps), if
only to display that there (still) is life in the DocBook project and
community. Sometimes it feels to me as if it has gone into maintenance
mode, with no or very little effort on development. To me, proposing
again to participate in GSoC is (also) an attempt to see whether that's
actually true or not.

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Re: [docbook] Google Summer of Code 2015 -- Last call for participants

[Stefan Seefeld]

On 10/02/15 04:06 AM, Jirka Kosek wrote:
 On 9.2.2015 22:32, Richard Hamilton wrote:
 So far, I've only received one message expressing interest in having the 
 DocBook project apply to participate in the Google Summer of Code this year.
 I can server as a mentor again.

Me too. Here is a project idea:

For years I have been using a stylesheet customization layer adding
support for changebars (based on revisionflag). In its current form that
simply adds visual markup to highlight the changed content.
However, in my typical workflow I need to maintain versions of the
document (OMG / ISO specifications) with and without changebars, which
right now requires editing the document.
What I'd like to suggest is a way to add an XSL parameter based on which
the generated document is either

* the original unchanged document
* the changed document with highlighted changes
* the changed document without highlighted changes.

This is slightly non-trivial as the required XSL adjustments even touch
indexing and TOC generation (since some content may be filtered out if
is new or no longer there in a given version).

In other words, I would like to produce old and new versions of my
docs purely based on the revisionflag markup and an XSL parameter,
rather than having to modify the sources.

(I'll put the above on the wiki, but wanted to post it to the list, too,
to inspire other people to post their own ideas. :-) )

Stefan




-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Docbook Slides

[Stefan Seefeld]

On 02/02/15 09:31 AM, Sascha Manns wrote:
 Hello List,

 actually i'm experimenting with Docbook Slides. Does anyone know how
 to place a company logo?

The easiest way to do that would be to customize the CSS for the output
medium you chose, and add the logo into the appropriate place (such as
as background image into the header).
If that isn't enough you may consider looking through the available xslt
parameters, and if that still isn't enough you can customize the
templates themselves. In that respect the process isn't much different
from ordinary DocBook XSL customization.

Stefan



 Greetings
 Sascha
 -- 
 Yours sincerly
 Sascha Manns
 -
 XCOM AG
 Qualitätsmanagement Banksystem Backend
 Rechnungswesen, Meldewesen, Steuern
 Rennweg 60
 Haus 2
 56626 Andernach

 Telefon  +49 2632 9899-158
 Telefax  +49 2632 9899-010
 sascha.ma...@xcom.de
 http://www.xcom.de

 *** XCOM AG Legal Disclaimer ***

 Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allein 
 für den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten ist das 
 Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir bitten, eine 
 fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns eine 
 Nachricht zukommen zu lassen.

 This email may contain material that is confidential and for the sole use of 
 the intended recipient. Any review, distribution by others or forwarding 
 without express permission is strictly prohibited. If you are not the 
 intended recipient, please contact the sender and delete all copies.

 Hauptsitz: Allee 8, D-47877 Willich, USt-IdNr.: DE 812 885 664
 Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900, 
 www.xcom.de
 Handelsregister: Amtsgericht Krefeld, HRB 10340
 Vorstand: Dirk Franzmeyer, Marco Marty, Dirk Werner, Sascha Bochartz
 Vorsitzender des Aufsichtsrates: Stefan H. Tarach


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] LaTeX math inside docbook, on-the-fly MathML conversion?

[Stefan Seefeld]

On 29/01/15 03:25 PM, Warren Young wrote:
 On Jan 29, 2015, at 12:46 PM, Marco Giebel marco-gie...@gmx.de wrote:

 These formulas should be interpreted on the fly to MathML
 Are you sure you want to prevent the correct viewing of your document in 
 stock versions of Chrome, IE, and Opera?

 http://caniuse.com/#search=mathml

 Yes, I know there are browser plugins and hacks like MathJax that can fix 
 this, but…ech.

 If you’re also targeting PDF, most XSL-FO processors don’t support MathML, 
 either.  Last time I checked, only Antenna House did.

I have been using FOP with the jeuclid plugin for a number of years and
have been (mostly) satisfied with its support for MathML.

FWIW,
Stefan



-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] LaTeX math inside docbook, on-the-fly MathML conversion?

[Stefan Seefeld]

On 29/01/15 05:10 PM, Warren Young wrote:
 On Jan 29, 2015, at 2:20 PM, Stefan Seefeld ste...@seefeld.name wrote:

 On 29/01/15 03:25 PM, Warren Young wrote:
 ...most XSL-FO processors don’t support MathML, either.  Last time I 
 checked, only Antenna House did.
 I have been using FOP with the jeuclid plugin for a number of years and
 have been (mostly) satisfied with its support for MathML.
 Is the prerequisites section at the top of the following page correct in 
 indicating that the plugin doesn’t support either FOP 1.0 or 1.1?

http://jeuclid.sourceforge.net/jeuclid-fop/

I'm not sure why that page indicates that. While at some point I did
have some difficulties to use jeuclid with FOP 1.0 an 1.1, I eventually
got it working. However, I never used the version directly from
sourceforge, but rather the one that is distributed by debian. Perhaps
support for newer FOP versions was added there and never merged upstream
? I'm not sure...

Still, I have been using FOP 1.1 for quite a while now with jeuclid, and
never run into major issues.

(I'm a very happy XMLMind user, by the way, including and especially
with its MathML editing support. I understand the OP's desire to type
math in latex, though. That may be faster for someone already familiar
with LaTeX. FWIW.)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

[docbook-apps] Re: [docbook] Google Summer of Code 2015

[Stefan Seefeld]

On 22/01/15 08:11 PM, Richard Hamilton wrote:
 Hi Stefan,

 Thanks for volunteering.

 Regarding the website, in about a week, if I get a few more interested people 
 saying they can participate, I'll update http://docbook.xmlpress.net for 2015.

 Anyone is welcome to look at that site now. It has all of the information 
 from our 2013 application, so you can browse around and get a sense of what 
 GSOC is all about.

Great, thanks. (I also think this might be a wonderful incentive to
tighten up a couple of loose ends with the current repository and build
system (example: move to github, ant, etc.). I still don't believe that
this is suitable for GSoC itself, but rather might be done to support
GSoC activity (i.e., to make it easier for newcomers to contribute).

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Google Summer of Code 2015

[Stefan Seefeld]

On 22/01/15 08:11 PM, Richard Hamilton wrote:
 Hi Stefan,

 Thanks for volunteering.

 Regarding the website, in about a week, if I get a few more interested people 
 saying they can participate, I'll update http://docbook.xmlpress.net for 2015.

 Anyone is welcome to look at that site now. It has all of the information 
 from our 2013 application, so you can browse around and get a sense of what 
 GSOC is all about.

Great, thanks. (I also think this might be a wonderful incentive to
tighten up a couple of loose ends with the current repository and build
system (example: move to github, ant, etc.). I still don't believe that
this is suitable for GSoC itself, but rather might be done to support
GSoC activity (i.e., to make it easier for newcomers to contribute).

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] Google Summer of Code 2015

[Stefan Seefeld]

On 21/01/15 07:44 PM, Richard Hamilton wrote:
 At today's DocBook TC meeting, we discussed the possibility of applying to be 
 a mentoring organization for this year's Google Summer of Code.

 As many of you know, the DocBook project (as distinct from the DocBook TC, 
 though many people participate in both activities) applied to the program 
 several times and was accepted twice. The program has brought us some useful 
 software and, even more important, new contributors to the DocBook community.

 To participate this year, we need two things:

 1) Mentors: we need at least 5 or 6 people who are willing to participate as 
 mentors.
 2) Ideas: we need ideas for projects that students can work on.

 I'm willing to be the organization administrator again this year, but I'm 
 glad to hand over responsibility if someone else wants the job this year.

 For the full schedule and more information about the program, go to:
 https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page

 February 20 is the deadline for applications. To participate, we need to have 
 mentors lined up by February 9, which is the opening date for filing 
 applications.

 If you're interested in participating, you can reply to this message on the 
 list or send me email directly at the address below.

I'd be happy to mentor, if I have the required knowledge depending on
the topic. (I'll think of ideas for the ideas page. Do we have a place
where to put those for this year ?)

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

[docbook-apps] Re: [docbook] Google Summer of Code 2015

[Stefan Seefeld]

On 21/01/15 07:44 PM, Richard Hamilton wrote:
 At today's DocBook TC meeting, we discussed the possibility of applying to be 
 a mentoring organization for this year's Google Summer of Code.

 As many of you know, the DocBook project (as distinct from the DocBook TC, 
 though many people participate in both activities) applied to the program 
 several times and was accepted twice. The program has brought us some useful 
 software and, even more important, new contributors to the DocBook community.

 To participate this year, we need two things:

 1) Mentors: we need at least 5 or 6 people who are willing to participate as 
 mentors.
 2) Ideas: we need ideas for projects that students can work on.

 I'm willing to be the organization administrator again this year, but I'm 
 glad to hand over responsibility if someone else wants the job this year.

 For the full schedule and more information about the program, go to:
 https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page

 February 20 is the deadline for applications. To participate, we need to have 
 mentors lined up by February 9, which is the opening date for filing 
 applications.

 If you're interested in participating, you can reply to this message on the 
 list or send me email directly at the address below.

I'd be happy to mentor, if I have the required knowledge depending on
the topic. (I'll think of ideas for the ideas page. Do we have a place
where to put those for this year ?)

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Restrictive Docbook XML editor which enforces Docbook schema?

[Stefan Seefeld]

On 15/01/15 10:01 AM, Dan Shelton wrote:
 Is there a Docbook XML editor which enforces the Docbook schema during 
 editing?

 I am looking for an editor which loads the Docbook XML schema and then
 only allows the creation of tags which are allowed at the current
 position in the XML document.

My favourite one is XMLMind's XXE: http://www.xmlmind.com/xmleditor/

FWIW,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Restrictive Docbook XML editor which enforces Docbook schema?

[Stefan Seefeld]

On 15/01/15 10:13 AM, Dan Shelton wrote:
 On 15 January 2015 at 16:04, Stefan Seefeld ste...@seefeld.name wrote:
 On 15/01/15 10:01 AM, Dan Shelton wrote:
 Is there a Docbook XML editor which enforces the Docbook schema during 
 editing?

 I am looking for an editor which loads the Docbook XML schema and then
 only allows the creation of tags which are allowed at the current
 position in the XML document.
 My favourite one is XMLMind's XXE: http://www.xmlmind.com/xmleditor/

 OK, but is there an opensource version which doesn't rely on java?

I'm not aware o any Free XML editor that is comes close to what I would
expect any XML editor worth its name to be able to do. I regularly look
for alternatives (myself preferring Free Software if possible), but
always come back disappointed.
http://en.wikipedia.org/wiki/Comparison_of_XML_editors gives you an
overview.
(Additional constraints such as no java reduce your chances even
further...)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] support for xpointer

[Stefan Seefeld]

On 2014-09-14 16:36, Richard Hamilton wrote:
 Hi Stefan,

 I didn't say it was elegant:-).

 I agree that DocBook transclusion may be the way to go. I need to look into 
 it further for our book process.

 And a multi-stage process works well for us. Maybe it's my long experience 
 with Unix, but I use multi-stage processes all the time. They let you use the 
 right tool for each step in the process and give you intermediate files that 
 you can examine when things go wrong.

Right. The disadvantage is that the original document no longer is a
valid DocBook document, and thus requires RNG customization to make my
editor happy (not to mention that the transclusion no longer is a
transparent process).

Ideally I would like to be able to encode the query in an attribute,
much as I would have preferred with xpointer, such as

listitem my:ref=*[@xml:id='foo']//d:listitem /

However, I can't manage to extract the above ref into a variable and
concatenate that into a valid xpath expression inside a custom stylesheet:

xsl:template match=*[@my:ref]
  xsl:variable name=ref select=@my:ref /
  xsl:variable name=content select=document('dict.xml')//$ref /
  ...
/xsl:template

It seems I'm misunderstanding something, as no matter how I spell the
above, I get XPath errors from xsltproc.
The only thing that seems to work is me injecting individual names into
an XPath expression, such as

  xsl:variable name=content
select=document('dict.xml')//d:section[@xml:id=$ref]//listitem[2] /

which however severely limits my flexibility as it supposes a fixed
structure (include the second listitem of the identified section). Am
I asking too much ?

Many thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] support for xpointer

[Stefan Seefeld]

Hi Thomas,

On 2014-09-19 10:17, Thomas Schraitle wrote:
 Hi Stefan,

 On Fri, 19 Sep 2014 09:53:33 -0400
 Stefan Seefeld ste...@seefeld.name wrote:

 [...]
 Ideally I would like to be able to encode the query in an attribute,
 much as I would have preferred with xpointer, such as

 listitem my:ref=*[@xml:id='foo']//d:listitem /

 However, I can't manage to extract the above ref into a variable and
 concatenate that into a valid xpath expression inside a custom
 stylesheet:

 xsl:template match=*[@my:ref]
   xsl:variable name=ref select=@my:ref /
   xsl:variable name=content select=document('dict.xml')//$ref /
   ...
 /xsl:template

 It seems I'm misunderstanding something, as no matter how I spell the
 above, I get XPath errors from xsltproc.
 Yes, as you try to dynamically evaluate a string as an XPath
 expression. This is not possible with standard XSLT 1.0 and 2.0.

 However, you could look into the dyn:evaluate() extension functions from
 the EXSLT initiative:

   http://exslt.org/dyn/functions/evaluate/index.html

 You may try this, although I haven't tested it:

  xsl:template match=*[@my:ref] xmlns:dyn=http://exslt.org/dynamic;
xsl:variable name=ref select=dyn:evaluate(@my:ref) /
xsl:variable name=content select=document('dict.xml')//$ref /
...
  /xsl:template

Great, it seems dyn:evaluate() is exactly what I'm looking for. Note
that I had to rephrase the above a little, as the way you wrote it
wouldn't work, since the evaluation of the (dynamic) xpath only makes
sense in the context of the doct.xml document, and thus can't be done
outside it.

But with that little adjustment I now get the expected result. It's
still not very pretty, but a huge step in the right direction.

 Unfortunately, very few XSLT 1.0 processors implement dyn:evaluate().
 It works in xsltproc, but it's unlikely it will work for Saxon.

Yeah, tools support has always been a great bottleneck with XML
processing. :-(

Many thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] support for xpointer

[Stefan Seefeld]

On 09/14/2014 05:09 AM, Jirka Kosek wrote:
 On 14.9.2014 3:22, Stefan Seefeld wrote:
 Can anyone confirm the state of xpointer support in xsltproc, or any
 other Free XSLT processor for that matter ? (For example, what about
 saxon ?) Are there any (free) test suites that I could use to get a
 sense of what is supported and what not ?
 AFAIK only thing which is reliable and works across different
 implementations is referencing node by its ID. Very sad.

That's sad indeed. I was trying to fetch a specific subnode of an
identified element, but couldn't manage to get that working with
xsltproc (haven't tried with saxon yet), so I was looking for working
examples.

(I'm not even sure what the right spelling is to express second
listitem within a section with id demo  using xpointers. And xsltproc
typically doesn't even give an error. It simply ignores the entire
xpointer attribute :-( )

 There is XInclude test suite, which has some XPointer tests as well:

 http://dev.w3.org/cvsweb/2001/XInclude-Test-Suite/

Thanks. These tests all are rather old, and limited as far as I can see.
Hasn't there been any recent activity on xpointers recently ? What other
tools for transclusion are people using nowadays ?

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] support for xpointer

[Stefan Seefeld]

On 09/14/2014 02:02 PM, Richard Hamilton wrote:
 Regarding the question of pulling the second listitem from a section with a 
 particular id, I think the following will do the trick (I don't claim it's 
 the most elegant way to do this, but it works with xmllint):

   xi:include href=filename.xml
   
 xpointer=xmlns(d=http://docbook.org/ns/docbook)xpointer(//d:section[@xml:id='sect-a']//d:listitem[2]))/

Thanks, that works indeed !
But the syntax is rather verbose and cumbersome, especially given that I
want to establish references such as the above for a couple of hundreds
of definitions in a single (modular) document.
I'm considering defining my own technique (drawing inspiration from
http://www.docbook.org/docs/transclusion/transclusion.html), then using
a two-phase processing with the first doing the transclusion processing
to generate valid DocBook, then the second to do the actual formatting.

Thanks for all the help (and the continued work that goes into DocBook's
evolution),

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] support for xpointer

[Stefan Seefeld]

Hello,

Sorry if the following is slightly off-topic.

I'm trying to refactor a large docbook document (an API specification)
into multiple documents, including relevant chunks of content from a
meta-model document into a language-bindings document via xinclude /
xpointer.

I played a bit with the sample code from
http://www.sagehill.net/docbookxsl/ModularDoc.html, using xsltproc
(Using libxml 20901, libxslt 10128 and libexslt 817) on Fedora 20, with
mixed results. While I got simple cases working, slightly more advanced
cases led to wrong results, letting me doubt the quality of the
implementation of xpointer support in xsltproc.

Can anyone confirm the state of xpointer support in xsltproc, or any
other Free XSLT processor for that matter ? (For example, what about
saxon ?) Are there any (free) test suites that I could use to get a
sense of what is supported and what not ?

Many thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Numbered paragraphs

[Stefan Seefeld]

On 08/01/2014 06:47 PM, Richard Hamilton wrote:
 Before I dive into a customization, has anyone ever customized the fo 
 stylesheets to generate paragraph numbers? That is, sequentially numbering 
 every paragraph in a book from the beginning to the end.

 The ideal would be to put them into the margin, but I'd be happy with any 
 method that assigned a sequential number to each paragraph.

For an OMG specification I have used ordered lists to wrap all text to
get essentially the same effect as you seem to seek (see
http://www.omg.org/spec/VSIPL++/1.2/PDF/).
You can find my customization in
https://github.com/vsip/specs/tree/master/xsl, though this may look like
a set of crude hacks to trained eyes. (Feel free to clone at your
leisure)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] epub3 mathml rendering

[Stefan Seefeld]

Hi Tim,

On 06/30/2014 02:35 PM, Tim Arnold wrote:
 Hi,
 This may not be a docbook issue, I'm not sure.

 I'm using epub3 stylesheets (1.78.1) from DocBook5 + MathML.
 The math is passed through to the xhtml content using the 'mml':
 namespace alias for MathML. 

 However, the MathML is not rendered in either Readium or Calibre. When
 I manually remove the namespace from the math blocks, Calibre can then
 render the math (Readium still fails).

 So my question: 
 For anyone successful in rendering mathml in epub3, what incantation
 are you using?
 and should the namespace be removed before packing up the epub?

 That is, from this (as rendered from the 1.78.1 epub3 stylesheets):
 mml:math xmlns:mml=http://www.w3.org/1998/Math/MathML; display=inline
 mml:mo\xc3\x97/mml:mo
 /mml:math

 to this:
 math display=inline
 mo\xc3\x97/mo
 /math

I'm sorry I can't answer your specific questions. However, I did observe
some issues with the math rendering in firefox. First, the output had to
be xhtml, not html, and second, the files really needed to use the
.xhtml extension. I didn't quite understand why, though, and haven't had
the time to investigate.

FWIW,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] document reviewing ideas

[Stefan Seefeld]

On 01/02/2014 03:57 PM, Mats Wichmann wrote:
 A little backstory here...

 I inherited a specification document that was written in MS-Word.
 Although not my preferred format, existing institutional familiarity
 meant I didn't initially have the option to change.  However, when the
 project evolved and it became clear I'd have to produce a half dozen or
 more variants of the document, while maintaining large chunks of the
 content as common text, I went ahead and did the conversion to docbook
 to maintain some semblance of my sanity.

I know exactly what you are talking about, as I went through pretty much
the same process. (The icing on the cake for me was that the Object
Management Group, to which I submitted the specification, is actually
keen on structured documents, and was very supportive of DocBook, even
though in practice most of the world still submit their docs as MS Word
documents, which are then turned into formal specs by some in-house staff).

 The problem I now have is my existing internal customers are used to
 reviewing with a wysiwyg tool (namely, Word) so they can markup and
 comment inline. Turns out I haven't had luck generating stuff Word can
 read directly, but it comes out at least acceptably if you feed it html.
  However... it doesn't seem ideal to convert to another format for
 reviewing, then have to backport things to the master. This might be a
 case for the roundtripping stuff (dbk2wordml) but I can't get a usable
 doc out of that at all.

That's an interesting question indeed. I'm also not sure what would be
ideal here, as changing the sources doesn't seem appropriate either. It
probably depends on many other factors, such as how the sources are
controlled (version control ?), and whether the reviewers are technical
people who also author using DocBook, or whether they are merely reading
and feeding back comments / annotations.
What would be nice, but is probably overkill for most users, is a system
of externally held annotations as once was propagated by the Annotea
project (http://www.w3.org/2001/Annotea/). I have no idea what became of
that, though.

 So... asking for advice.  What do people typically do when it's time to
 pass a document around to multiple reviewers?  I'm not convinced
 something like Word is the best answer even there (you end up having to
 review serially, not in parallel, or you'll go nuts reconciling the
 comments in multiple different docs, but it's certainly comfortably
 familiar to folks whose companies run on MS-Office).  Is there a better
 way that ties in well with having sources in docbook?

Again, depending on the scale of your use-case (how many documents are
being reviewed, how many reviewers are working in parallel, etc.)
different approaches may work best. I have seen tools plugged into
websites, enabling visitors to leave annotations there. That made a lot
of sense for community projects (I think this was www.boost.org I'm
thinking of). Personally I have had people review pdfs and just annotate
those directly (and me incorporating changes back into DocBook manually).

DocBook 5 also has some vocabulary to store annotations, though I doubt
that that's appropriate for short-lived annotations that only a single
person (the author) will consume.

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] Need help using MathML (Unknown formatting object {http://www.w3.org/1998/Math/MathML}math encountered)

[Stefan Seefeld]

On 12/06/2013 05:20 AM, Daniel Bishop wrote:
 Hello,
 I am rather new to docbook, but I have been successful using docbook
 (installed in Ubuntu 13.10) except for MathML content. Any math
 formatting is missing in the html output, and the pdf output is
 totally lacking the math content (not only the formatting).

 Can you please check the detailed description below and suggest how I
 can start working with MathML content to produce both html pages and
 printed documents with nicely formatted formulas?

 I have installed the following packages in ubuntu 13.10:
 $sudo apt-get install xsltproc docbook-xsl docbook-defguide fop
 docbook-xsl-doc-pdf docbook-mathml

 I am trying to process the following example (from
 http://www.docbook.org/tdg5/en/html/_any.mml.html) into html and pdf:

 test.xml:
 
 article xmlns='http://docbook.org/ns/docbook'
   xmlns:mml=http://www.w3.org/1998/Math/MathML;
 titleExample mml-math/title
  
 informalequation
 mml:math
   mml:msup
 mml:mix/mml:mi
 mml:mn3/mml:mn
   /mml:msup
 /mml:math
 /informalequation

 /article
 

that looks good...


 First I process test.xml into test.html with the following output:
 
 $ xsltproc -o test.html
 /usr/share/xml/docbook/stylesheet/nwalsh/html/docbook.xsl test.xml
 Note: namesp. cut : stripped namespace before processing  
 Example mml-math
 Note: namesp. cut : processing stripped document  
 Example mml-math
 $
 

You should use namespace-aware stylesheets to process this input (see
http://docbook.org/docs/howto/).


 The equation shows as x 3 in test.html (the superscript is ignored).
 Other MathML pages appear correctly in my firefox browser.

I'm observing the same. I'm not exactly sure why FF is behaving that
way, but when I produce XHTML instead of HTML, and use the .xhtml
extension for the generated files, the superscript displays fine.




 Next, I process test.xml into test.pdf with the following output:
 
 $ xsltproc -o test.fo
 /usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl test.xml
 Note: namesp. cut : stripped namespace before processing  
 Example mml-math
 Note: namesp. cut : processing stripped document  
 Example mml-math
 Making portrait pages on USletter paper (8.5inx11in)
 $ fop -pdf test.pdf -fo test.fo
 Unknown formatting object {http://www.w3.org/1998/Math/MathML}math;
 encountered (a child of fo:instream-foreign-object}. (See position
 2:29495)
 Unknown formatting object {http://www.w3.org/1998/Math/MathML}msup;
 encountered (a child of math}. (See position 3:17)
 Unknown formatting object {http://www.w3.org/1998/Math/MathML}mi;
 encountered (a child of msup}. (See position 4:17)
 Unknown formatting object {http://www.w3.org/1998/Math/MathML}mn;
 encountered (a child of msup}. (See position 5:17)
 Font Symbol,normal,700 not found. Substituting with Symbol,normal,400.
 Font ZapfDingbats,normal,700 not found. Substituting with
 ZapfDingbats,normal,400.
 The intrinsic dimensions of an instream-foreign-object could not be
 determined. (See position 2:29438)
 Rendered page #1.
 $
 

Again, use namespace-aware stylesheets.

In addition, I had to patch my fop installation to make it handle MathML
correctly. Whether that is an actual problem for you depends on the
platform you are on, as well as the specific FOP version you are using.

Hope this helps,

Stefan



 The pdf file shows nothing but the title.

 What is wrong? Do I need to install additional packages? Can you show
 a MathML example that renders correctly with the described setup?

 Thank you
 Daniel


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] Need help using MathML (Unknown formatting object {http://www.w3.org/1998/Math/MathML}math encountered)

[Stefan Seefeld]

On 12/06/2013 10:23 AM, Daniel Bishop wrote:
 Concerning the math formatting only working in xhtml, not in html
 files, I followed Stefans advice. He is right, and I can create
 working xhtml files.
 It is strange that the formatting doesn't work for html files.
 Renaming the generated test.xhtml to test.html removes all math
 content again.
 There are many examples that display MathML content in html files. Is
 there any possibility to make xsltproc produce such html files without
 missing content?

I don't quite understand what's going on there myself, but I would
suggest looking at the respective (x)html sources, and perhaps also pass
it through an online html validator tool, which may give hints at what
is wrong with the generated files.

Sorry I can't help more,

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] DocBook Technical Committee Meeting Minutes: 16 October 2013

[Stefan Seefeld]

On 2013-10-24 14:11, Bob Stayton wrote:
 Hi Mike,
 I think Norm's comment about add-ons was about managing how several
 independent add-ons could be applied at the same time without
 conflict. With multiple add-ons, each potential combination has to be
 checked.  He didn't give any more details.

Assuming each add-on uses its own namespace, what conflicts need to be
checked for ?


 The plan is to include the new slides schema and stylesheets in the
 next XSL distribution, but that work has not yet been done.

I'm again offering my help (as I have been doing since the end of the
project in fall 2012).
I would also like to see us participating in the Google SoC program next
summer again. However, it's hard to justify if we haven't even wrapped
up the integration of previous projects.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] PDF Output: calling a different page master for a specific element

[Stefan Seefeld]

On 2013-09-04 17:36, Jeff Hooker wrote:
 Hi all,

 I'd like to call a specific page master for an element that contains a 
 specific attribute value. Essentially, if for long, narrow tables I want to 
 be able to call a three-column page master that prevents it from flowing over 
 a 100 pages when 33 would do. I'm having issues figuring out how to call the 
 new master, and a certain degree of difficulty understanding the exact 
 hierarchy I'm working with here.

 I've been puzzling over the references in Docbook XSL trying to understand 
 how to apply them to this case, but have so far come up dry. Has anyone 
 written up a good explanation of this somewhere? 

While I haven't used this myself, it seems this might be relevant:
http://www.sagehill.net/docbookxsl/PageDesign.html#UsePageMasters

HTH,

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook snapshot SVN problem

[Stefan Seefeld]

Bob,

if that working copy doesn't contain any local edits, I suggest you
simply blow away the tree and check out out from scratch.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook/XSL: What's the Subversion/SVN URL of the docbook-xsl-ns and docbook-xsl stylesheets?

[Stefan Seefeld]

On 04/22/2013 11:39 AM, Shlomi Fish wrote:
 Hi all,

 Please let me know what is the Subversion/SVN URL of the docbook-xsl-ns and
 docbook-xsl stylesheets that can be found here:
 http://docbook.sourceforge.net/snapshot/ . I want to do an svn checkout/svn
 co command and update it using svn update/svn up.

The DB stylesheet sources are here:
https://docbook.svn.sourceforge.net/svnroot/docbook/trunk

Please note that there are no separate trees for xsl-ns and xsl. Both
packages are generated from the same sources. In fact, to be able to
work with the source tree requires quite a bit of insight knowledge of
the build process, as well as a bunch of prerequisite tools. Unless you
really know what you are doing it might be best to stick to prepackaged
releases / snapshots.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] using xpointer with modular DocBook

[Stefan Seefeld]

Hello,

I'm trying to refactor a DocBook document a little, moving certain
sections into an external document and xi:including them subsequently
using xpointers.

The document I want to refactor is a software API specification, where
each definition contains a small section I'd like to move out into a
separate (meta-model) document. The resulting API document will thus
contain hundrets of references to always the same external document,
pulling in different nodes for the different definitions.

The xinclude syntax I use right now looks like this:

  variablelist
xi:include href=../vsip/signal.xml
   
xpointer=xmlns(db=http://docbook.org/ns/docbook)xpointer(//db:varlistentry[@xml:id='foo'])/
  ...
  /variablelist

This works well, but introduces a lot of redundancy as for each chunk
I'd like to include I have to redefine the namespace used in the xpath
expression. Is there a way to avoid that, by making this the default in
some way ? If I just leave out the xmlns() I get an error as the
xpointer can't be resolved.
(I'm using xsltproc to process the DB documents.)

Thanks for any help with this,

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] using xpointer with modular DocBook

[Stefan Seefeld]

Hello Thomas,

On 04/14/2013 02:56 PM, Thomas Schraitle wrote:
 Hello Stefan,

 Am Sonntag, 14. April 2013, 14:08:03 schrieb Stefan Seefeld:
 [...]
   variablelist
 xi:include href=../vsip/signal.xml

 xpointer=xmlns(db=http://docbook.org/ns/docbook)xpointer(//db:varlistentry[
 @xml:id='foo'])/ ...
   /variablelist
 If I'm not mistaken, you can simplify the above xpointer expression as

   xpointer(id(foo))

 Not sure if this scheme is supported, but it maybe worth a try. Maybe you 
 need 
 quotes for id(...) so try both notations.

Yes, that works indeed. Unfortunately my real references are a little
more complex, as they don't have (explicit) ids. So I typically need to
refer to things such as the first varlistentry child of the node with
id ID.

 This works well, but introduces a lot of redundancy as for each chunk
 I'd like to include I have to redefine the namespace used in the xpath
 expression. Is there a way to avoid that, by making this the default in
 some way ? If I just leave out the xmlns() I get an error as the
 xpointer can't be resolved.
 (I'm using xsltproc to process the DB documents.)
 I don't think you can avoid the namespace. Have you tried entities? You could 
 define a entity (let's say dbxmlns) inside the internal subset of the DTD:

   !DOCTYPE chapter 
   [
 !ENTITY dbxmlns xmlns(db=http://docbook.org/ns/docbook)
   ]

 and use it like this:

   xi:include href=../vsip/signal.xml
   xpointer=dbxmlns;xpointer(id(foo))/

 Entites are resolved before any xinclude processing is done. If this works, I 
 think this should be compact enough. ;)

Indeed, that works. Thanks for the tip !
However, I'd rather prefer to avoid entities. The document will be
edited with XML editors such as XMLMind's XXE, which would discard
(substitute) the entities.
(Of course, if everyone used such editors it wouldn't matter, but since
some use normal text-based editors, I'm looking for a solution that
works everywhere.

Thanks again for your help,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] using xpointer with modular DocBook

[Stefan Seefeld]

On 04/14/2013 03:24 PM, Thomas Schraitle wrote:
 If your variablelist has the ID foo and you want to refer to the
 first varlistentry you can write:
 xmlns(db=http://docbook.org/ns/docbook)xpointer(id(foo)/db:varlistentry[1])


Right, but that doesn't solve my problem of having to repeat the
namespace declaration. :-)

 (Of course, if everyone used such editors it wouldn't matter, but since
 some use normal text-based editors, I'm looking for a solution that
 works everywhere.
 I don't think there is a general solution where you define somewhere the 
 namespace and just refer to it. It seems, you need to add the namespace 
 xmlns() scheme every time.

That's unfortunate. I was hoping there was a mechanism such as
xmlns-local() to export the namespaces from the current document into
the xpointer context.

 Maybe you add the xmlns() XPointer scheme before passing it to your XML 
 parser. You could (theoretically) apply an XSLT transformation step and add 
 the xmlns() scheme. That way you could avoid entities, however, you add an 
 additional step (which may not be useful).

I wouldn't mind the additional step, but I don't like the idea that the
unprocessed document isn't valid any longer.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Some text after a section

[Stefan Seefeld]

On 04/09/2013 08:00 AM, markus.sticker.e...@zf.com wrote:

 Hi,

  

 I tried to have some text (maybe as para)after a section(parent chapter).


By some text I assume you are referring to the preprocessor instructions.
What's the purpose of those in your document ?

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: AW: [docbook] Some text after a section

[Stefan Seefeld]

On 04/09/2013 08:23 AM, markus.sticker.e...@zf.com wrote:
 Hi (and Moin Moin),

 it is a technical document, and we use the Draft Mode to have the 
 processing-instructions
 inside the document. So we get one pdf with all possible variants inside.

DocBook has its own way to (semantically) mark up conditional sections
(see http://www.sagehill.net/docbookxsl/Profiling.html).
If you customize the appropriate stylesheets you may be able to generate
output with the conditionals highlighted appropriately.

The way you try to represent the conditionals violates the document
structure, and thus doesn't work with DB.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: AW: AW: [docbook] Some text after a section

[Stefan Seefeld]

On 04/09/2013 08:45 AM, markus.sticker.e...@zf.com wrote:
 So how to get the content  of the pi written after this section? will be 
 the 
 question I have to think of.

It might be better to think of your PIs as conceptually being part of
the section, and then format them using a template customization. In any
case, you are operating outside the DB vocabulary, so should be prepared
for the required work to extend the schema and stylesheets.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: AW: AW: AW: [docbook] Some text after a section

[Stefan Seefeld]

On 04/09/2013 10:25 AM, markus.sticker.e...@zf.com wrote:
 Hi,

 thank you, Stefan. This is a good advice but don't meet my problem/question.
 Also I if use profiling, the issue will remain.

Your question reminds me a little of how people who aren't trained to
think in terms of structured documents approach styling questions, for
example by asking how can I make this text bold, instead of thinking
about the semantics of the desired style. You were asking how to add
highlighted text that's fully oblivious to the document structure, and
my advise was to instead think about the semantics of the annotation you
want. My understanding was that in fact the text you want isn't
oblivious to the document structure, quite the opposite: it's an
annotation of document structure, which you just happen to want to put
outside the formatted section instead of inside.
I believe that thinking along those lines will make it easier to get to
a solution that works with DocBook and not against it.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] GSoC Application

[Stefan Seefeld]

On 04/08/2013 03:17 PM, Richard Hamilton wrote:
 Looks like odd-numbered years are not good for DocBook at GSoC.

 Our application for this year's GSoC program was rejected.

That's sad news indeed. Please don't read to much into that decision
though (such as how our ideas page could have been at fault); the
decisions whether or not to accept an organization aren't entirely
deterministic, AFAICT...

 Thanks to everyone who volunteered to be a mentor and for the interest from 
 prospective students. I hope that some of the ideas generated for this year's 
 program can get implemented in other ways. If not, they can form the basis 
 for another try next year.

Indeed, let's hope all the enthusiasm and work that went into preparing
and discussing ideas so far wasn't wasted.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] GSoC Project Idea: integrated LaTeX output support for the stylesheets

[Stefan Seefeld]

On 04/06/2013 09:03 AM, Jirka Kosek wrote:
 On 5.4.2013 22:40, Gábor Kövesdán wrote:

 Having this solution, would you still be interested in a more integrated
 solution that follows the conventions of the DocBook XSL stylesheets and
 allows tuning with parameters and easy customization? Are there any
 serious problems in dblatex that aren't solved for you? Any
 functionality that you preferred to be implemented in a different way?

 Hi,

 if you will develop another XSLT based DB-TeX solution I strongly
 suggest to use XSLT 2.0 and reuse shared code from
 https://github.com/docbook/xslt20-stylesheets

The primary reason for this work is to get rid of fop as a dependency to
create pdfs.
As far as I'm aware, at this point there is a single (Free) processor
that can handle XSLT 2.0, so overall the situation wouldn't be much
better for the purpose of helping the FreeBSD community to move to an
XSL-based DB processing flow.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] GSoC Project Idea: integrated LaTeX output support for the stylesheets

[Stefan Seefeld]

Hi Gabor,

On 04/05/2013 09:09 AM, Gábor Kövesdán wrote:
 Hi,

 I plan to apply to this year's Summer of Code and I wanted to share my
 idea with you for discussion. 

That's great to hear. I very much share your concern for the lack of
tools to transform DB to printable media, and therefore support the idea
to work in that area. I do have a few questions about your suggested
approach, though.

 There are two projects, db2latex and dblatex, which provide such
 functionality but they do not integrate well with the existing
 stylesheets and dblatex also introduces a new dependency, Python.

Can you elaborate a little how you would reuse existing stylesheets in
your approach ? AFAIU they are all specific to a particular output
medium (e.g. HTML or FO), and so the only way to reuse them would be to
process the generated FO instead of DB, no ?
I'm also not concerned about Python as a dependency. It is widely
available, and seems to me to be a better tool to translate XML to LaTeX
than XSLT. However I'd be happy to learn otherwise. :-)

 Do you also think it is useful? Any potential mentors? Please share
 your thoughts.

While I'm concerned about the scope of the project, I'd be happy to
mentor you again this year.

Regards,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] GSoC Project Idea: integrated LaTeX output support for the stylesheets

[Stefan Seefeld]

On 04/05/2013 10:38 AM, Gábor Kövesdán wrote:
 Em 05-04-2013 15:26, Stefan Seefeld escreveu:
 There are two projects, db2latex and dblatex, which provide such
 functionality but they do not integrate well with the existing
 stylesheets and dblatex also introduces a new dependency, Python.
 Can you elaborate a little how you would reuse existing stylesheets in
 your approach ? AFAIU they are all specific to a particular output
 medium (e.g. HTML or FO), and so the only way to reuse them would be to
 process the generated FO instead of DB, no ?
 I'm also not concerned about Python as a dependency. It is widely
 available, and seems to me to be a better tool to translate XML to LaTeX
 than XSLT. However I'd be happy to learn otherwise.:-)
 There are couple of general templates and facilities, e.g. those that
 handle localized text and the titlepage generation mechanism. I mean
 here integration and not strict reuse. People would be able to use
 these stylesheets with the same conventions as they use XHTML and FO
 stylesheets, that is, generating a titlepage, setting XSLT parameters
 to control behavior and overriding certain templates, in which they
 can insert localized templates or use e.g. the object.id template. It
 could be shipped with the DocBook XSL distribution and could have a
 similar reference documentation of XSLT parameters?

OK, that makes sense.


 If you prefer Python, it could be an alternative but I'd like to
 provide a purely XSLT-based mechanism, as well. According to my
 estimation, it would require very minimal coding.

Fair enough.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Specify FO output font size in xml element?

[Stefan Seefeld]

On 04/05/2013 08:57 PM, Eric Nordlund wrote:
 Thanks Richard. I have used the attribute sets for the entire document, but 
 some of my examples are too long to fit on the page and I want to shrink the 
 font size for only that instance so I can fit it without compromising the 
 rest of the verbatim blocks.

For such cases I have been using the role attribute:

* Use something like verbatim role=extra.small.text.../verbatim

* Define a template like xsl:template
match=verbatim[@role='extra.small.text'] and reduce the font size to
your hear's content (for example by adding xsl:attribute
name=font-size70%/xsl:attribute to your putput).

Hope that helps,

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Company logo in title page (non-standard, I already RTFM)

[Stefan Seefeld]

Hi Eric,

On 04/04/2013 01:43 PM, Eric Nordlund wrote:
 So, here is my question: can I use a template to add a static mediaobject 
 to the bookinfo element before the title page xslt happens? I added a small 
 template to my customization layer that sort of works (it adds the 
 mediaobject, but then FOP crashes when it tries to make the PDF). Here is 
 the template I added:

[...]

What you describe sounds like a two-stage workflow, where you first
process your document one time, inserting a mediaobject, then take the
resulting XML file and process that a second time to generate FO output
from that. That should indeed work. What doesn't work is to inject a
mediaobject in the generated FO (since then it wouldn't be valid FO any
longer).
However, I wonder why you want to inject a mediaobject in the first
place, instead of a fo:graphic. Making the graphics part of the
stylesheet allows you to not having to change all your document sources
and still get the desired graphics into the pdf, when using that custom
stylesheet.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] [HELP] How can I get rid of the output of the revhistory / tag in the EPUB output

[Stefan Seefeld]

On 03/26/2013 12:48 AM, Shlomi Fish wrote:
 Hi all,

 can anyone reply to my post with an answer? I have waited a long time enough
 after wasting a lot of time waiting for an answer on #docbook on Freenode. 

Shlomi,

someone already pointed out to you on IRC that you were pretty rude
there. Now you are dragging that same rudeness into this mailing list.
Please stop it.
If no-one has answered yet, it's likely because everyone is busy, and
you don't get people to be less busy or more helpful by requesting an
answer or being rude.
That's not going to work.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Docbook to PDF via FOP question which related to ANT

[Stefan Seefeld]

On 02/20/2013 11:30 AM, Lars Vogel wrote:
 Hi,

 not sure if this is the right distribution list.

It seems the question is about ant, not docbook, so you may look for an
ant-related forum (or apache fop, if this is about fop's behaviour) to
ask such questions.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] About FOP 1.1

[Stefan Seefeld]

Jacques,

I'm using fop 1.1 with my own documents successfully.
However, I have never used fop to handle the first DB-FO
transformation. Instead, I'm using xsltproc to generate the FO, then fop
to translate that to PDF.
This might work for you, too, i.e. allow you to debug the problem with
missing parameters when using your custom stylesheet.

FWIW,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] How do you manage your catalogs ?

[Stefan Seefeld]

On 12/10/2012 10:21 AM, Kerry, Richard wrote:
  
 The easiest thing to do would be an editor as XMLMind's XXE 
 (as Stefan 
 Seefeld pointed out), or Oxygen XML Editor which my 
 department is using. 
 That involves buying some editors as we don't currently have any; though I 
 think XXE can be used for free so that might be a possibility for the moment.

Absolutely. There are many XML editors available, some Free, some
proprietary. The choice shouldn't matter for the workflow.
 Creating common formats like HTML, XHTML, PDF, and EPUB is 
 pre-configured in Oxygen, so it's just a matter of a few clicks to 
 produce those formats.
 Because we're used to seeing a particular style of results I'd need to 
 customize this, which is what I'm doing with the stylesheets at the moment.
  
 We've set up a 
 make-based system that works the exact same way on the central build 
 server and when run locally; for example (for a document 
 named book.xml):

 * 'make book.valid': runs xmllint and other tools to validate book.xml
 * 'make book.html'
 * 'make book.pdf'
 * 'make book.epub'
 * etc.
 I'd need to hide the specific tool as my colleagues aren't used to 
 command-line tools in general, and make in particular.  

That was one reason why I suggested a tool like xxe: It offers a very
convenient GUI to structural documents authoring which may make the
transition easier for people coming from MS Word. But if for you DocBook
is just an intermediate format that may not be very useful.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] customizing index generation

[Stefan Seefeld]

Hello,

I'm writing an API reference manual for a library, whose symbols all
start with a common prefix. Having added one indexterm per symbol, the
generated index now contains a list with a single letter - the first
letter of the shared prefix.

So, having foo_something and foo_other would now generate a single
letter F under which both symbols are listed.

Is there a way to strip off the common prefix for purposes of index
generation only, that is without actually removing the prefix from the
indexed symbols themselves ?

So, The two symbols foo_something and foo_other above would end up
in two sections, the first under S, the second under O.

Is that possible ?

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...

-
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] How do you manage your catalogs ?

[Stefan Seefeld]

On 12/07/2012 10:14 AM, Kerry, Richard wrote:

  

 Peter,

  

 So yours is a workflow where the XML writers don't produce final
 outputs themselves.  Indeed many/most of them can't do so as they
 don't have the publishing tools.

  

 Is this the common way DocBook authoring and publishing are done ?


I'm not sure about what is most common, but in my organization all
developers have everything available for local builds, so they can
actually review the generated html and pdf while working on
documentation (and in some cases styling).

We mostly work on GNU/Linux platforms, using a variety of distributions
(Ubuntu, Fedora, etc.), for which docbook packages exist containing all
that is needed (including correct catalogs).

Note that we also use proprietary editors (such as the excellent XMLMind
XML Editor (http://www.xmlmind.com/xmleditor/), which I find extremely
convenient for authoring. That includes its own set of stylesheets,
dtds, rngs, and likely catalogs, so provides a self-contained
environment for authoring.

FWIW,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] n00b

[Stefan Seefeld]

On 12/04/2012 03:29 PM, Marja van Waes wrote:

 Someone advised me to subscribe to this mailing list, to get the
 answers to my questions.

That was good advise. However, merely subscribing isn't enough - you
also need to ask the questions. :-)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...



-
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] How to style db 4.2 html output made with dsssl

[Stefan Seefeld]

On 11/06/2012 11:27 AM, Karl O. Pinc wrote:
 Hi,

 I'm trying to improve a table of PostgreSQL error codes
 in the PostgreSQL docs.

 Postgresql uses Docbook 4.2 and openjade/dsssl style sheets.

Is there even a remote chance for you to migrate to XSL stylesheets ?
I'm not sure the DSSL ones are maintained at all at this point, so
improvements, fixes, and customizations are much easier to get with XSL.

FWIW,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] semantics of replaceable element.

[Stefan Seefeld]

On 11/06/2012 01:54 PM, Bob Stayton wrote:
 According to http://docbook.org/tdg/en/html/parameter.html parameter is
 allowed inside function.

 More research shows that parameter is allowed in function DocBook 4,
 but not DocBook 5.  In DocBook 4, function could contain all kinds of
 elements, and it was apparently used to present function syntax as
 well, based on that early stylesheet template.

 It seems that the elements for documenting function syntax were
 changed significantly in DocBook 5.   To show the syntax of a function
 in DocBook 5, you should use funcsynopsis. The function element itself
 is now only used to name a function, typically inline, so that is why
 parameter is no longer allowed in function.

Right, that's exactly how I use the markup. Thanks for confirming that.


 Regarding the semantics of replaceable, I use it when I need to
 indicate user input in which the text that is shown would not make
 sense if used literally.  So I don't think it would be used for
 function parameters, which do make sense as variables in an
 expression.  I would use it for replaceablelogin-name/replaceable
 and such, where if the user types login-name it would not work. Hope
 that helps.

That all sounds good to me. Thanks.

I'm still rather uneasy with the stylesheet's attempt to synthesize
language-specific syntax with all the synopsis markup elements. But that
really is an entirely separate discussion. (And a while ago we have
worked on an extension vocabulary to add proper support for modeling (at
least C and C++).

So, I think it would be best if replaceable would not attempt to
synthesize programming-language syntax. But the solution to
conditionalize that behavior based on an attribute setting also sounds
like a good fix.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] semantics of replaceable element.

[Stefan Seefeld]

Hello,

I'm writing an API documentation for generic C code, where certain
tokens in a given (function) name are to be substituted to map the name
to a real function name. For example, I'm using
functioncompute_replaceablet/replaceable/function to stand for a
set of functions compute_f, compute_d, compute_i, etc.

It even happens that certain names contain multiple such replaceable
parameters.

However, the stylesheets at present inject commas, which makes it
impossible to have replaceable tags in the middle of a name. I'm
reading http://docbook.org/tdg/en/html/replaceable.html but it doesn't
suggest anything that would justify such a comma injection.

What is the use-case for this ? Am I using replaceable wrongly ? (I
can of course customize the template matching d:function/d:replaceable,
but it still seems I'm missing something.

Any help would be appreciated.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] semantics of replaceable element.

[Stefan Seefeld]

On 11/05/2012 06:50 PM, Richard Hamilton wrote:
 Hi Stefan,

 I suspect the problem is in your customization. I just tried this with 1.77.1 
 (PDF and HTML), and there were no commas inserted in the output.

Hi Richard,

thanks for following up so quickly. I don't yet use a customization for
this. Please have a look at either the fo/inline.xsl or html/inline.xsl
stylesheets and look for the template matching
d:function/d:replaceable. It does indeed add a comma if there is more
content after the replaceable element:

xsl:template match=d:function/d:replaceable priority=2
  xsl:call-template name=inline.italicmonoseq/
  xsl:if test=following-sibling::*
xsl:text, /xsl:text
  /xsl:if
/xsl:template

(In my docs I have things like
functionvsip_replaceabled/replaceableclip/function, such that
the comma would be inserted between the 'd' and the 'clip'.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] semantics of replaceable element.

[Stefan Seefeld]

On 11/05/2012 08:37 PM, Richard Hamilton wrote:
 I just looked at the stylesheets, and they include a parameter called 
 function.parens, which when set will take input of the following type:

 functionfooreplaceablex/replaceablereplaceabley/replaceable/function
 and render it as: foo(x, y).

I see. But isn't that the wrong markup for this desired output ?
Shouldn't that use parameter instead of replaceable ?

 The problem seems to be that the template for d:function checks this 
 parameter, but the template for d:function/d:replaceable (and 
 d:function/d:parameter) doesn't . The result when function.parens is set to 0 
 is inconsistent.

 I think the following change would fix the problem for Stefan, and leave the 
 capability in for anyone who wants to use function.parens:

 xsl:template match=d:function/d:replaceable priority=2
   xsl:call-template name=inline.italicmonoseq/
   xsl:if test=$function.parens != '0' and following-sibling::*  !-- here 
 is the changed line --
 xsl:text, /xsl:text
   /xsl:if
 /xsl:template

 You'd need to do the same with d:function/d:parameter, too, though it appears 
 that parameter is not allowed inside function, so it may be a moot point.

According to http://docbook.org/tdg/en/html/parameter.html parameter is
allowed inside function.

But no matter what, it seems that these two usages of replaceable are
radically different, which seems to suggest that I still don't fully
grasp what a replaceable represents.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Where can I find this package?

[Stefan Seefeld]

On 10/17/2012 11:59 AM, Yves S. Garret wrote:
 Hello,

I'm trying to build git from source and one of the hang-ups that
 I'm experiencing is this.  I've run the following commands (which I
 found in INSTALL) and the error that I got is shown below the
 commands:

 Commands:
 $ make prefix=/usr all doc info ;
 $ make prefix=/usr install install-doc install-html install-info ;

[...]

 /bin/sh: line 1: docbook2x-texi: command not found
 make[1]: *** [user-manual.texi] Error 127
 make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation'
 make: *** [info] Error 2

 Now I'm just confused...


I believe you are looking for http://docbook2x.sourceforge.net/.
I'm not sure how to get a cygwin version for that, though. Or in fact
why anyone would still want to use texinfo when he has DocBook. But I
figure that's off-topic. :-)

Good luck,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] DocBook Technical Committee Meeting Minutes: 15 August 2012

[Stefan Seefeld]

On 2012-09-07 06:56, justus-b...@piater.name wrote:
 Are these Gabor Kovesdan's slides, or something else?

Yes.

Stefan


 Justus


 Bob Stayton b...@sagehill.net wrote on Wed, 15 Aug 2012 11:06:53
 -0700:

 8.  Add slides schema variant to DocBook 5?

 We discussed how to handle schema extensions at a previous meeting.

 ACTION: Bob to research what we decided before.

 Larry suggested that perhaps the slides extensions could be
 implemented in DocBook assembly, with outputformat=slides.
 Dick thought the DocBook website schema might fit into that
 as well.  

 ACTION: Bob to send the proposed slides schema to the TC.

 ACTION:  Larry to try mapping slides to assembly.


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] GSoC Just Concluded

[Stefan Seefeld]

On 2012-08-24 20:39, Richard Hamilton wrote:
 The Google Summer of Code just wrapped up, and I'm pleased to announce that 
 all four of our students passed their final evaluations.

 Congratulations to our students, Visitha Baddegama (Webhelp), Arun, Bharadwaj 
 (Webhelp), Buddhiprabha Erabadda (DocBook to Word XML roundtripping), and 
 Gihan Karunarathne (Support Output Suitable For Use On iOS And Android 
 Devices).


Richard,

please don't forget Gabor Kovesdan, who did great work on DocBook Slides !

Thanks Gabor for your great work !

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] docbook qandaset

[Stefan Seefeld]

On 2012-08-03 07:48, Mathieu Malaterre wrote:
 I am not looking for something like:
 http://www.sagehill.net/docbookxsl/HideAnswers.html I want to be able
 to display the question on the videoproject, leave 5 min to think,
 then display the answer. I really mean 'hide' temporarily, not remove.

You may be interested in the work that Gabor Kovesdan has been doing on
DocBook Slides, as part of this year's Google Summer of Code. There, a
new 'incremental' attributed is introduced, which is then used together
with new xhtml-based output media to add items incrementally to slide
presentations. I don't know whether that attribute is used in the fo /
pdf stylesheets. I imagine that the natural way to use it there would be
to regenerate the same page, but with an item previously hidden now
being displayed.

The above DocBook Slides work is planned to be merged into mainline over
the course of the next couple of weeks.


FWIW,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

[docbook] Re: [docbook-apps] Small!! Lightweight!! xslt processor which is standalone!! and runs Docbook/XSL stylesheets?

[Stefan Seefeld]

On 2012-07-30 09:12, Dan Shelton wrote:
 Does anyone know a small, lightweight xslt processor (doesn't need to
 be fast) written in ANSI/ISO C which can handle the Docbook/XSL
 stylesheets but does not depend on a quintillion of shared libraries?
 We want to use the Docbook/XSL stylesheets in our software package but
 ran afoul that we need a xslt processor installed and need to ship one
 if the underlying system doesn't have one. xsltproc ruled itself out
 because shipping all of it's dependencies means we have to ship 30MB
 of source code extra.

xsltproc is the best you can get. The required packages (libxml2 and
libxslt) are stable, portable, and as self-contained as possible.
(Running 'ldd' on libxml2.so and libxslt.so shows no dependencies other
than to the C runtime and libz for compression. And I'm pretty sure you
can avoid the latter if you are willing to recompile the packages to
explicitly disable compression support.)

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] Small!! Lightweight!! xslt processor which is standalone!! and runs Docbook/XSL stylesheets?

[Stefan Seefeld]

On 2012-07-30 09:12, Dan Shelton wrote:
 Does anyone know a small, lightweight xslt processor (doesn't need to
 be fast) written in ANSI/ISO C which can handle the Docbook/XSL
 stylesheets but does not depend on a quintillion of shared libraries?
 We want to use the Docbook/XSL stylesheets in our software package but
 ran afoul that we need a xslt processor installed and need to ship one
 if the underlying system doesn't have one. xsltproc ruled itself out
 because shipping all of it's dependencies means we have to ship 30MB
 of source code extra.

xsltproc is the best you can get. The required packages (libxml2 and
libxslt) are stable, portable, and as self-contained as possible.
(Running 'ldd' on libxml2.so and libxslt.so shows no dependencies other
than to the C runtime and libz for compression. And I'm pretty sure you
can avoid the latter if you are willing to recompile the packages to
explicitly disable compression support.)

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Mapping OMG / ISO specification files to DocBook

[Stefan Seefeld]

On 07/27/2012 04:35 PM, Bob Stayton wrote:
 Hi Stefan,
 Short of schema customization, the @role attribute in DocBook is the
 preferred mechanism to refine the semantics of an existing element
 into another element.  In a situation similar to yours, I used
 preface with role=frontmatter as the container for the special
 information, likewise because it required sections.  I customized the
 stylesheet to skip preface role=frontmatter when generating
 output, and I modified the titlepage templates to pull information
 from it where needed.  That makes such a preface more like an info
 container, which is not output by default but only handled as a
 special case.  I don't consider it an abuse of preface, as this
 information does come before the body of the document, and the role
 attribute makes it clear that it is not a normal preface.

OK. Perhaps the title of a preface could be made optional, then ?

 You also said:

 Please note that the OMG formally supports DocBook as input format for
 specifications.

 In what way do they support DocBook?

That's a good question, and it appears the OMG is trying to figure that
out right now. :-)

OMG allows for submissions of new standards to be made using the DocBook
format. Apparently, no-one had ever done that before, though. Most
people send in MS Word documents. In the process of adoption the
documents need to be reformatted, which typically means that an editor
will convert the original MS Word document into FrameMaker. To avoid
this, I'm now working on custom stylesheets that generate a (pdf) format
that corresponds to the OMG / ISO expectations. This would allow the
original DocBook sources to be retained, which a) makes life easier for
the editor, and b) allows me to incorporate new revisions of the
standard into the original DocBook documents.
Assuming all of this is working out as planned, I intend to publish the
stylesheets such that others can then use the same process.

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] parameter to control pdf bookmark generation

[Stefan Seefeld]

Hi Bob,

On 2012-07-16 02:00, Bob Stayton wrote:
 Hi Stefan,
 There is currently no param to turn off bookmarks, but a simple
 template customization will do it.  Add this to your customization layer:

 xsl:template match=* mode=fop1.outline/

 That will only turn off the bookmarks, while leaving any other fop1
 extensions in effect.

That's exactly what I'm doing. :-)

   This would make a good param, I suppose.

Yes. The need to disable bookmarks hadn't occurred to me before, but I'm
submitting an IEEE paper to http://pdf-express.org/ and the validator
complains about the bookmarks, so I'm trying to turn them off.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] embedding fonts in generated pdf

[Stefan Seefeld]

Hello,

this is not strictly a DocBook question, but I hope that the question is
common enough in this community that someone may actually be able to help.

For an IEEE paper submission I need to embed the used fonts into the
pdf. I'm using fop, and `pdffonts paper.pdf` reports

name  type  emb sub uni object ID
- - --- --- --- -
Helvetica Type 1no  no  no 181  0
Times-Roman   Type 1no  no  no 182  0
Times-BoldItalic  Type 1no  no  no 183  0
Courier   Type 1no  no  no 184  0
Times-Italic  Type 1no  no  no 185  0
Times-BoldType 1no  no  no 186  0

http://www.sagehill.net/docbookxsl/AddFont.html suggests that I need to
generate a font metrics file for the fonts I'd like to embed. So I'm
looking for the above fonts on my system (Fedora 17).

I have found a urw-fonts package, apparently containing ...good
quality versions of the 35 standard PostScript(TM) fonts However,
the font names don't match the above.

Any suggestion as to how to embed the standard (default) fonts when
generating pdf from DocBook ?

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] embedding fonts in generated pdf

[Stefan Seefeld]

On 2012-07-16 11:08, Ron Catterall wrote:
 Is this any use on creating the font metrics - from the MML2SVG
 documentation./

  These font metrics files are created with ttfreader tool that
 comes with FOP.

Ron,

thanks for the suggestion. I'm pretty illiterate as far as fonts and
font management is concerned. FOP is referencing Type 1 fonts, so how
would embedding TrueType fonts help here ? Don't I need to make sure the
very Type 1 fonts that are being referenced are embedded ?
Alternatively, I'd need to tell FOP to use different fonts (and font
types). But again, I have no idea how to do that.

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] embedding fonts in generated pdf

[Stefan Seefeld]

On 2012-07-16 13:28, Bob Stayton wrote:
 I second the suggestion of using fonts other than the standard fonts
 for embedding in PDFs. The Type 1 fonts you list are not embeddable
 unless you purchase the font outlines from Adobe and install them on
 your system.  The font outlines (the code that draws the letter
 shapes) are not included in any operating system that I know of
 because of that licensing fee. They were originally built into every
 printing device, and so the operating system only needed to the font
 metric files to set type in those fonts.  Windows substitutes Arial
 and Times New Roman TrueType fonts, which are embeddable.

Ah ! I sense slowly a consistent picture forming in my mind. :-)

Still, I seem to be missing some missing link. For example: Who or what
caused the generated pdf to reference Type 1 fonts, and what would it
take to switch to TrueType ?

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] embedding fonts in generated pdf

[Stefan Seefeld]

On 2012-07-16 14:49, Thomas Schraitle wrote:

 Still, I seem to be missing some missing link. For example: Who or what
 caused the generated pdf to reference Type 1 fonts, and what would it
 take to switch to TrueType ?
 Well, let me give you a short explanation. You start with the idea that you 
 want to use a different font in your document.

[...]

Thanks for the explanation. You are describing steps to change the
font-family. The issue I have above is not with font-families, but with
font types. The generated pdf is referring to various Type 1 fonts
(Times, Helvetica, Courier). I have locally installed the equivalent
TrueType fonts, and told FOP about them in the configuration file. But
it still generates pdfs referring to unembedded Type 1 fonts.
The change of a font family doesn't even enter the picture here, or does
it ?

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] parameter to control pdf bookmark generation

[Stefan Seefeld]

Hello,

I'm looking for an xsl parameter that allows me to suppress pdf bookmark
generation.
Looking at the code, I see that bookmark generation is conditional on
the value of fop1.extensions, which seems at least a little unintuitive.
While I could set that parameter to '0', it isn't clear what other
effects that may have. But ultimately, as end-user I don't actually want
to know about backend-specific extensions. (In fact, I may not even know
what backend is used to generate a particular output medium !)
I want to control output features.

Am I missing something ?


Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Fwd: RE: [xep-support] ANNOUNCEMENT - RenderX moves to the Cloud

[Stefan Seefeld]

On 06/25/2012 11:12 AM, Jirka Kosek wrote:
 On 24.6.2012 19:54, Stefan Seefeld wrote:

 OK, thanks for the info. I'm happy to adjust the build rules to get this
 working. So far I couldn't find any instructions on how this is done,
 though. Do I need to process the original .fo file to substitute the
 MathML by SVG, before I pass it along to the FO processor ?

 Yes, exactly. Also, sometimes additional adjustment in FO are necessary,
 there is XSLT provided in SVGMath distribution for it. Basically you
 will need workflow similar to:

 saxon -o x.fo doc.xml fo.xsl
 python c:\SVGMath-0.3.3\math2svg.py -c c:\SVGMath-0.3.3\svgmath.xml -o
 y.fo x.fo
 saxon -o z.fo y.fo c:\SVGMath-0.3.3\fo\adjustbase.xsl
 xep -quiet -fo z.fo -pdf doc.pdf

OK, thanks.



 Also, what are the issues that makes the MML-SVG-PDF only
 acceptable, as opposed to good ? Does this affect all equations, or
 just specific expressions ?

 Well, if one gets used to TeX in teenage then it is very hard to give
 good rank to any other math typesetting system. :-)

Hah, thanks. That gives me a good idea indeed of what reference is used
for acceptable. :-)

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] DocBook Slides 5.0 alpha1 available for testing

[Stefan Seefeld]

On 06/23/2012 03:18 AM, justus-b...@piater.name wrote:
 Hi Gabor,

 Gabor Kovesdan ga...@kovesdan.org wrote on Sat, 23 Jun 2012 08:21:14
 +0200:

 I have no idea how to calculate what will fit on a slide and what
 won't and it also depends on the output format.
 I think this is beyond the scope of DB-Slides.  It is up to the user to
 decide what to put on a slide.

I agree.

 I suspect that consistent content positioning (without using tables)
 between HTML and FO targets will require some thought.  To this end,
 will slide-specific markup be part of your project?
 I imagine you mean that you want to present the content on web and
 provide a printable version with the very same outlook
 No, I don't need strict consistency. But it would be nice to be able to
 use any suitable output formats for presentations (HTML, PDF, ...).  It
 is easy (but cumbersome and abusive) to achieve almost any page layout
 using tables in a target-agnostic way.  But if we want to layout HTML
 using CSS (float style, etc.), then we need DB Slides markup that is
 translated into CSS classes for HTML and into, say, tables for FO
 output.  We have already discussed such markup on this list.

Right. I think we all understand that for slides, the distinction
between content and style is quite different than for other DocBook
content. With slides much of the styling is itself content, so the
vocabulary needs to support that. However, I'd really like to experiment
to find a minimal set of additional markup to support this. Right now we
already have an additional style attribute that could be used to pick
different slide layouts (in both the fo xsl templates as well as the
html CSS). I'd be interested in seeing how far we can get with that,
before having to add more.

I'd also like to see support for multi-column layout in slides, but in
contrast to other places where the text would flow freely into them,
it's quite likely that slide authors want to explicitly position content
into columns.

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] Fwd: RE: [xep-support] ANNOUNCEMENT - RenderX moves to the Cloud

[Stefan Seefeld]

On 06/24/2012 01:13 PM, Ron Catterall wrote:
 Hi Stefan

 At present XEP does not do MML.  (Antenna House will support it - but
 costly)
 I have the Mathflow for Oxygen from dessci.com and put MML code
 directly into Docbook source.  Thjis all works transparently and
 yields reasonable (acceptable) output.  I have aso used the mml2svg
 package that Jirka menioned (http://sourceforge.net/projects/svgmath/
 ) - again output is acceptable, but it means breaking the XML+MML to
 PDF at the FO stage.  Not transparent, but can be automated.

OK, thanks for the info. I'm happy to adjust the build rules to get this
working. So far I couldn't find any instructions on how this is done,
though. Do I need to process the original .fo file to substitute the
MathML by SVG, before I pass it along to the FO processor ?

Also, what are the issues that makes the MML-SVG-PDF only
acceptable, as opposed to good ? Does this affect all equations, or
just specific expressions ?

Many thanks for the help,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Fwd: RE: [xep-support] ANNOUNCEMENT - RenderX moves to the...

[Stefan Seefeld]

On 06/24/2012 03:59 PM, deannel...@aol.com wrote:
 Stefan,
 FYI, I use the FOP/Jeuclid combination to satisfy my XML+MML to
 PDF  needs. That way I can use MML directly or xinclude the equations
 as needed.

Dean,

thanks. I'm having great difficulties with that. As far as I'm aware,
jeuclid doesn't work with fop 1.0. At least I didn't get it working on
Fedora. I filed a bug report over a year ago, and nothing has changed
since (https://bugzilla.redhat.com/show_bug.cgi?id=703896).

The jeuclid / fop combination does work as bundled with xmlmind's xxe,
though.

In any case, this doesn't really satisfy my needs as I also need
fo:float support. (Well, at least I'm trying to implement support for
annotations as fo:float. Perhaps there is another technique that is
supported by fop ?)

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] fo processor features

[Stefan Seefeld]

Hello all,

I'm working with the Object Management Group (http://omg.org/) to
establish the feasibility to support DocBook as a source format for OMG
/ ISO specifications.
It appears DocBook itself is very well suited to write specifications,
however the quality of available FO processors is still rather limited.
Two particular features I'm interested in right now are MathML support
and fo:float (as a way to format annotations).

The two formatters I have immediate access to either don't support
fo:float (apache's fop) or don't support mathml (xep).

Thus I wonder: can anyone recommend a good fo processor with good
coverage as far as support for the above (and other standard-) features
is concerned ? Or even better: is there a publicly available feature
matrix comparing the available solutions ?

Many thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Symbol for indicating that the line actually continues

[Stefan Seefeld]

On 06/08/2012 02:58 PM, Lars Vogel wrote:
 Hello,

 As the program code in my Books is sometimes to long, I have to break
 the line into two. I do this manually and its working fine. 

 I would like to use a special sign to indicate that the line
 continues. I have seen printed documents where a little arrow was used. 

 Does the bookbook standard has a tag for this line continues in the
 next line? If not what is the symbol which is typically used? 

 My output is PDF via FOP.

The fo stylesheets allow to customize that (see
http://docbook.sourceforge.net/release/xsl/1.76.1/doc/fo/hyphenate.verbatim.html).
That document also suggests a couple of  unicode characters to be used,
which may also be useful when doing it manually.

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

[docbook] Re: [docbook-apps] toc customization question

[Stefan Seefeld]

On 06/01/2012 09:18 AM, Tim Arnold wrote:
 Hi Dick,
 Thanks, I have been reading that section, but it's not that I want to
 control the toc on every section, just one section that has a
 particular attribute. My question wasn't clear that I do want section
 tocs, just not for this particular section.

Allow me to jump in with a somewhat related request:

I have run into other situations where I'd like to be able to control
ToC generation explicitly. For example: In DocBook Slides, I'd like to
generate a ToC for each foilgroup (and highlight the current position).
So far I have done this by customizing the appropriate xsl templates.
However, I think it would be very convenient for authors to be able to
explicitly request a toc at a given place, for example using a toc
element, akin to index. (This could be further tuned by adding
attributes to indicate whether this should be a toc for the local
subtree, or a global one.)

Does this sound reasonable ? I will cross-post this to the docbook list,
too, as it is essentially a request for the DB grammar itself.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook] Re: [docbook-apps] toc customization question

[Stefan Seefeld]

Hi Bob,

thanks for the quick follow-up. I don't know why I had overlooked this
so far, as it seems to be (almost) exactly what I'm looking for.
I guess I can get the specific behaviour I need by using the ubiquitous
role attribute and then add specialized templates for that.

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


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

Re: [docbook-apps] toc customization question

[Stefan Seefeld]

On 06/01/2012 09:18 AM, Tim Arnold wrote:
 Hi Dick,
 Thanks, I have been reading that section, but it's not that I want to
 control the toc on every section, just one section that has a
 particular attribute. My question wasn't clear that I do want section
 tocs, just not for this particular section.

Allow me to jump in with a somewhat related request:

I have run into other situations where I'd like to be able to control
ToC generation explicitly. For example: In DocBook Slides, I'd like to
generate a ToC for each foilgroup (and highlight the current position).
So far I have done this by customizing the appropriate xsl templates.
However, I think it would be very convenient for authors to be able to
explicitly request a toc at a given place, for example using a toc
element, akin to index. (This could be further tuned by adding
attributes to indicate whether this should be a toc for the local
subtree, or a global one.)

Does this sound reasonable ? I will cross-post this to the docbook list,
too, as it is essentially a request for the DB grammar itself.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] Re: [docbook] Re: [docbook-apps] toc customization question

[Stefan Seefeld]

Hi Bob,

thanks for the quick follow-up. I don't know why I had overlooked this
so far, as it seems to be (almost) exactly what I'm looking for.
I guess I can get the specific behaviour I need by using the ubiquitous
role attribute and then add specialized templates for that.

Thanks,
Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] generating pdf from DocBook slides

[Stefan Seefeld]

On 05/30/2012 02:32 PM, honyk wrote:
 Hi Justus,
  
 I've tried to utilize Slides DTD for our training courses but quicky
 find the element suite too small and hence limiting me.
  
 Did you use slides or slides-full? The latter contains essentially
 all of DocBook.
 to be honest, your reply was the first place I saw this 'slides-full'
 option. And it looks really promising.

I wasn't aware of this either. However, as we are now working on a
slides grammar on top of DB5, I hope we can soon discuss what the
canonical vocabulary should look like in the RelaxNG age. :-)

 FYI to persuade my colleagues to abandon PowerPoint I had to offer them an
 acceptable replacement. I had previous experience with Oxygen XML wysiwyg
 mode so I used this tool here as well. There was no built-in support for
 DocBook Slides (my request is here
 http://www.oxygenxml.com/forum/topic5128.html ) and as I was in a hurry,
 instead of customizing Oxygen I tweaked the core DocBook.

 If I started now (and had enough time), I'd likely use the opposite
 approach.

FWIW, I'm using xxe from xmlmind (http://www.xmlmind.com/xmleditor/),
and am very happy with it. It comes with Slides (3.4) support built in,
and thus it's easy to get started writing DB-based slides.

I have tweaked the fo stylesheets quite heavily to produce pdf slides in
an acceptable format, and would like to merge those changes (hopefully
improvements) back into mainline as I have time. As you also seem to
have done quite some work on fo stylesheets to produce the slides that
you were referring to in an earlier mail, perhaps you would also be
willing to contribute your work back ?

As part of this year's GSoC project we will mainly focus on HTML-based
presentations, and in particular include S5
(http://meyerweb.com/eric/tools/s5/).

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] generating pdf from DocBook slides

[Stefan Seefeld]

Hello Jan,

thanks a lot for your feedback. That is very valuable.
I hope that we can consider that (as well as other comments about the
slides vocabulary and stylesheets that were sent to this list) as we
work on DB 5 Slides over the next couple of months.

I have just worked on some xsl-fo stylesheets to accommodate my
immediate need, and would certainly like to apply some lessons learned
to this project.

Stefan


-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] generating pdf from DocBook slides

[Stefan Seefeld]

On 05/26/2012 03:20 AM, justus-b...@piater.name wrote:
 Hi Stefan,

 Why not use HTML for presentations?

Only HTML isn't enough. I need to distribute the slides to people who
didn't attend, and there pdf is more convenient.

 I used to provide PDF slides to my students, but have stopped doing that
 in favor of reformatting my slides as a DocBook article using home-brew
 XSLT, with better text flow and additional content.

We are talking about corporate culture here with branding and
pre-defined templates. I will be lucky if I can use anything other than
PowerPoint at all, so I want to deviate from mainstream as little as
possible (or at least only one step at a time).

Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] generating pdf from DocBook slides

[Stefan Seefeld]

Hello,

I'm trying out the generation of pdf (via fo stylesheets) from DocBook
Slides.

The repository contains fo stylesheets specifically for slides, but I
can't find any documentation for how to customize them. Has anyone ever
used them to produce pdf from DB Slides ?

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] generating pdf from DocBook slides

[Stefan Seefeld]

On 05/25/2012 05:56 PM, Gábor Kövesdán wrote:
 On 2012.05.25. 22:58, Stefan Seefeld wrote:
 I'm trying out the generation of pdf (via fo stylesheets) from DocBook
 Slides.

 The repository contains fo stylesheets specifically for slides, but I
 can't find any documentation for how to customize them. Has anyone ever
 used them to produce pdf from DB Slides ?
 You should pick a stylesheet first (in the slides subdir of the
 docbook-xsl distribution). The documentation explains what options you
 have:
 http://docbook.sourceforge.net/release/slides/3.4.0/doc/

 Then use the parameter reference to decide what parameters you want to
 customize:
 http://docbook.sourceforge.net/release/xsl/1.77.0/doc/slides/index.html

Right, I did that. But the only parameters I could find are for choosing
fonts. Typically styling slides also includes setting color schemes,
heading and footer content, background images, etc., so I was hoping
there were already parameters to do that.

It seems there aren't, so I'll just have to do the customization myself.
I may merge that into our GSoC project if it works out. :-)

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


-
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] use of legalnotice

[Stefan Seefeld]

On 05/24/2012 01:40 PM, Bob Stayton wrote:
 I have used preface role=legalnotice for such situations and then
 customized the stylesheet to handle it.  A preface can occur anywhere
 as a child of book, not just at the front.

OK, that appears to be working well.

Thanks,
Stefan

-- 

  ...ich hab' noch einen Koffer in Berlin...


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