Re: [docbook-apps] Thumb register

[Camille Bégnis]

Hello,

I guess this is the colored square you print on the edge of each page of
a chapter, in order to easily select it with the thumb on the book edge?

We've been doing this by adding a fixed block to the header template
(even if it's located outside the header on the page).

HTH,

Camille.

Le 20/07/2020 à 09:40, Norman Tovey-Walsh a écrit :
> Bernhard Kleine  writes:
>> I have used a thumb register in a book produced with LaTeX. That was
>> fairly straight forward. I wonder whether this is also possible with
>> docbook -> PDF. Is there a solution already?
> Pardon my ignorance, but what is a “thumb register”?
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
>> The real art of conversation is not only to say the right thing at the
>> right place but to leave unsaid the wrong thing at the tempting
>> moment.--Dorothy Nevill



signature.asc
Description: OpenPGP digital signature

[docbook-apps] Launching DocBook CCMS Calenco SaaS

[Camille Bégnis]

Good Morning fellow DocBook users,

I am excited to announce the SaaS availability of our DocBook based
Components Content Management System Calenco.

It features:

  * A tag based classification system for all your content
  * Visual representations of dependencies (inclusions and images)
  * Automatic multi-formats publishing
  * Connectors to push outputs on remote servers (FTP, SFTP, email)
  * An impressive Full Web WYSIWYM XML Editor
  * A fully graphical, Drag'nDrop PDF Layout editor
  * Ability to import your own XSL
  * Full integration with a Translation Management System
  * And many more...

It's been in production for years now in dozens of companies in Europe.

We would be delighted to get feedback from the community, you can
register a trial account at:
https://www.calenco.com/en/Rates-Trial-offer.html

Do not hesitate to contact me directly.

Have  nice day,

-- 
French Fab   

NeoDoc
Camille Bégnis
CEO
cami...@calenco.com
Tél: 04.42.52.24.20
http://www.calenco.com/
789, rue de la gare
F-13770 Venelles
 
neodoc

Re: [docbook-apps] DocBook content review process/tools?

[Camille Bégnis]

Hi Peter and all,

We have developed a feature into Calenco (https://www.calenco.com) based
on http://annotatorjs.org/ that allows anyone to comment on a Web
version of the source file. Comments are stored server side.
Then the technical writer have access to the same page with a list of
all comments, who wrote it, etc.
Do not hesitate if you need further information.

Have a nice day,

Camille.

Le 23/10/2018 à 18:53, Peter Desjardins a écrit :
> Hi! Does anyone have a document content review process you can
> recommend? One that allows non-DocBook users to easily provide input
> and see each other's comments?
>
> My team uses Google docs for content review because reviewers can
> comment easily and see each other's input (this is at a company that
> uses Google email/docs). It's error-prone and tedious to transform
> DocBook content to Google documents though. I would love to find a
> better solution.
>
> We keep content in GitHub and I love the pull request content review
> tools there. Most of our subject matter experts do not use GitHub
> though, and it's not practical to review all DocBook content by
> reading the source XML.
>
> The conversion to Google doc format that works the best for us (so
> far) is DocBook > HTML > LibreOffice OpenDocument > Upload to Google
> drive and convert to Google doc format. We lose important formatting
> like bold for guilabel elements and bullet characters for
> itemizedlists disappear. Preparing a document for review is painful.
>
> Do you have a great DocBook-based review process?
>
> Thanks!
>
> Peter
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>

-
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: XML databases

[Camille Bégnis]

Hi all,

thanks for this interesting discussion, what DB would you use or suggest
for XML?

Camille.


Le 06/04/2018 à 11:43, Norman Walsh a écrit :
> Dave Pawson  writes:
>> Agree with your logic. Good for thousands (hard to index)
>> Less so for hundreds (I use db indexing)
> Yes, but as I said, it depends on the app you’re trying to build.
>
> drinks.nwalsh.com: ~200 small documents, easy to build in a DB, harder 
> outside.
> so.nwalsh.com: ~600 documents and growing, easy to build in a DB, *much* 
> harder outside
> photos.nwalsh.com: ~14,000 documents, same story
> tzinfo.nwalsh.com: ~225,000 documents, probably not practical any other way
>
> (Drinks.nwalsh.com is a simple app, you could do that off the
> filesystem with a little bit of Python and some cleverness.
> So.nwalsh.com would be much harder because it’s using full-text,
> semantic, and geospatial indexes and runs queries in real time that
> rely on those indexes to perform well.)
>
>> I'd hate to have the data in a corrupt database
> Or a corrupt filesystem. I don’t think databases are inherently a
> riskier place to put your data. And if having them in a database
> encourages you to have a more reliably backup strategy, they’re
> arguably less risky.
>
> Backup early. Backup often. And remember: if you copy data to a backup
> drive, then remove the data from your computer, you don’t have a
> backup, you have a vulnerable data set on a single external drive.
>
> Be seeing you,
>   norm
>


-
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] Pure JS WebHelp

[Camille Bégnis]

Hi Jan and all,

that looks really nice and more modern than what we have recently, and
should be more flexible too from what I read.

Hope to see it soon on github.

Cheers,

Camille

Le 16/04/2017 à 16:46, Jan Tosovsky a écrit :
> Dear All,
>
> as promised, I've published a demo output
> https://www.bilyujezd.cz/beta/strucna-historie.html
>
> Core changes against the current WebHelp:
> - responsive design (Mobile First)
> - breadcrumb 
> - improved ToC processing (ToC is linked, not embedded in every HTML file)
> - enhanced search related code (cleaning up the code for better maintenance)
> - enhanced translation support (all messages are stored in standard l10n XML
> files)
> - storing client state even on file system or localhost (utilizing HTML5
> Local Storage)
> - removing jQuery and jQueryUI dependency
>
> Further features:
> - ability to enlarge downsized images (aka lightbox, especially useful for
> SVG images)
> - ability to copy links to specific anchors
> - SASS styling (interpreted into CSS)
>
> Weaknesses:
> - only modern browsers are supported (Chrome, FF, Edge, IE10+)
> - no custom params to override current bahavior
> - no out-of-the-box scripts for copying dependencies to the target
> destination
>
>
> Should I put related XSL files and resources to my GitHub account or
> directly to some DocBook sandbox?
>
> Thanks,
>
> Jan
>
>
> -
> 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] WebHelp search - anybody working on improving?

[Camille Bégnis]

We've been facing the issue too, and any tip will be appreciated.

The issue is that people are used to Google Search, and doing that on
the client side is not easy ;-)

Cheers,

NeoDoc
Camille Bégnis
Gérant
cami...@neodoc.fr
Tél: 04.42.52.24.20
http://www.neodoc.fr/
789, rue de la gare
F-13770 Venelles

Le 10/11/2016 à 13:02, Janice Manwiller a écrit :
> I use DocBook source with the docbkx Maven plugin to generate PDFs,
> WebHelp, and some HTML.
>
> The WebHelp search is a source of frustration, mostly because it does
> not support phrase searches. So if you search for "source connectors",
> it looks for topics that have either the word source or the word
> connectors. While topics that contain both words do bubble to the top,
> the search does not specifically look for the phrase "source
> connectors", where both words are together in that order.
>
> Has there been any effort to improve the search? Has anyone else
> implemented a custom search that supports phrase searches?
>
> Thanks,
>
> Janice
>
> -- 
> Janice Manwiller
> Principal Technical Writer
> Sqrrl Data, Inc.
> www.sqrrl.com <http://www.sqrrl.com> | @SqrrlData

Re: [docbook-apps] Automatically detecting which PDFs are affected by changes in a DocBook Git commit

[Camille Bégnis]

Hello,

we have implemented in the Calenco CMS a method based on the IF FOP
intermediary XML Format, which is an XML description of each resulting
page. It is based on the following simple algorithm:

1. Generate the original document IF XML
2. Generate the IF XML based on new sources
3. Compare with an XSLT the 2 IF documents to extract whatever
information we need

We have been using this successfully in production to generate PDF with
only the modified pages between 2 different versions of a document.

HTH,


NeoDoc
NeoDoc
Camille Bégnis
Gérant
cami...@neodoc.fr
Tél: 04.42.52.24.20
http://www.neodoc.fr/
789, rue de la gare
F-13770 Venelles
qrcode
Le 01/11/2016 à 15:42, Bergfrid Skaara a écrit :
> I´d like to know the overall difference between versions X and Y of a
> single PDF - automatically so we don't need to inspect and compare
> page by page manually (simplifying release process).
>
> I need to know all PDFs (and what content within them) that have
> changed as a result of commits X,Y, Z (simplifying review and release
> process).
>
> I´d like notifications if a commit targeted only at feature A ends up
> changing PDFs unrelated to feature A. This would typically indicate
> profiling errors or misplaced includes that need to be fixed.
>
> Inserting build numbers or some similar ID from the CI environment
> into the PDF metadata would also help.
>
> The challenge with comparing PDFs is all the noice you get from layout
> changes (white space) and info in headers and footers such as dates
> and version numbers.
>
> And if you go the convert-PDFto-text-before compare route, would it
> not be better to compare the intermediate FO files rather than waste
> time going through the entire publishing pipeline first?
>
> We are not looking to replace our current CI environment. Extending
> the current build-logic is not a problem, but I´m not sure what the
> new logic should look like.
>
> Bergfrid Skaara Dias
>
> On Wed, Oct 26, 2016 at 6:48 PM, Stefan Seefeld <ste...@seefeld.name
> <mailto:ste...@seefeld.name>> wrote:
>
> 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
> <mailto:docbook-apps-unsubscr...@lists.oasis-open.org>
> For additional commands, e-mail:
> docbook-apps-h...@lists.oasis-open.org
> <mailto:docbook-apps-h...@lists.oasis-open.org>
>
>

Re: [docbook-apps] Visual DocBook editors

[Camille Bégnis]

Hello,

our CCMS Calenco actually uses XMLMind's XXE as an editor. We actively
support DocBook, and are scheduling support for DocBook 5.1.

Best regards,

*NeoDoc*
*Camille Bégnis*
cami...@neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/

Le 23/05/2015 23:33, Jan Tosovsky a écrit :
 Hi Nils,

 wow, what a nice list of projects!

 On 2015-05-23 Nils Cordes wrote:
 On 2015-05-23 Jan Tosowsky wrote:
 Have I overlooked any handy tool or service?
 NeoDoc Calenco

 http://www.neodoc.biz/en/calenco/index.html
 http://sourceforge.net/projects/calenco/
 I can see just marketing on their site, not a live demo or even screenshot of 
 their content editor. DocBook is not mentioned anywhere...

 Has anybody any experience with this system?

 Doctored.js
 http://holloway.co.nz/doctored/
 https://github.com/holloway/doctored
 While not a real WYSIWYG this one looks cool. But understaffed (maintained by 
 a single person... no recent updates...). Some operations seem to be 
 overcomplicated (how do I delete a tag without switching into source XML?).

  
 JBoss Tools Visual Editor
 http://tools.jboss.org/
 https://github.com/jbosstools/jbosstools-
 vpe/tree/master/plugins/org.jbo
 ss.tools.vpe.docbook
 Is there any screencast to demostrate how it works?


 DEP4E
 http://dep4e.sourceforge.net/
 http://sourceforge.net/projects/dep4e/
 In the quick start guide there is only raw XML editing mentioned, not WYSIWYG.

 Regards,
 Jan



 -
 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 - docx

[Camille Bégnis]

Hello,

I advise the XSL-FO converter from XMLMind:
http://www.xmlmind.com/foconverter/
It's reasonably priced and does a very good job.

However one limitation is that the output is made out of XSL-FO so all
the structure information is lost (basically the Word output does not
use styles)

HTH,

*NeoDoc*
*Camille Bégnis*
cami...@neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/
Le 23/01/2015 16:03, David Goss a écrit :
 There is also the roundtrip stylesheets in the Docbook XSL
 distribution. These require that you use a subset of docbook elements.

 http://www.sagehill.net/docbookxsl/MSWord.html

 I haven't personally tried the roundtrip stuff. Whenever a
 non-technical person has asked for an editable version of a docbook
 file, I usually just copy/paste the HTML into Word, and explain the
 caveat that they should just ignore the formatting.

 **

 --
 *David Goss*, Technical Writer
 Frontier Science | www.fstrf.org
 4033 Maple Rd, Amherst, NY 14226
 (716) 834-0900 extension 7204

 
 *From: *Peter Lavin lavin.pe...@gmail.com
 *To: *Fredrik Unger f...@tree.se
 *Cc: *docbook-apps docbook-apps@lists.oasis-open.org
 *Sent: *Friday, January 23, 2015 9:03:12 AM
 *Subject: *Re: [docbook-apps] docbook - docx

 Hi Fredrik,
 pandoc does a decent job of converting DocBook to .docx.

 See:

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

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

 Peter

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

 Hi,

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

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

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

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

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

 Are there any better alternatives to this approach ?


 Thanks,

 Fredrik Unger

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

[docbook-apps] Fop failing with illicit table

[Camille Bégnis]

Hello,

I am facing the infamous error:
A table-cell is spanning more rows than available in its parent element.
When trying to convert DocBook to PDF using FOP.
It is a big document with many tables, and looking for the culprit is
tedious.

Has anyone faced this issue, and found a way to detect the issue?
A simple XPath would do I guess?

Cheers,

-- 
*NeoDoc*
*Camille Bégnis*
cami...@neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/

[docbook-apps] DocBook 5 samples for tests

[Camille Bégnis]

Hello,

there is an extensive set of samples in DB4, but I cannot find a DB5 
version, does it exist?


I'm looking for it to stress test our Calenco CMS (http://www.calenco.com)

Thanks for your help,

--
*NeoDoc*
*Camille Bégnis*
cami...@neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/

[docbook-apps] Link from part of SVG

[Camille Bégnis]

Hello,

I want to create a clickable SVG with various zones inside the SVG that
point to different chapters in my document.
I have managed to create an HTML link from within a SVG, by adding the
element

a xlink:href=chap3 
view-source:file:///home/camille/Bureau/tmp/images/chap3

so when I add that SVG inside a DocBook document, and transform it to
HTML, that zone of the SVG points to the chapter with xml:id chap3.
So far so good.

I haven't found the required code to be added to the SVG so that the
same behavior is achieved in the PDF (made with fop) output.

Any idea?

Have a nice day,

-- 
*NeoDoc*
*Camille Bégnis*
cami...@neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/

Re: [docbook-apps] Profiling on table columns

[Camille Bégnis]

Thanks Jirka, David,

I'll try to make a simple table data structure indeed, and a short
customization for this specific usecase.

Best regards,

--
NeoDoc
Camille Bégnis

On 13/12/2012 18:32, David Cramer wrote:
 On 12/13/2012 10:26 AM, Jirka Kosek wrote:
  So in some cases it can be quite straightforward, in some cases it
  would be very difficult.

 Another difficulty is that you might also need/want to adjust column
 widths.

 Another approach would be to store the content in a custom semantic
 format suited to the data and transform it into a CALS or HTML table
 as a preprocessing step as part of the build, then xinclude the table
 into your doc. The preprocessing step could include/exclude data based
 on profiling inputs. The custom format might be easier to understand
 and edit than a CALS or HTML table as well.

 David

[docbook-apps] Profiling on table columns

[Camille Bégnis]

  
  
Hello all,

I didn't find anything relevant about this topic, but I am facing
this very same problem. A table from which I need to filter out
columns...
Did anyone solve this?
I thought the profiling attribute could be set on the colspec, and
then removing the corresponding entries shouldn't be that hard, but
dealing with spans might be a cause of major headaches.

Anyone already tried?

Have a nice day,

-- 
  
  
Camille Bgnis
Grant
cami...@neodoc.fr
Tl: +33(0)9.54.96.99.55 - Fax:
  +33(0)9.59.96.99.55
http://www.neodoc.fr/
 5, rue de la Touloubre
  13770 Venelles
  France 
  

  

Re: [docbook-apps] Upgrading from DocBook 4.5

[Camille Bégnis]

  
  
Hello,

you should find all needed info here: http://docbook.org/docs/howto/
As for 5.1 it's not published yet, so moving to 5.0 should be a good
first step.


  
  
Camille Bgnis
Grant
cami...@neodoc.fr
Tl: 09.54.96.99.55 - Fax: 09.59.96.99.55
http://www.neodoc.fr/
 5, rue de la Touloubre
  13770 Venelles 
  


On 03/02/2012 20:17, Jeff Powanda wrote:

  
  
  
  
  

I'm considering upgrading my DocBook 4.5
toolchain and had some basic question before I start:

- Where's the best guide on how to convert
DocBook 4.5 XML files to DocBook 5.x? Is the Transition
Guide (http://www.docbook.org/docs/howto/)
the best place
to start? Are there other guides?
- Where should I go to download the RelaxNG
schema?
- Where should I go to download the latest
DocBook XSL stylesheets for DocBook 5.x? Should I go here: http://sourceforge.net/projects/docbook/files/docbook-xsl-ns/
- What tools for validation are there
available for DocBook 5.x?
- Are there any gotchas I should be aware
of?
- Is there any reason I shouldn't move to
DocBook 5.1 (rather than DocBook 5.0)?

Regards,
Jeff Powanda
Vocera Communications, Inc.

  

  

Re: [docbook-apps] Content Management solutions that support DocBook 5.x?

[Camille Bégnis]

  
  
Hello,

I have revived and updated the corresponding wiki page:
http://wiki.docbook.org/ContentManagementTools
If any of you know of other CMS supporting DocBook, please add them!
I'm sure there are many more.

Disclaimer: I am heading the company that develops Calenco.

Best regards,


  
  
Camille Bgnis
Grant
cami...@neodoc.fr
Tl: 09.54.96.99.55 - Fax: 09.59.96.99.55
http://www.neodoc.fr/
 5, rue de la Touloubre
  13770 Venelles 
  


On 03/02/2012 22:29, Jeff Powanda wrote:

  
  
  
  
  

I'm looking for a content management
solution that supports DocBook. I would consider both
commercial and open source solutions. I would appreciate any
recommendations, warnings, or tips that anyone has to offer.

I'm also considering upgrading from DocBook
4.5 to DocBook 5.x, so would be interested to hear of CM
solutions that support DocBook 5.x.

Regards,
Jeff Powanda
Vocera Communications, Inc.

  

  

Re: [docbook-apps] Customizing and creating a stylesheet for docbook using the XML Mind or Oxygen XML Editor

[Camille Bégnis]

  
  
Hi Daniel,

the reference book for DocBook XSL customization is "DocBook XSL:
The Complete Guide" http://www.sagehill.net/docbookxsl/

You should find there all you need and more.

HTH


  
  
Camille Bgnis
Grant
cami...@neodoc.fr
Tl: 09.54.96.99.55 - Fax: 09.59.96.99.55
http://www.neodoc.fr/
 5, rue de la Touloubre
  13770 Venelles 
  


On 17/01/2012 09:43, daniel.ke...@finaris.de wrote:
Hello,
  
  
  currently my company is thinking about transferring
its
user documentation into XML and docbook.
  
  Since we are an IT company, XML and programming in
general
is not a problem. But: We cannot find and adjust the stylesheet
needed
to create our custom documentation.
  
  We are currently setting up a prototype for our
documentation,
following the instructions from Walshs "DocBook 5: The
definitive
Guide" and working with the XML Mind Editor and a trial version
of
"OXYGEN Editor".
  
  
  Basically, we are satisfied with the results and
trust
in docbooks function (since having lots of trouble with Word),
but the
lacking transparency makes
it really hard to come up with a sample documentation/ prototype
.Each
file we open has at least one reference to a website we cannot
open and
dozens of files that dont exist or are really hard to find. We
checked
the regular docbook.zip from the docbook homepage, but also all
files
of the respective editors. (Is there something as a "default"
Docbook editor that you would propose?)
  
  
  Can anyone give me some advice, a link or even a
how-to
for adjusting the docbook stylesheet? Personally, I would love
to use docbook
for our user documentation, simply for the additional features
it has compared
to other text processing program, but only if I can adjust the
appearance.
Especially regarding corporate identity this is absolutely
necessary.
  
  
  Thanks and with best regards,
  
  
  
  D. Keyes
  
  

===
Disclaimer
The information contained in this e - mail and any attachments
( together the "message") is intended for the addressee only
and may 
contain confidential and/or privileged information. If you have
received
the message by mistake please delete it and notify the sender
and do
not copy or distribute it or disclose its contents to anyone.

FINARIS Financial Software Partner GmbH
Smmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bchle, Dipl. Inf.
Werner Mrkl
===

  

Re: [docbook-apps] how put narrow non-breaking spaces before punctuation marks

[Camille Bégnis]

Hello,

I don't know if oXygen provides a shortcut, but in DocBook 5 you have to
insert the unicode character for non breaking space, that is #160; in
the XML code.

HTH,

Camille.

On 10/11/2011 16:25, D-BookeR wrote:
 Hi,

 I am using docbook 5 for publication in French, so I need to place the
 usual narrow non-breaking space before strong punctuation like colon,
 semi colon, exclamation and question marks.
 How to proceed ?
 Should I introduce them from the start, in the docbook manuscript ?
 Then how? 
 Or can we do it automatically with the xslt ? Is there any parameter
 for that ?

 [I am editing with Oxygen]

 Thanks for your help,
 Patricia

-
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 put narrow non-breaking spaces before punctuation marks

[Camille Bégnis]

This is just a character in the XML stream, so DocBook is not the culprit.
It's rather an issue in the processing toolchain, or the glyph missing
in the font used to render this character...

Camille.

On 10/11/2011 18:16, D-BookeR wrote:
 Thanks!
 Do you know whether I can get a narrower one ?
 The *narrow* non-breaking space
 (http://www.fileformat.info/info/unicode/char/202f/index.htm) seems
 not to work with docbook5.

 patricia

 2011/11/10 Camille Bégnis cami...@neodoc.biz mailto:cami...@neodoc.biz

 Hello,

 I don't know if oXygen provides a shortcut, but in DocBook 5 you
 have to
 insert the unicode character for non breaking space, that is #160; in
 the XML code.

 HTH,

 Camille.

 On 10/11/2011 16:25, D-BookeR wrote:
  Hi,
 
  I am using docbook 5 for publication in French, so I need to
 place the
  usual narrow non-breaking space before strong punctuation like
 colon,
  semi colon, exclamation and question marks.
  How to proceed ?
  Should I introduce them from the start, in the docbook manuscript ?
  Then how?
  Or can we do it automatically with the xslt ? Is there any parameter
  for that ?
 
  [I am editing with Oxygen]
 
  Thanks for your help,
  Patricia

Re: [docbook-apps] CMS recomendations

[Camille Bégnis]

  
  
Hello,

we at NeoDoc have been developing an XML CMS since 2009, with tight
integration with DocBook (dependencies management, output
processing, etc.)
You can get more details here:
http://www.neodoc.biz/static/en/section-calenco.html

I will happily study your requirements if you have already written
some specifications.

Best regards,


  
  
Camille Bgnis
Grant
cami...@neodoc.fr
Tl: 09.54.96.99.55 - Fax: 09.59.96.99.55
http://www.neodoc.fr/
 5, rue de la Touloubre
  13770 Venelles 
  


On 19/09/2011 12:55, Eric Johnson wrote:

  My company is considering moving to a CMS. Are there any
recommendations for a CMS that supports DocBook? I'd really rather not
be forced into migrating our content to a different XML format just to
use a CMS.

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


  

attachment: camille.vcf
-
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] CHM Index Problem

[Camille Bégnis]

Hi Sam,

I have been unable to get an index using the help compiler under wine
either.
Let us know,

Camille.

On 07/09/2010 07:01, Sam Fischmann wrote:
 Thanks for the suggestion. Unfortunately, that's what I've been doing
 (if htmlhelp.use.hhk is off, I get no index at all). Given the same
 project produced by the stylesheets, in windows, the entries in the
 .hhk file are sorted by the help compiler and grouped together. Under
 WINE, they simply appear in the index in the same exact order as they
 do in the .hhk file, duplicates and all. It's kind of interesting that
 a very specific part of the process is broken but I figure it's at
 least some kind of hint as to what I need to configure in WINE.

 -Sam

 On Mon, Sep 6, 2010 at 6:04 PM, Cramer, David W (David)
 dcra...@motive.com mailto:dcra...@motive.com wrote:

 Hi Sam,

 Maybe try building it using an hhk file instead of the activex goo
 put in place of each indexterm by default. See:

  

 
 http://docbook.sourceforge.net/release/xsl/current/doc/html/htmlhelp.use.hhk.html

  

 and

  

 http://www.sagehill.net/docbookxsl/HtmlHelp.html#HHGenIndex

  

 David

  

 *From:* Sam Fischmann [mailto:sam.fischm...@gmail.com
 mailto:sam.fischm...@gmail.com]
 *Sent:* Monday, September 06, 2010 7:18 PM
 *To:* docbook-apps@lists.oasis-open.org
 mailto:docbook-apps@lists.oasis-open.org
 *Subject:* [docbook-apps] CHM Index Problem

  

 Hello,

  

 Due to some specific requirements, I need to compile CHM files
 from the htmlhelp stylesheets under WINE in Linux. While my
 project compiles without errors under both windows and linux, the
 final .chm index compiled in linux is unsorted and the index
 entries are not consolidated. Everything else appears normal. I
 realize this has nothing to do with the stylesheets directly, but
 I figure there's some slim chance somebody here has encountered
 this problem so I thought I'd ask if anybody has any insight. I'm
 already using native versions of itss.dll, itircl.dll, and
 hhctrl.ocx to no avail.

  

 Thanks,

  

 -Sam


attachment: camille.vcf-
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 and InDesign

[Camille Bégnis]

Hello,

I have a client that wishes to be able to fine tune the PDF rendering
with InDesign, of content written in DocBook.
Have someone already done that? Is it realistic? Costly?

Any feedback appreciated.

Thanks,

Camille;
attachment: camille.vcf-
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 and InDesign

[Camille Bégnis]

Hi all,

thanks for your feedback!
I have created a page on Wiki to gather content:
http://wiki.docbook.org/topic/DocBookInDesign

I have shamelessly reused content from your posts, please do check it is
still relevant out of context. I think this is a good starting point,
can someone add links to the ICML/IDML specifications?

Camille.

On 15/06/2010 15:18, Giuseppe Bonelli wrote:
 Hi Keith,
 thanks for the pointer to the ickmull projects. It is definitely worth
 looking at it.

 Based on your experience , can you please briefly elaborate on the
 main problems you may anticipate in developing a DB-ICML roundtrip
 scenario? A roundtrip solution would be very attractive indeed, as it
 would elegantly solve the problems of transferring back to the DB file
 any modification made in inDesign during the fine tuning of the
 typography (trimmed paragraph, change in the body text due to layout
 contraints and the like).

 Thanks,

 __peppo

 2010/6/15 Keith Fahlgren abdela...@gmail.com:
   
 I agree with Jirka's assessment about transforming a subset of DocBook and
 think this would be a relatively straightforward XSLT. I would not try to
 roundtrip.
 

   
 The project is open source and available at (from memory):
 http://code.google.com/p/ickmull/
 
 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
   
attachment: camille.vcf-
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] Rethinking XSLT 2.0 design

[Camille Bégnis]

Hi Norm and all,

My opinion on the subject is that we should try listing the cases (like
/section/info/title) why the first step is required.
And then see if the schema could not be simplified to make that first
step unnecessary.

I have found that this kind of choice is often confusing for the end
user (the writer). Notwithstanding the processing issues. You can very
well decide to process differently /section/info/title and
/section/title while they are theoretically the same thing according
to the schema...

Sorry I don't help you much for your current problem :-)

Camille.

On 27/05/2010 13:59, Norman Walsh wrote:
 Hi folks,

 I'm going to be turning my hands to the XSLT 2.0 stylesheets for
 DocBook again soon, partly with an eye towards making them more
 production ready, partly to try a few experiments.

 When I set out on the XSLT 2.0 reimplementation, I had in mind a
 design where there'd be a normalization phase that does some cleanup
 followed by a processing phase that does the actual work.

 For example, normalization turns

   sectiontitlefoo/title...

 into

   sectioninfotitlefoo/title/info...

 so that subsequent processing can know that the title is
 section/info/title.

 After several years of experience, I've come to the conclusion that
 that was a mostly bad idea.

 1. It's very expensive. The entire document gets processed at least
 twice. While the idea of simplifying the downstream design seemed
 very attractive, I think the cost is too high.

 2. It doesn't actually simplify things. Oh, in theory it does, but in
 practice, it's harder to debug because the document you're looking at
 isn't actually the one being styled.

 3. That problem extends to the actual users as well, if something goes
 wrong, the error messages don't reflect the document that the user
 actually sent to the stylesheets.

 4. I made a DB4 to DB5 conversion phase part of that normalization,
 and that makes the problems even worse (three phases, an even broader
 disconnect).

 So my initial plan is to look at breaking things down so that the
 processing is more direct. I'll probably keep the normalization phases
 around as separate stylesheets.

 I reserve the right to change my mind again when I get underway :-)

 Comments most welcome.

 Be seeing you,
   norm

   
attachment: camille.vcf-
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] Testers wanted for Calenco V2

[Camille Bégnis]

Hi all,

after one year of intensive coding, I am glad to announce the
availability of Calenco V2 RC1.
Calenco is a Web based XML CCMS, with built-in support for DocBook V5.
It allows you to:
- Store and modify files (XML and images notably) through a WebDAV
interface.
- Show the tree of dependencies (XIncludes and images)
- Store your XSL customization layers
- Setup publications (PDF, HTML, RTF, PS, CHM) that are automatically
rebuilt when content changes

BTW this is Free Software, you can get it
at https://sourceforge.net/projects/calenco/

There is also an online demonstration server available here:
http://trac.calenco.com/wiki/CalencoV2Demo
featuring a preliminary WYSIWYG editor.

Looking forward for your feedback,

Camille.
attachment: camille.vcf-
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] Migration from text processing to DocBook

[Camille Bégnis]

Hello all,

I've written a short article about how to take best advantage of
OpenOffice.org DocBook export to transform Word or OOo documents to DocBook.
I would appreciate your feedback and experience so this can be further
enhanced and later included in the DocBook wiki.

http://blog.neodoc.net/2010/02/migrate-text-processing-document-do.html

Thanks,

Camille.
attachment: camille.vcf-
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: [docbook] DocBook and Google Summer of Code ?

[Camille Bégnis]

Hello,

I have always dreamed of a graphical application that would allow
someone without a CS degree to customize the XSL-FO stylesheets.
A first version would concentrate on customizing specific parts of the
stylesheet, like:
- standard customization parameters, clearly organized, with choice or
value validation
- personalization of attribute sets, proposing a reduced set of
parameters available in XSL-FO
- customization of specific zones like title pages, headers, footers

All this should be very flexible: aka it must be easy for a programmer
to propose new parameters (for example the logo filename to appear on
the title page) to be added  to the interface. So I thought maybe the
extra information needed to build the interface could be coded in the
XSL itself... To be discussed.

Anyone interested in that?

Camille.

master pages,
David Cramer wrote:
 I believe the DocBook wiki is broken at the moment, but yes, having a
 list somewhere to start from would be useful.

 My vote would be for a WebHelp output with toc, search, and index tabs
 in the nav pane. It would be like
 http://www.thingbag.net/docbook/docbook-webhelp/index.html but better:
 the toc pane would synchronize with the content (or perhaps it wouldn't
 be use frames at all, but be more like website's nav mechansim), the
 search would ideally be more i18nized, etc., and it would be part of the
 DocBook XSL distribution. 

 David 

   
 -Original Message-
 From: Stefan Seefeld [mailto:seef...@sympatico.ca] 
 Sent: Tuesday, January 26, 2010 6:48 PM
 To: docb...@lists.oasis-open.org; DocBook Apps Mailing List
 Subject: [docbook-apps] Re: [docbook] DocBook and Google 
 Summer of Code ?

 Mid-december I sent a mail to this list, suggesting that 
 DocBook applies to participate in Google's Summer of Code program.
 A couple of people followed up with interest and ideas, so 
 I'd like to send out a little note with some details.
 Google just sent out this: 
 http://groups.google.com/group/google-summer-of-code-discuss/b
 
 rowse_thread/thread/d839c0b02ac15b3f?pli=1
   
 The most important bit is this:

 We will begin accepting application from would-be mentoring 
 organizations beginning March 8th at approximately 19:00 UTC, 
 with applications closing on March 12th at 23:00 UTC. 

 I would like to suggest that, as a start, we collect project 
 ideas on the wiki. (I was going to do that, then realized 
 that the pages I looked at where marked immutable. May be I'm 
 just lacking enough karma to edit them. Can someone help ? A 
 new GSoCIdeas page would be a good start !)

 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


 

 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
   
attachment: camille.vcf-
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] Editing the DocBook wiki

[Camille Bégnis]

Hi all,

the wiki looks to have been locked, all pages are marked Immutable
Page so I cannot add RuedigerLandmann nor modify any page on wiki even
though I'm logged in.

Any idea? Norm?

Camille.

Ruediger Landmann wrote:
 Hi --

 Sorry if this request is in an odd place; the timezone I'm in makes it
 difficult for me to catch people in IRC

 Could someone please add me to the UserGroup page of the DocBook wiki?
 My username is RuedigerLandmann

 I'd like to update the WhoUsesDocBook page to include Red Hat's
 documentation team, correct the link to the Fedora docs team, and then
 update the DocBookPublishingTools page to include Publican, the tool
 that we use to work the magic in :)

 Cheers

 Ruediger


 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
attachment: camille.vcf-
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] should xml:id be inside TITLE or SECT1?

[Camille Bégnis]

Hi,

semantically speaking, I guess that when you want to reference an item,
you mean to point to the section, and not the title of it. Because if
you use

title xml:id=wifiWi Fi Networking/title

you tell the processors that the ID applies only to the title, not the
section. And actually the way xref elements are processed expects that
the ID is on the structural element (chapter, section, figure, etc.).
So the correct syntax is

sect1 xml:id=wifi

just test :-)

Camille.

Robert Nagle wrote:
 I am creating a book mainly for PDF rendering but also for
 ebook/chunked html output.

 I'll be including cross-references throughout; I don't expect to do a
 lot of fancy customizations.

 Is there a preferred method for when to use xml:id?

 sect1 xml:id=wifi
 title /title
 para../sect1

 OR

 sect1
 title xml:id=wifiWi Fi Networking/title
 para /para /sect1

 Does it make a difference? Are there advantages to putting it in the
 title rather rather than the sect1 element? Opinions?  Thanks...

 rj
   
attachment: camille.vcf-
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] Page shrinking or scaling

[Camille Bégnis]

Hi,

font size is static by default. But you could actually make the value
dynamic by assigning its value depending on the paper.type parameter for
example.

xsl:param name=body.font.master
  xsl:choose
xsl:when test=$paper.type=A510pt/xsl:when
xsl:when test=$paper.type=A314pt/xsl:when
xsl:otherwise12pt/xsl:otherwise
  /xsl:choose
/xsl:param

(untested)

Concerning images, you can either:
- make the size relative (e.g. width=80%)
- recalculate the size at transformation time by extracting it in the
image handling template and making it a fraction of the static size
depending on the paper size change... (might be more difficult).

Good luck,

Camille.

deannel...@aol.com wrote:
 Hi y'all,
  
 Is there a way to shrink the page size in Docbook without having to
 reformat the doc going to PDF (FOP).
  
 My users would like to have a half size manual to travel with
 instead of a regular US Letter size page. I guess I could to this at
 the printers, but it would be nice if I could do it at the office.
  
 I tried adjusting the page.height and .width but that just messed
 things up because the fonts were still the same size as were the images.
  
 Any ideas?
  
 Regards,
 Dean Nelson
attachment: camille.vcf-
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 set up profiling in customization layer?

[Camille Bégnis]

Ah well, could you provide a minimal (XML+XSL) sample (on
http://docbook.pastebin.ca/ for example) that shows the issue?

Camille.

Bergfrid Skaara wrote:
 ofcourse... I should have thought of that. But no, adding inner quotes
 did not do any difference
  
 Best Regards,
 Bergfrid Skaara

 On Tue, Sep 29, 2009 at 2:01 PM, Camille Bégnis cami...@neodoc.biz
 mailto:cami...@neodoc.biz wrote:

 Hello,

 xsl:param name=profile.audience select=None/

 Will try to select a None element. Try this instead:

 xsl:param name=profile.audience select='None'/

 With the word 'None' into simple quotes so it's taken as a
 string I
 was caught a number of times on this :-)

 Camille.

 Bergfrid Skaara wrote:
  Hi,
  I'm trying to introduce profiling to the following scenario, so far
  without success:
 
  DocBook 5, modular with xincludes and olinks. Have unique xml:id and
  profiling attributes set
  XSL customization layer which imports fo/profile-docbook.xsl
  oxygen XML Editor 10.3 with saxon6.5.5 and FOP0.95 stylesheets
 1.75.1
 
  problem:
  I have section audience=All... and add xsl:param
  name=profile.audience select=None/xsl:param to my cust.layer
  and the generated PDF is not filtered (everything is included). Both
  validation and transformation are successfull and
  fo/profile-docbook.xsl is read at processing. It seems like the
  profile param is ignored.
 
  I believe I've followed the instructions in the book to the letter,
  but clearly I must be missing something. Suggestions?
 
  Best regards,
  Bergfrid Skaara


attachment: camille.vcf-
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 set up profiling in customization layer?

[Camille Bégnis]

Hello,

xsl:param name=profile.audience select=None/

Will try to select a None element. Try this instead:

xsl:param name=profile.audience select='None'/

With the word 'None' into simple quotes so it's taken as a string I
was caught a number of times on this :-)

Camille.

Bergfrid Skaara wrote:
 Hi,
 I'm trying to introduce profiling to the following scenario, so far
 without success:
  
 DocBook 5, modular with xincludes and olinks. Have unique xml:id and
 profiling attributes set
 XSL customization layer which imports fo/profile-docbook.xsl
 oxygen XML Editor 10.3 with saxon6.5.5 and FOP0.95 stylesheets 1.75.1
  
 problem:
 I have section audience=All... and add xsl:param
 name=profile.audience select=None/xsl:param to my cust.layer
 and the generated PDF is not filtered (everything is included). Both
 validation and transformation are successfull and
 fo/profile-docbook.xsl is read at processing. It seems like the
 profile param is ignored.
  
 I believe I've followed the instructions in the book to the letter,
 but clearly I must be missing something. Suggestions?
  
 Best regards,
 Bergfrid Skaara
attachment: camille.vcf-
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 prevent one word from being split into two lines

[Camille Bégnis]

Hi,

what I found in those cases is to use the zero width no break space
U+FEFF between characters.

aka:

C#xFEFF;+#xFEFF;+

Not tested though.

Camille.

Camille.

Baoqiu Cui wrote:
 Hi,

 For PDF output using FOP, is there a way to prevent a word like C++
 from being split into two lines (C is at the end of one line and ++
 is at the start of the next line)?  I have never run into this problem
 until today, and I could not find a solution for this problem anywhere.

 I must be missing something...  Can anyone give me some help?

 Thanks in advance!

 - Baoqiu


 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
   
attachment: camille.vcf-
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: How to prevent one word from being split into two lines

[Camille Bégnis]

Baoqiu Cui wrote:
 Baoqiu Cui cbao...@yahoo.com writes:

   
 Camille Bégnis cami...@neodoc.biz writes:

 
 Hi,

 what I found in those cases is to use the zero width no break space
 U+FEFF between characters.

 aka:

 C#xFEFF;+#xFEFF;+

 Not tested though.
   
 Thanks a lot, Camille!  This works like a charm!
 

 Another thought: unicode character #x2060; (WORD JOINER) could be a
 better character than #xFEFF; for this purpose.  What do you think?
   
I didn't know this one, but tif the rendering is fine, why not?

Camille.
 - Baoqiu

   
 - Baoqiu

 
 Camille.

 Baoqiu Cui wrote:
   
 Hi,

 For PDF output using FOP, is there a way to prevent a word like C++
 from being split into two lines (C is at the end of one line and ++
 is at the start of the next line)?  I have never run into this problem
 until today, and I could not find a solution for this problem anywhere.

 I must be missing something...  Can anyone give me some help?

 Thanks in advance!

 - Baoqiu
 


 -
 To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
 For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
   
attachment: camille.vcf-
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] Easy collaborative authoring and translating using DocBook

[Camille Bégnis]

Hi all,

I had announced a first version here some months ago, we have now built
a more user friendly website and user Interface for the application.

In short Calenco allows to:
- Store modular DocBook 5 files (book, chapter, section, etc.) using
Xinclude, and images, on a central repository
- Store translations in specific language directories
- Allow authorized people to browse the repository through a Web browser
and upload/update files
- Store XSL customization layers
- Run a compilation (PDF, HTML, HTML chunked; for now) using standard or
customized XSL, all through the Web interface

You will find more information at: http://www.calenco.com
Calenco is Free Software released under the AGPL license.

If you want to test it live:
* Connect to  http://my.calenco.com:8080/calenco
* login: gu...@calenco.com
* password: invite

Your comments will be much appreciated.

Camille.
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] Always use most specific markup?

[Camille Bégnis]

Lasse Kliemann wrote:
 Should one always use the most specific markup available?

Well, it depends ;-)
The question can be broaden: should one use inline markup at all?

It depends whether you plan to make use of that meta-information or not.
The question should be:
- Do I need to differentiate the rendering of a file name and a command
in the output documents?
- Do I need to be able to scan for all file names used in the document?
- Do others that will further use the document need that information?
- etc.

The risk with DocBook is one can be tempted to markup every word, just
because there is an element that may fit it. It can make writing a pain,
and maintaining the stylesheets too.
The answer to those questions is specific for each of us, IMHO.

If the simplified DocBook project has been unmaintained, I guess this is
because DocBook 5 makes it so easy to create its own simplified DocBook
(see http://norman.walsh.name/2005/11/05/dbtiny).

However the Publishing subcommittee may bring more answers.

Regards,

Camille.

  For 
 example, sometimes it may be conceivable to use 'systemitem' 
 instead of 'filename', 'envar', or 'function'.

 Sometimes, even, there is no more specific markup available than 
 'systemitem'. When I write a document where I am forced to use 
 'systemitem' in many places (since there is nothing more specific 
 available), it might seem unproportional to be so very specific 
 as 'filename', 'envar', etc. in other places, unless it is clear 
 that this specific markup serves a purpose.

 The Simplified Docbook Project looked as if it could offer some 
 guidance concerning such questions, but unfortunately it seems to 
 be no longer maintained. It would in general be good to have more 
 documentation and public discussion on how to use Docbook markup 
 appropriately for different purposes. Maybe we can spur some 
 development in that direction.
   

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] DocBook 5 modules?

[Camille Bégnis]

Hi Bob,

Indeed DocBook suffered a major transformation for 5.0 since it is now
developped as a RNG schema instead of a DTD.
Other versions than RNC/RNG are automatically generated.

For more information: http://www.docbook.org/docs/howto/ and notably
http://www.docbook.org/docs/howto/#cust-attributes

Camille.

DuCharme, Bob wrote:
 I'm a little behind with DocBook, and I can't find module files for it
 such as dbpool.mod and dbhier.mod. (Or maybe I missed some major
 re-engineering step in DocBook's  evolution!)
  
 I downloaded 5.0 from http://www.docbook.org/xml/5.0/ , which seems to
 lead only to one- or two-file versions of DocBook.
 http://www.oasis-open.org/docbook/xml/5.0/ has only one file, and that
 tells me me that 5.0 hasn't been released yet. Are there other places
 to look?
  
 I wanted to add an attribute to a few elements and thought that I'd
 insert it into the appropriate local.whatever.attrib parameter entity
 declaration, but I can't find the declaration anywhere.
  
 thanks,
  
 Bob DuCharme
 Disclaimer:
 ---

 This e-mail and any files transmitted with it are for the sole use of
 the intended recipient(s) and may contain confidential and privileged
 information. If you are not the intended recipient, please contact the
 sender by reply e-mail and destroy all copies of the original message.
 Any unauthorized review, use, disclosure, dissemination, forwarding,
 printing or copying of this e-mail or any action taken in reliance on
 this e-mail is strictly prohibited and may be unlawful.

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] Different params for different outputs .....

[Camille Bégnis]

Hi,

that should do the trick:
http://docbook.sourceforge.net/release/xsl/current/doc/html/ignore.image.scaling.html

Camille.

Kerry, Richard wrote:
  
 Team,
  
 I have a DocBook source file that includes a reference to a png file
 for a diagram.
  
 When I generate a pdf file from it (via FO using FOP) I need to
 specify a scaling.
 ie
 imagedata fileref=./Diagrams/Flowchart.png scale=35 /
  
 When I generate an html file I don't.
 ie
 imagedata fileref=./Diagrams/Flowchart.png /
  
 What's my best way to handle this ? 
 Of course I don't want to have two separate DocBook source files for
 the two output formats.
  
  
 Regards,
 Richard.
  
  
  

 *Richard Kerry**
 *Colledia Control Engineer*
 *Siemens IT Solutions and Services Ltd**/
 /Room 457 Drama Building, BBC Television Centre, Wood Lane, London,
 W12 7RJ*/
 /**T:* +44 (0)20 822*59063* *F:* +44 (0)20 8576 8182 *M:* +44 (0)7921
 244993
 *Email:* richard.ke...@siemens.com
 blocked::mailto:richard.ke...@siemens.com
 *Website:  **www.siemens.co.uk/it-solutions
 blocked::outbind://47/www.siemens.co.uk/it-solutions*

 This e-mail contains confidential information and is for the exclusive
 use of the addressee/s.  If you are not the addressee, then any
 distribution, copying or use of this e-mail is prohibited. If received
 in error, please advise the sender and delete it immediately.  We
 accept no liability for any loss or damage suffered by any person
 arising from use of this e-mail.

 *Siemens IT Solutions and Services Limited**
 *Registered No: 1203466 England
 Registered Office: Faraday House, Sir William Siemens Square, Frimley,
 Camberley, GU16 8QD

  
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


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

[Camille Bégnis]

Hi,

please look at this thread:
http://markmail.org/message/u7fccvab3obvovul?q=docbook+diffmk+configurationpage=1refer=ygqxnn6mvplvdcua

Camille.

Marcel Tromp wrote:
 I am trying to use diffmk 3.0.a1 to generate change markup for
 docbook5. It is kind of working, but I have certain changesets where
 deleted text is put in a phrase at an illegal location as well as an
 superfluous /section:

 /section
 phrase revisionflag=deletedSome deleted Text./phrase
 /section

 I also read diffmk needs a diffmk.xml config file, but I am not able
 to have the tool pick it up. How is this done? Is this file still
 relevant for version 3.0.a1 (it is not part of the distribution)?

 Or should I just switch to DeltaXML? Their licensing model is a bit
 painful (cpu core based instead of number of concurrent users) and
 will pretty much prevent us from local docbook processing.

 Thanks,

 Marcel
 --

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] Consultants who work with Docbook implementations

[Camille Bégnis]

Hi all,

indeed I think there is no such think as a DocBook consultants listing,
is there one?

I have created this page on the wiki:
http://wiki.docbook.org/topic/DocBookConsultancy
Please feel free to improve it, and I suggest to everyone here that can
provide paid support for DocBook to register there.

I think this is also an opportunity for professional to identify others
that can help out :-)

Greetings to everyone,

Camille.

Karen Schneider wrote:
 Is there a list or wiki for these? If you are such a consultant,
 please feel free to contact me directly at k...@esilibrary.com
 mailto:k...@esilibrary.com.

 (Oh, and happy holidays, and all that!)

 -- 
 -- 
 | Karen G. Schneider
 | Community Librarian
 | Equinox Software Inc. The Evergreen Experts
 | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712
 | E-Mail/AIM: k...@esilibrary.com mailto:k...@esilibrary.com
 | Web: http://www.esilibrary.com
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] Announce: Calenco: a collaborative XML CMS for DocBook

[Camille Bégnis]

Hello,

We (http://www.neodoc.biz) have been working for a long time on an
internal project that could allow us to collaborate on documentation
projects.

This project is now released under a Free license and offers the
following features:
- Store content (XML, XSL, images, etc.) in a central repository, on a
project and language basis
- Transform content on the server to PDF or HTML
- All through a simple Web Interface

This release supports DocBook v5 out of the box.

You will find all details here: http://trac.calenco.com/
Including access to a live demo platform.

We would be pleased to read your comments, do not hesitate to contact us
for assistance.

Best regards,

Camille.
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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] Announce: Calenco: a collaborative XML CMS for DocBook

[Camille Bégnis]

Dave Pawson wrote:

 From a docbook view, can a group of users each provide (for example)
 on chapter of a book?
Yes absolutely, that's exactly what the system has been designed for.
 Then the entire book is generated?
yes, through xincludes that are processed during documents transformation.
 I.e. collaborative authoring using docbook?
errr yes, looks like I must improve my communication skills yet :-)
 (The multiple languages is a neat idea :-)
Thanks,

Camille.
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:cami...@neodoc.biz
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
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 and XLIFF

[Camille Bégnis]

Hello,

I have been looking for means to inject DocBook documents strings into a
translation system (namely pootle) through XLIFF.

I have found a few solutions:
http://transolution.python-hosting.com/
https://open-language-tools.dev.java.net/
http://sourceforge.net/projects/xliffroundtrip/

But what do you use for the purpose of easing translation of DocBook
files for translators used to CAT tools?

Camille.
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] Re: [docbook] marking up a play

[Camille Bégnis]

Hello,

IMVHO TEI (http://www.tei-c.org/) is best suited for the task than docbook.

Camille.

Dieter Baron wrote:
 hi,

 is there a standard way to mark up a theatrical play using docbook?

   thanks,
   dillo

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
   
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] different background-color in header table for different chapters

[Camille Bégnis]

Hello,

you just need to make a test and set the color according to the chapter 
cardinality, something like:



xsl:attribute-set name=header.table.properties
  xsl:attribute name=background-color
xsl:choose
  xsl:when test=preceding-sibling::chaptergreen/xsl:when
  xsl:otherwisered/xsl:otherwise
/xsl:choose
  /xsl:attribute
/xsl:attribute-set

Camille.

Lily Galle wrote:

Dear all,

I produce one book with “DocBook” and “XSL”. 

There is one header on each page. 
In Chapter 1 the “header.table” has “background-color” red. In chapter two it should have “background-color” green. (“header.table” in different chapter should have different background-color.)


I write the following code in “myStylesheet.xsl”. 


xsl:attribute-set name=header.table.properties
   xsl:attribute name=background-colorred/xsl:attribute
/xsl:attribute-set

But how can I get “green” for chapter two?

I copied the template “header.table” in my customized stylesheet. But I do not know how to customize it. 


Thanks for any help!

Lily


  
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Parameters in Docbook Article

[Camille Bégnis]

Russell Seymour wrote:

Camille,

That worked brilliantly, thanks.


Great, actually I had never thought about it before, but I guess that's 
something that could be generalized and possibly included by default in 
the docbook XSL.


What's the others experience with this kind of requirement? (as a 
replacement to SGML ENTITY...)

What system did you use? Xinclude?


Camille.

Russell

2008/8/26 Russell Seymour [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED]


Camille,

Thanks very much for the pointer.  I will give it a go and let you
know how it goes.

Russell



2008/8/26 Camille Bégnis [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]

Hi,

yes that looks completely reasonable, you'd just need to
decide what markup in the source XML would be used to hold the
client name, for example phrase role=xslparam
vendor=output.client/ (completely wild guess).

and then define in your custom XSL the function that will
match the above element and replace it with the content of the
$output.client parameter

Hope that helps,

Camille.


Russell Seymour wrote:

Good afternoon,

I am starting to work with Docbook again after a long time
of not using it.

I am trying to find my feet again, and I am sure there is
something that I used to do that I cannot work out how to
do how so I am hoping you will be able to assist me.

I would like to set a parameter on the command line that
sets the client, e.g. --stringparam output.client ACME
and then use the output.client within the Docbook markup
and for ACME to be displayed in the final output.

Is this possible or have I lost I completely lost the plot?

Thanks, Russell



begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] Error transforming double-sided DocBook with fop

[Camille Bégnis]

Hi all,

we have just found a problem with stylesheets 1.74 and parameter 
double.sided=1


software used:
   - Saxon 6.5.5
   - Same happens with fop 0.95 and 0.94

The below error are thrown by fop when transforming a double sided fo 
file generated with Saxon and DocBook XSL1.74.


Any idea?

Camille Bégnis.


$ saxon -o test.fo Test.xml 
/opt/docbook-xsl-1.74.0/fo/profile-docbook.xsl double.sided=1


$ fop test.fo test.pdf
13 août 2008 11:30:47 org.apache.fop.fonts.FontInfo notifyFontReplacement
ATTENTION: Font 'Symbol,normal,700' not found. Substituting with
'Symbol,normal,400'.
13 août 2008 11:30:47 org.apache.fop.fonts.FontInfo notifyFontReplacement
ATTENTION: Font 'ZapfDingbats,normal,700' not found. Substituting with
'ZapfDingbats,normal,400'.
13 août 2008 11:30:47 org.apache.fop.hyphenation.Hyphenator
getHyphenationTree
GRAVE: Couldn't find hyphenation pattern en
13 août 2008 11:30:47 org.apache.fop.cli.Main startFOP
GRAVE: Exception
java.lang.IllegalStateException: Flow 'xsl-region-body' does not map to
the region-body in page-master 'blank'.  FOP presently does not support
this.
   at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)

-

java.lang.IllegalStateException: Flow 'xsl-region-body' does not map to
the region-body in page-master 'blank'.  FOP presently does not support
this.
   at
org.apache.fop.layoutmgr.PageProvider.cacheNextPage(PageProvider.java:275)
   at
org.apache.fop.layoutmgr.PageProvider.getPage(PageProvider.java:221)
   at
org.apache.fop.layoutmgr.PageProvider.getPage(PageProvider.java:185)
   at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.createPage(PageSequenceLayoutManager.java:139)
   at
org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.makeNewPage(AbstractPageSequenceLayoutManager.java:289)
   at
org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.doForcePageCount(AbstractPageSequenceLayoutManager.java:370)
   at
org.apache.fop.area.AreaTreeHandler.finishPrevPageSequence(AreaTreeHandler.java:186)
   at
org.apache.fop.area.AreaTreeHandler.startAbstractPageSequence(AreaTreeHandler.java:199)
   at
org.apache.fop.area.AreaTreeHandler.startPageSequence(AreaTreeHandler.java:194)
   at
org.apache.fop.fo.pagination.PageSequence.startOfNode(PageSequence.java:114)
   at
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:295)
   at
org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:163)
   at
org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072)
   at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
   at
org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
   at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
   at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown 


Source)
   at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
   at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
   at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
   at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:214)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)


begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Error transforming double-sided DocBook with fop

[Camille Bégnis]

Ah my bad, fop1.extension=1 was missing of course... I thought the 
stylesheets would support fop by default now...


Sorry for noise,

Camille.

Camille Bégnis wrote:

Hi all,

we have just found a problem with stylesheets 1.74 and parameter 
double.sided=1


software used:
   - Saxon 6.5.5
   - Same happens with fop 0.95 and 0.94

The below error are thrown by fop when transforming a double sided fo 
file generated with Saxon and DocBook XSL1.74.


Any idea?

Camille Bégnis.


$ saxon -o test.fo Test.xml 
/opt/docbook-xsl-1.74.0/fo/profile-docbook.xsl double.sided=1


$ fop test.fo test.pdf
13 août 2008 11:30:47 org.apache.fop.fonts.FontInfo notifyFontReplacement
ATTENTION: Font 'Symbol,normal,700' not found. Substituting with
'Symbol,normal,400'.
13 août 2008 11:30:47 org.apache.fop.fonts.FontInfo notifyFontReplacement
ATTENTION: Font 'ZapfDingbats,normal,700' not found. Substituting with
'ZapfDingbats,normal,400'.
13 août 2008 11:30:47 org.apache.fop.hyphenation.Hyphenator
getHyphenationTree
GRAVE: Couldn't find hyphenation pattern en
13 août 2008 11:30:47 org.apache.fop.cli.Main startFOP
GRAVE: Exception
java.lang.IllegalStateException: Flow 'xsl-region-body' does not map to
the region-body in page-master 'blank'.  FOP presently does not support
this.
   at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)

-

java.lang.IllegalStateException: Flow 'xsl-region-body' does not map to
the region-body in page-master 'blank'.  FOP presently does not support
this.
   at
org.apache.fop.layoutmgr.PageProvider.cacheNextPage(PageProvider.java:275) 


   at
org.apache.fop.layoutmgr.PageProvider.getPage(PageProvider.java:221)
   at
org.apache.fop.layoutmgr.PageProvider.getPage(PageProvider.java:185)
   at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.createPage(PageSequenceLayoutManager.java:139) 


   at
org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.makeNewPage(AbstractPageSequenceLayoutManager.java:289) 


   at
org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.doForcePageCount(AbstractPageSequenceLayoutManager.java:370) 


   at
org.apache.fop.area.AreaTreeHandler.finishPrevPageSequence(AreaTreeHandler.java:186) 


   at
org.apache.fop.area.AreaTreeHandler.startAbstractPageSequence(AreaTreeHandler.java:199) 


   at
org.apache.fop.area.AreaTreeHandler.startPageSequence(AreaTreeHandler.java:194) 


   at
org.apache.fop.fo.pagination.PageSequence.startOfNode(PageSequence.java:114) 


   at
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:295) 


   at
org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:163)
   at
org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072) 


   at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
   at
org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
   at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
   at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown 


Source)
   at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 


Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown 
Source)

   at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
   at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) 


   at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:214)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] DiffMk configuration

[Camille Bégnis]

Hi,

this is just a wild guess, put let's put ourselves in diffmk shoes,
walking down the XML tree:

1- I find a title, identical content, OK
2- I find a para, identical content, OK
3- I find a para in old, it is also in new, I output it.
4- When I compare the content of this para I realize it is different, so
I -Huh- do something
5- Next para is only in new so Ipara diffmk:change=added

Providing diffmk does not look forward -which would have allowed it to
see para2 was actually moved- I think the issue is in step 4 where we
should have @diffmk:changed = 'changed'.

Actually it's not the first issue I found in diffmk, Norman always
stated this was alpha, and I'm afraid he has other xml cats to whip at
the moment...

XML diff is quite a challenge, some guys spent PhD thesis on the topic...

Camille.

Jeff Hooker wrote:
 Hi,

 After more testing, I've found an issue which I hope someone finds familar.

 For in-line changes, DiffMk works fine, wrapping changes in tagged markers 
 exactly as advertised. For changes to structural elements, however, it is 
 reliably incorrect. When adding a PARA element, for example, it will wrap the 
 content of the PARA element in a new element, and then also mark the 
 following sibling PARA element as added. This holds true for sections, 
 chapters, books, etc. Adding one element results in the following sibling 
 being marked as new.

 old.xml
 ---
 article
 titleThis is the title/title
 parapara1/para
 parapara2/para
 /article

 new.xml
 ---
 article
 titleThis is the title/title
 parapara1/para
 parapara3/para
 parapara2/para
 /article

 output.xml
 --
 article diffmk:version=3.0 xmlns:diffmk=http://diffmk.sf.net/ns/diff;
 titleThis is the title/title
 parapara1/para
 paradiffmk:wrapper diffmk:change=addedpara3/diffmk:wrapper/para
 para diffmk:change=addedpara2/para
 /article

 The problem affects only the following sibling; if the element is that last 
 child element, then the next elements on the tree are unaffected. If there 
 are more than one siblings following the affected element, they are untouched.

 Does this look familar to anyone?

 Thanks,
 Jeff.

 -Original Message-
 From: Camille Bégnis [mailto:[EMAIL PROTECTED]
 Sent: Friday, May 30, 2008 2:15 AM
 To: Jeff Hooker
 Cc: apps docbook
 Subject: Re: [docbook-apps] DiffMk configuration


 Hi,

 please find attached those two files as I use them, I can't recall if I
 modified them for my own use, better review it.

 H after digging further I think Norm had sent me a modified jar, I
 might have modified the XSL too, so I put the whole modified package I
 use here: http://www.neodoc.biz/files/diffmk-3.0.a1.patch.zip

 Note I could never make the --diff option work.

 Good luck,

 Camille.

 Jeff Hooker wrote:
   
 Hi all,

 I *think* this is appropriate for this list. If not, my apologies.

 I'm trying to get DiffMk (http://nwalsh.com/java/diffmk/index.html) up and 
 running using Bob Stayton's instructions 
 (http://www.sagehill.net/docbookxsl/Changebars.html) and not having much 
 success for far.

 At the moment I'm just getting Failed to load Main-Class manifiest 
 attribute from diffmk.jar but I suspect that this is a config issue rather 
 than a java issue.

 Bob's instructions include reference to two files that do not seem to exist 
 in the current diffmk applicaton: diffmk.xml and DiffMk.properties, both of 
 which are supposed to reside in a nonexistant directory called config. 
 I've tracked  down a sample DiffMk.properties file, but am working blind 
 with the diffmk.xml file.

 Has anyone got this thing working, and if so, could you send me some 
 guidance?

 Thanks,
 Jeff

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
   
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
   
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Handling run-on lines?

[Camille Bégnis]

Hi,

 there are a few options to manage this situation, see
http://www.sagehill.net/docbookxsl/FittingText.html

Camille.

Jean Jordaan wrote:
 Hi all

 I have some long example lines from CSV files in my DocBook document.
 They wrap when printed. I'd like to ensure that these lines get an
 indicator that the linebreak is for formatting only. How do others
 handle this situation?

   
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Including external documents

[Camille Bégnis]

Hi,

if your appendix don't need to be tightly integrated in the document
(not appear in table of contents, no xrefs, etc.), there is a simple
solution that consists in sticking the resulting PDFs together using
pdftk for example. No need for complex pagemasters...

Camille (quick'n dirty mode).

John Brown wrote:
 Hello all,
 
 I want to have an appendix which includes forms, contracts, etc.  These
 documents were created in Microsoft Word. I want their appearance to be
 exactly the same as in Microsoft Word. Specifically, I do not want to see:
 
 Appendix A: Confidentiality Agreement
 
 I hereby agree that I will  ...
 [rest of agreement]
 
 Instead, I want Appendix A: Confidentiality Agreement on a page
 by itself with the usual headers and footers, followed by the agreement, 
 without any headers and footers.
 
 I converted a form to PDF and put it in an imageobject, but I need to stop
 DocBook from adding page numbers, inserting titles, etc.
 
 Is this possible?
 
 _
 Get in touch in an instant. Get Windows Live Messenger now.
 http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] orgname not displayed in authorgroup

[Camille Bégnis]

Hi,

after crawling up about a dozen templates I found out why my orgname was
not showing on verso book titlepage. It was not referenced within
person.name.first-last so I modified the template (see below). I'm not
sure this is the right place nor the right way to do it, I'll let
experts inject that upstream if needed.

Camille.


xsl:template name=person.name.first-last
  xsl:param name=node select=./

  xsl:if test=$node//honorific
xsl:apply-templates select=$node//honorific[1]/
xsl:value-of select=$punct.honorific/
  /xsl:if

  xsl:if test=$node//firstname
xsl:if test=$node//honorific
  xsl:text /xsl:text
/xsl:if
xsl:apply-templates select=$node//firstname[1]/
  /xsl:if

  xsl:if test=$node//othername and $author.othername.in.middle != 0
xsl:if test=$node//honorific or $node//firstname
  xsl:text /xsl:text
/xsl:if
xsl:apply-templates select=$node//othername[1]/
  /xsl:if

!-- Add orgname support --
  xsl:if test=$node//orgname
xsl:if test=$node//honorific or $node//firstname
  or ($node//othername and $author.othername.in.middle
!= 0)
  xsl:text /xsl:text
/xsl:if
xsl:apply-templates select=$node//orgname[1]/
  /xsl:if

  xsl:if test=$node//surname
xsl:if test=$node//honorific or $node//firstname
  or ($node//othername and $author.othername.in.middle
!= 0)
  xsl:text /xsl:text
/xsl:if
xsl:apply-templates select=$node//surname[1]/
  /xsl:if

  xsl:if test=$node//lineage
xsl:text, /xsl:text
xsl:apply-templates select=$node//lineage[1]/
  /xsl:if
/xsl:template
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Website. docbook v5? Documentation.

[Camille Bégnis]

Hi Dave,

speaking for http://www.neodoc.biz we use V5 for all our new projects
since many monthes now, and are now migrating old v4 to v5, since v5 is
now (almost?) official :-)

Schemas offer greater flexibility (though SGML entities might miss to
some) and tools support is great.

Finally DTD version of DB won't be further maintained I guess.

Camille.

Dave Pawson wrote:
 I'm about to start some additional documentation about using
 and building website.
 
 I'm tempted to port the schema to relax / docbook v5
 and document it based on that.
 
 Any opinions/preferences please?
 
 
 
 regards
 
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] Re: Russian translation of Mandriva's documentation

[Camille Bégnis]

[I'm following this on ML because that can be interesting for others.]

Hi,

you must first declare the fonts so fop can use them:
http://www.sagehill.net/docbookxsl/AddFont.html

Then you must tell what fonts to use for compilation in
XSL/docbook-fo-common.xsl

See the *.font.family parameters at the beginning of that file.

Let me know,

Camille.

Denis Philippov wrote:
 Camille Bégnis пишет:

 Denis Philippov wrote:
 Camille Bégnis пишет:
 OK, still one missing:

 xsltproc --xinclude  -o Master-Starter.fo ../XSL/docbook-fo.xsl
 Master-Starter.xml
 warning: failed to load external entity titlepage-urlblurb.xml
 Master-Starter.xml:19: element include: XInclude error : could not load
 titlepage-urlblurb.xml, and no fallback was found

 A few images are missing too.

 However I got the PDF? but the fonts do not have the Cyrillic glyphs,
 whch font do you suggest?

 Is where a choice?
 Should we use a free fonts? Or we may use a commercial ones?

 Free is better of course, which one you know that work?

 I want to use fonts that have a correct kerning info for a Cyrillic
 glyphs and that ones that correctly hinted. Where is no such free fonts.
 IMHO We should use some sans typeface for headers and serif for
 paragraph text.

 Can you provide such fonts?

 
 Teach me please where I should place the fonts on my system and what
 files should I edit.
 I want to try it by myself.
 
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] How to set the left and right margin of the page?

[Camille Bégnis]

Xuan Ngo wrote:
 How to set the left and right margin of the page?

Those are actually called inner and outer margins:
http://docbook.sourceforge.net/release/xsl/current/doc/fo/page.margin.inner.html
http://docbook.sourceforge.net/release/xsl/current/doc/fo/page.margin.outer.html

To take into account writing directions.

Camille.

 There are page.margin.bottom and page.margin.top parameters but not for left 
 and right margin.
 
 I'm using FOP v0.94 and Docbook v1.73.2
 
 thx!
 Xuan
 
 
   Looking for the perfect gift? Give the gift of Flickr! 
 
 http://www.flickr.com/gift/
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] large docbook files

[Camille Bégnis]

FYI I'm working on cleaning up their markup and crafting an XSL-FO
toolchain.

It works quite well, though fop memory had to be increased :-)

Camille.

Dave Pawson wrote:
 700+mb of docbook!
 http://www.markshuttleworth.com/archives/134
 
 Neat idea though.
 
 regards
 
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Docbook article

[Camille Bégnis]

Dave Pawson wrote:
 http://www.devx.com/Java/Article/35301

yes it got good coverage in news websites, good to see that DITA doesn't
get the exclusivity.

Camille.
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] Re: [docbook] configurable docbook to pdf

[Camille Bégnis]

Hi,

what you need is profiling http://www.sagehill.net/docbookxsl/Profiling.html

But I'm not sure why you want to set the level in the main document,
passing it as a parameter at publication time looks easier to me.

Otherwise you'll need to write a little XSLT code to define the
profiling parameters according to the level value in the main document.

Hope this helps,

Camille.

flemse6 wrote:
 Hello 
 
 I have a main document which contains 15 different chapters and each chapter
 is devided into 4 different files acconding to which level of access the
 document must be.
 
 Is it possible to define a level in the start of the main document where the
 access level can be defined. This way the main document can be used as main
 document for all access levels.
 
 I want to define that I need access level 3 which uses the first 3 files in
 each chapter.
 Acconding to this I can define the access level in the start of the main
 document and the right pdf document is created.
 
 Please help me


begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] application xsl-template

[Camille Bégnis]

Bonjour,

I'm not sur I understood, is this what you're looking for?

[EMAIL PROTECTED] docbook-xsl-1.73.0]$ grep -n 'template
match=application' */*.xsl
fo/inline.xsl:391:xsl:template match=application
html/inline.xsl:435:xsl:template match=application
xhtml/inline.xsl:416:xsl:template match=application


Camille.

Jacques Foucry wrote:
 Hello,
 
 It's stupdi, I know, but I cannot find de application xsl-template
 definition in the last 1.73 snapshot.
 
 Who can tel me where I can find it ?
 
 Thanks in advance,
 Jacques

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] chunking at book level

[Camille Bégnis]

Marie Sauvage - EBM WebSourcing wrote:
 I could be a solution but I'd have to do the toc and all navigation
 headers and footer manually... I have something like 15 books in a set,
 so chunking at chapter level makes a complicated navigation and a very
 long toc. So as our chapters aren't very long (some are just 10 lines or
 contain just a small table), we think it would be better to have one
 page per book.

I don't know your specific constraints, but maybe then your structure is
not appropriate, a chapter of just 10 lines looks odd to me.
Maybe lowering all your structure by one level:
set - book
book - chapter
chapter- section

would solve all your problems.

But as I stated, I don't know your other specific constraints...

Camille.

 Regards,
 Marie.
 
 Denis Bradford a écrit :
 If you want to build the entire set at once, I'm not sure how to chunk
 at the book level, maybe one of the wise heads here knows. But the
 usual way to get one document per book is to build each book
 separately, using docbook.xsl instead of chunk.xsl.

 hth,
 Denis

 Marie Sauvage - EBM WebSourcing wrote:
 Hi all !

 For my documentation, I have a set of many books, is it possible to
 make the chunk output splitting at book level to have only one page
 per book, instead of splitting at chapter level ?
 I've tried to decrease the chunk.section.depth to 1 or 0 but it has
 no effect.
 Maybe can I do this by customizing a template in the xsl stylesheet
 but I don't find which one, could you help me on that point ?

 thanks in advance !
 Marie.
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 - To
 unsubscribe, e-mail: [EMAIL PROTECTED] For
 additional commands, e-mail: [EMAIL PROTECTED]

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] chunking at book level

[Camille Bégnis]

I see.

Then I'd suggest a two-steps chain:
1) Extract all books in separate files by applying a simple splitting
stylesheet
2) Apply your output format transformation stylesheet to each of the
resulting files.

The advantage of such method is that you can apply any stylesheet
(notably PDF) to the resulting XML book files.

Camille.

Marie Sauvage - EBM WebSourcing wrote:
 it would be long to explain our constraints but we can't change this
 structure.
 Actually the set is a document grouping all our technical
 documentations. Their chapters are short because they have a global
 structure and some of them haven't many thing to complete some points...
 We first thought of transforming books in chapters but we want to be
 able to edit and generate them separately, and the structure is more
 logic that a module = a doc = a book.
 
 thanks for you suggestion,
 Marie.
 
 Camille Bégnis a écrit :
 Marie Sauvage - EBM WebSourcing wrote:
   
 I could be a solution but I'd have to do the toc and all navigation
 headers and footer manually... I have something like 15 books in a set,
 so chunking at chapter level makes a complicated navigation and a very
 long toc. So as our chapters aren't very long (some are just 10 lines or
 contain just a small table), we think it would be better to have one
 page per book.
 

 I don't know your specific constraints, but maybe then your structure is
 not appropriate, a chapter of just 10 lines looks odd to me.
 Maybe lowering all your structure by one level:
 set - book
 book - chapter
 chapter- section

 would solve all your problems.

 But as I stated, I don't know your other specific constraints...

 Camille.

   
 Regards,
 Marie.

 Denis Bradford a écrit :
 
 If you want to build the entire set at once, I'm not sure how to chunk
 at the book level, maybe one of the wise heads here knows. But the
 usual way to get one document per book is to build each book
 separately, using docbook.xsl instead of chunk.xsl.

 hth,
 Denis

 Marie Sauvage - EBM WebSourcing wrote:
   
 Hi all !

 For my documentation, I have a set of many books, is it possible to
 make the chunk output splitting at book level to have only one page
 per book, instead of splitting at chapter level ?
 I've tried to decrease the chunk.section.depth to 1 or 0 but it has
 no effect.
 Maybe can I do this by customizing a template in the xsl stylesheet
 but I don't find which one, could you help me on that point ?

 thanks in advance !
 Marie.
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

   
 - To
 unsubscribe, e-mail: [EMAIL PROTECTED] For
 additional commands, e-mail: [EMAIL PROTECTED]
 

   
 - To
 unsubscribe, e-mail: [EMAIL PROTECTED] For
 additional commands, e-mail: [EMAIL PROTECTED]

begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:;;139 rue Philippe de Girard;Pertuis;;84120;France
email;internet:[EMAIL PROTECTED]
tel;work:+33.9.54.96.99.55
tel;fax:+33.9.59.96.99.55
tel;cell:+33.6.33.15.10.23
url:http://www.neodoc.biz
version:2.1
end:vcard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] 'id=' unexpected attribute in DB5 documents

[Camille Bégnis]

Hi,

DB5 no uses the standard xml:id form instead, see
http://www.docbook.org/docs/howto/2006-05-16/#changes-linking

Camille.

Ron Catterall wrote:
 Validating db5 documents with relames I get 'unexpected attribute id'
 when I have appendix id=qwerty and figure id=asdfgh
 
 docbook-xsl-ns-1.73.0/fo/docbook.xsl
 
 java -Xss1024K -jar relames-20060319/relames.jar rng/docbook.rng
 /Library/Webserver/Documents/_XML/Lanc_db5/LL-db5.xml
 
 Is this a relames problem or a 1.73.0
 
 -- 
 
 Ron Catterall, Phd, DSc email: [EMAIL PROTECTED]
 Prolongacion de Hidalgo 140
 http://catterall.net/
 San Felipe del Aguatel: +52 951
 520 1821
 Oaxaca  68020  Mexico  fax: +1 530 348 8309
 - To
 unsubscribe, e-mail: [EMAIL PROTECTED] For
 additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] saxon, xerces, xinclude, and DB5 (was Re: [docbook-apps] trouble using FOP to process FO file generated by Xalan or Saxon)

[Camille Bégnis]

Hi all,

funny I'm struggling with similar issue.

I did set up saxon to use Xerces 2.9.0 and while full inclusions like

  xi:include href=Inserted.xml/

works, referencing an id with

  xi:include href=Inserted.xml xpointer=para/

doesn't work:

-
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to
fallback. Resource error reading file as XML (href='Inserted.xml').
Reason: XPointer resolution unsuccessful.
Error on line 8 column 52 of file:home/camille/test/master.xml:
  Error reported by XML parser: An 'include' failed, and no 'fallback'
element was found.
Transformation failed: Failed to parse stylesheet
-

This is with docbook 5 RNG. With Docbook 4 DTD it works.

I suspect this is because the parser has no way to know the xml:id
attribute is actually of ID type, while with DocBOok 4 it has the DTD to
learn thatthe id attribute is an ID.

Anyone succeeded using xinclude with xpointer=id with DB5 RNG?

Camille.



Jeff Powanda a écrit :
 One follow-up comment about using Xerces XML parser
 (http://xerces.apache.org/xerces2-j/) with Saxon or Xalan. The latest
 version of Xerces (2.9.0) fully supports XML inclusions (XInclude),
 including XPointer syntax.

 Regards,
 
 Jeff Powanda
 
  
 
 
 
 *From:* Jeff Powanda
 *Sent:* Sunday, June 10, 2007 11:14 PM
 *To:* '[EMAIL PROTECTED]'; docbook-apps@lists.oasis-open.org
 *Subject:* RE: [docbook-apps] trouble using FOP to process FO file
 generated by Xalan or Saxon
 
  
 
 Thanks, Bob! I followed your instructions and can now process my
 documents with xsltproc, Saxon, or Xalan. I appreciate your help.
 
  
 
 Regards,
 
 Jeff Powanda
 
  
 
 
 
 *From:* Bob Stayton [mailto:[EMAIL PROTECTED]
 *Sent:* Saturday, June 09, 2007 7:36 PM
 *To:* Jeff Powanda; docbook-apps@lists.oasis-open.org;
 [EMAIL PROTECTED]
 *Subject:* Re: [docbook-apps] trouble using FOP to process FO file
 generated by Xalan or Saxon
 
  
 
 Hi Jeff,
 
 The XIncludes in your XML file are not resolving.  That leaves your book
 improperly stuctured, leading to improperly structured FO output.  You
 should have seen an error message from the stylesheet about not having a
 template that matches xi:include.
 
  
 
 You need to set up either Saxon or Xalan with a recent version of Xerces
 parser and with the XInclude option turned on.  See this section in my book:
 
  
 
 http://www.sagehill.net/docbookxsl/Xinclude.html#JavaXIncludes
 
  
 
 Bob Stayton
 Sagehill Enterprises
 DocBook Consulting
 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
 
  
 
  
 
 - Original Message -
 
 *From:* Jeff Powanda mailto:[EMAIL PROTECTED]
 
 *To:* docbook-apps@lists.oasis-open.org
 mailto:docbook-apps@lists.oasis-open.org ;
 [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]
 
 *Sent:* Saturday, June 09, 2007 5:34 PM
 
 *Subject:* [docbook-apps] trouble using FOP to process FO file
 generated by Xalan or Saxon
 
  
 
 I was using xsltproc as my XSLT processor, but it ran out of memory
 on a large book, so I decided to try Xalan and Saxon to convert a
 test book. I set up Xalan and Saxon according to the instructions in
 Bob Stayton’s book, DocBook XSL: The Definitive Guide
 (http://www.sagehill.net/docbookxsl/index.html). However, when I try
 to use FOP 0.93 to convert either of the attached FO files, it
 reports the following exception:
 
  
 
 org.xml.sax.SAXParseException: Content is not allowed in prolog.
 
  
 
 I pasted full output of the exception below.
 
  
 
 Has anyone else experienced this problem? Please take a look at the
 attached FO files and tell me what’s wrong.
 
  
 
 Regards,
 
 Jeff Powanda
 
  
 
  
 
 [Fatal Error] :1:1: Content is not allowed in prolog.
 
 Jun 9, 2007 5:21:38 PM org.apache.fop.image.analyser.XMLReader
 createDocument
 
 WARNING: Error while constructing image from XML
 
 org.xml.sax.SAXParseException: Content is not allowed in prolog.
 
   at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
 
   at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown
 Source)
 
   at
 javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
 
   at
 org.apache.fop.image.analyser.XMLReader.createDocument(XMLReader.java:115)
 
   at
 org.apache.fop.image.analyser.XMLReader.loadImage(XMLReader.java:95)
 
   at
 org.apache.fop.image.analyser.XMLReader.verifySignature(XMLReader.java:65)
 
   at
 
 org.apache.fop.image.analyser.ImageReaderFactory.make(ImageReaderFactory.java:85)
 
   at
 

Re: [docbook-apps] saxon, xerces, xinclude, and DB5 (was Re: [docbook-apps] trouble using FOP to process FO file generated by Xalan or Saxon)

[Camille Bégnis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks Dave and George,

so is there another parser that would support this (without applying a
patch), and how to use it with saxon?

Thanks,

Camille.

Dave Pawson a écrit :
 Camille Bégnis wrote:
 Hi all,

 funny I'm struggling with similar issue.

 I did set up saxon to use Xerces 2.9.0 and while full inclusions like

   xi:include href=Inserted.xml/

 works, referencing an id with

   xi:include href=Inserted.xml xpointer=para/

 doesn't work:

 ---
 
 I don't think the Xerces parser fully implements the xpointer stuff
 Camille. Simple xincludes yes, but not partial includes.
 
 
 
 
 
 regards
 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFGbsGijv9P65BfOUMRAq5LAKCTns4D/p6k9Yb6cJd2xJXQRGr7QQCfT2S9
rrJefweOUitPAvJ674kqZxI=
=QaKG
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] images scaling with maximum

[Camille Bégnis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

quoting http://www.sagehill.net/docbookxsl/ImageSizing.html

To keep a graphic for printed output at its natural size unless it is
too large to fit the available width, in which case shrink it to fit,
use scalefit=1, width=100%, and contentheight=100% attributes.

First a note to Bob: it seems it is contentdepth instead of contentheight.


So this works fine, I can also have the image reduced, while it being
kept within the content area using contentdepth=80%.
However if I use contentdepth=150% the image goes out of the content
area. Can I prevent that?

I am using XEP.

Camille.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFGSW+6jv9P65BfOUMRAs9BAKCZ0gkBlzkmh40K2yjac8+qsiT/4QCgm5+o
ds7Nj+a2fQrF4z8ab5iendA=
=yYND
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Newbie-question: para doesn't render into paragraphs

[Camille Bégnis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Gueven Bay a écrit :
 Hello,
 
 I made a Docbook document in which I am using para like this: (1)
 I am using Ubuntu 7.04 where I have installed:
 docbook-xml 4.4-5, docbook-xsl 1.71.0.dfsg.1-1.1 and
 libxslt1.1 1.1.20-0ubuntu2, xsltproc 1.1.20-0ubuntu2.
 
 If transforming my document with:
  
 xsltproc /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/onechunk.xsl 
 exam101.xml  exam101.html
 
 then the para doesn't render into own paragraphs. 
 Instead I get one line of output.

This snippet is not valid: as the documentation puts it: formalpara — A
paragraph with a title

Aka: only one paragraph.

In your case I'd simply use a section tag instead of formalpara.

Camille.

 You can have a look at the transformed docs here: (2) (in this archive you 
 also find the docbook documents.) 
 
 My question: How do I get one paragraph out of every para in my document?
 
 Thank you. 
 regards
 Gueven
 
 
 (1)
 formalpara
   title
 The following is a partial list of the used files, terms and utilities:
   /title
   para
 For Linux:
 ldd
 ldconfig
 /etc/ld.so.conf
 LD_LIBRARY_PATH
   /para
   para
 For FreeBSD:
 /usr/bin/ldd
 ldconfid
 /etc/ld.so.conf
 /etc/ld-elf.so.conf
   /para
   para
 For NetBSD:
 /usr/bin/ldd
 ldconfig
 /etc/ld.so.conf
/para
para
 For OpenSolaris:
 ldd(1)
 ld.so.1(1)
 /var/ld/ld.config
   /para
 /formalpara
 
 (2)
 http://rapidshare.com/files/27161539/lpiport.tar.gz.html
 http://rapidshare.com/files/27161846/lpiport.tar.gz.md5.html
 ___
 SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
 kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFGLvzijv9P65BfOUMRArq6AJ9GhGDQyfCmBbxdhAfMJYgoh8gqsACfbY+m
oTEV4+BAUpL8YP2pmIpqpeQ=
=HRxT
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Newbie-question: para doesn't render into paragraphs

[Camille Bégnis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Gueven Bay a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 Gueven Bay a écrit :
 Hello,

 I made a Docbook document in which I am using para like this: (1)
 I am using Ubuntu 7.04 where I have installed:
 docbook-xml 4.4-5, docbook-xsl 1.71.0.dfsg.1-1.1 and
 libxslt1.1 1.1.20-0ubuntu2, xsltproc 1.1.20-0ubuntu2.

 If transforming my document with:
  
 xsltproc /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/onechunk.xsl 
 exam101.xml  exam101.html

 then the para doesn't render into own paragraphs. 
 Instead I get one line of output.
 This snippet is not valid: as the documentation puts it: formalpara � A
 paragraph with a title
 
 Yes, this snippet is not valid because it is copypasted out from a large 
 document only to show
 how I am using para. But I gave you the link where you can download the 
 whole document which
 is valid and renders with xsltproc fine BUT with the problem I mentioned with 
 the para sections.
 (Please look at the bottom of this mail where you can find the link.)
 
 Aka: only one paragraph.
 In your case I'd simply use a section tag instead of formalpara.
 
 Thank you for your answer. Before I made the formalpara sections they were 
 sect2 sections.
 This rendered into a ugly looking html with TOC links everywhere. So I went 
 and made the sect2
 to formalpara with which i get rid of the TOCs.

Ah OK, that's a completely differetn problem :-) See
http://www.sagehill.net/docbookxsl/TOCcontrol.html#TOClevels


  
 Camille.

 You can have a look at the transformed docs here: (2) (in this archive you 
 also find the docbook documents.) 

 My question: How do I get one paragraph out of every para in my document?

 Thank you. 
 regards
 Gueven


 (1)
 formalpara
   title
 The following is a partial list of the used files, terms and utilities:
   /title
   para
 For Linux:
 ldd
 ldconfig
 /etc/ld.so.conf
 LD_LIBRARY_PATH
   /para
   para
 For FreeBSD:
 /usr/bin/ldd
 ldconfid
 /etc/ld.so.conf
 /etc/ld-elf.so.conf
   /para
   para
 For NetBSD:
 /usr/bin/ldd
 ldconfig
 /etc/ld.so.conf
/para
para
 For OpenSolaris:
 ldd(1)
 ld.so.1(1)
 /var/ld/ld.config
   /para
 /formalpara

 (2)
 http://rapidshare.com/files/27161539/lpiport.tar.gz.html
 http://rapidshare.com/files/27161846/lpiport.tar.gz.md5.html
 
 
 
 ___
 SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
 kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD4DBQFGLwIsjv9P65BfOUMRAp2xAJICmj9QvV9GE9OKPfZDbvjoddVXAKCnRMGo
+/TJUcrtgJ42BrsZBemeww==
=5E8E
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] translation of docbook documents

[Camille Bégnis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hinrich Aue a écrit :
 Hello there,
 
  
 
 Does anyone have experience in translating docbook documents?
 
 Are there any tools out there to assist? What is the best approach?


There's also XLIFF:
http://www-128.ibm.com/developerworks/xml/library/x-localis2/

Camille.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFGE7QAjv9P65BfOUMRArb8AJ0cHqooQCOKTw7SEUa9+Dmob5jeUgCgrIHs
CUrUjTjCCY2LzZmVK0vT/98=
=P4TJ
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DOCBOOK-APPS: Error in Page numbering

[Camille Bégnis]

Hello,

running openjade on following sample with stock 1.77 stylesheets
---
book
  titletest/title
  chapter
titleFirst Chapter/title
parablabla/para
  /chapter
  part
titleFirst Part/title
  chapter
titleSecond Chapter/title
parablabla/para
  /chapter
  /part
/book
---
gives the following page sequence:
--
[blank] (Title page)
[blank]
iii (TOC)
1   (First Chapter)
[blank] (Part I)
2   (Second Chapter)
--
Which is wrong because last page should be numbered 3 (For larger 
first chapters, the first page of second chapter is always 2)

Then if I enclose the first chapter in a part, I also get the page sequence:
--
[blank] (Title page)
[blank]
iii (TOC)
[blank] (Part I)
1   (First Chapter)
[blank] (Part I)
2   (Second Chapter)
--
Funnily, If I set the parameter: (define %generate-part-titlepage% #f) 
the page sequence gets OK in the second case. Not the first one.

Should I report a bug or is this behavior intended? Is there a parameter 
that may change that?

This testcase shows another minor issue: the page pointed at in the 
TOC for the parts is the page of the following chapter, not the part 
title page.

Camille.

DOCBOOK-APPS: Ending a book with Notes

[Camille Bégnis]

Hello,

For printing reasons, printed books usually ends with a few to many 
blank pages.

Has someone come up with a solution with DocBook to fill those blank 
pages with a Notes header?

Camille.

Re: DOCBOOK-APPS: Doubled page numbers with preface

[Camille Bégnis]

Ian Castle wrote:

There is an extra patch somewhere to cope with that.

The rule is to start renumbering when you get to the main thing.
However, you've got more than main thing

..I had a patch for that floating around somewhere.. but it isn't too
hard to fix.. What is hard is coming up with a nice general rule -
because there isn't really anything that says this is where we want to
set numbers back to 1... It could be the first chapter, or the first
preface or the first foreword 


So why not adding a new parameter, say %restart-page-numbering-at%, 
holding the element for which first occurence in document would trigger 
renumbering. As a fallback (element absent from doc) start numbering 
from 1 on titlepage.

Also, what if someone wants same numbering for whole doc?

.. Actually, I suppose it could be done.. but it was too hard to fit
into the existing structure.


On Fri, 2002-11-29 at 14:54, Camille Bégnis wrote:


Hi,

I have noticed the print dsssl backend (1.77) numbers first pages i, ii, 
... (starting from book titlepage) and then restart i, ii, ... on 
preface. Is this intended?

Camille.

Re: DOCBOOK-APPS: Ignoring image widths in HTML--a solution

[Camille Bégnis]

Dennis Grace wrote:
  A couple weeks back, Camille posed this question:
 
 
  I am using in my documents the same image format for both PDF and HTML
  outputs (PNG). Though I want to specify the width for PDF output but not
  for HTML. An option is to define two different imageobject but I find
  much easier to change the XSL template for imageobject and ignore the
  width.
 
  Can someone tell me the easier way to do so?
  
 
  I've been working on solutions for the same problem. I, too, found the
  two-different-imageobjects solutions less than satisfactory (that whole
  dual source issue).

the resolution trick is brilliant. Though it is not an option when you
have more than one thousand images...

  So far, my best solution has been external to DocBook. In GIMP or
  PhotoShop, I can alter the resolution to find the optimum pixels/inch
  (pixels/mm) for a given size. An image that looks good in the browser at,
  say, 640 pixels wide will--at a resolution of 72 pixels/inch (2.8346
  pixels/mm)--be too wide (8.9 in[225.8 mm]) for standard page outputs.
  Resetting the resolution to 110 pixels/inch (4.33 pixels/mm) reduces the
  print version to a printable width of 5.8 in ( 147.8 cm) while retaining
  the total pixel width unaffected for HTML output.
 
  Dennis Grace
 
  Information Developer
  IBM Linux Technology Center
  (512) 838-3937  T/L 678-3937  cell: (512)-296-7830
  [EMAIL PROTECTED]
 
  There are only 10 kinds of people in the world: those who understand 
binary
  and those who don't.
 
 

Re: DOCBOOK-APPS: xsltproc segfaults with 1.51.1

[Camille Bégnis]

Hi,

The following is my version that segfaults:
-
Using libxml 20420, libxslt 10018 and libexslt 709
xsltproc was compiled against libxml 20421, libxslt 10018 and libexslt 709
libxslt 10018 was compiled against libxml 20421
libexslt 709 was compiled against libxml 20421
-

Indeed using 
ftp://ftp.gnome.org/pub/GNOME/stable/redhat/i386/libxslt/libxslt-1.0.18-1.i386.rpm
I don't get anymore segfault, just:
-
Error Undefined namespace prefix
xmlXPathCompiledEval: evaluation failed
-

And this version looks slightly older than Mandrake (above) one:
-
Using libxml 20420, libxslt 10018 and libexslt 709
xsltproc was compiled against libxml 20419, libxslt 10018 and libexslt 709
libxslt 10018 was compiled against libxml 20419
libexslt 709 was compiled against libxml 20419
-

So now, what's the problem(s):
- a bug in libxslt ?
- a bug in the 1.51.1 XSL?
- a bug in the compilation/packaging step?

Camille.

Michael Smith wrote:
 Daniel Veillard [EMAIL PROTECTED] writes:
 
 
On Wed, Jun 05, 2002 at 06:09:39AM -0500, Michael Smith wrote:

Camille Bégnis [EMAIL PROTECTED] writes:


Hmm, tracking down to the code causing the error was easier than I
thought: the following sample works fine with 1.48 and makes xsltproc
1.0.18 segfault with 1.51.1 html (works with FO).

Yep -- I just tried the same doc instance below on my environment with
xsltproc and the current (cvs) version of the stylesheets
(html/docbook.xsl) and reproduced the same segfault.

  Hum, I can't reproduce it here:

paphio:~/XSLT/tests/docbook - /usr/bin/xsltproc  
~/tmp/docbook-xsl-1.51.1/html/docbook.xsl tst.xml 
Error Undefined namespace prefix
xmlXPathCompiledEval: evaluation failed
htmlheadmeta content=text/html; charset=ISO-8859-1 
http-equiv=Content-Typetitlexsltproc segfault test/titlemeta name=generator 
content=DocBook XSL Stylesheets V1.51.1/headbody bgcolor=white text=black 
link=#FF vlink=#840084 alink=#FFdiv class=articlediv 
class=titlepagedivh2 class=titlea name=id2760937/axsltproc segfault 
test/h2/divhr/div/div/body/html
paphio:~/XSLT/tests/docbook - /usr/bin/xsltproc --version
Using libxml 20422, libxslt 10018 and libexslt 709
xsltproc was compiled against libxml 20419, libxslt 10018 and libexslt 709
libxslt 10018 was compiled against libxml 20419
libexslt 709 was compiled against libxml 20419
paphio:~/XSLT/tests/docbook - 

 Same for my development version from libxslt/libxml2 CVS, I will dig up about
the Undefined namespace prefix error ... but can you check first with the
RPMs from ftp://xmlsoft.org/
 
 
 I compiled from latest release source (libxslt-1.0.18)  I get no
 segfault running xsltproc built from that on the same test file (only
 error is the 'Undefined namespace prefix' thing).
 
 The xsltproc version I got the segfault from was:
 
   Using libxml 20417, libxslt 10013 and libexslt 705
   xsltproc was compiled against libxml 20417, libxslt 10013 and libexslt 705
   libxslt 10013 was compiled against libxml 20417
   libexslt 705 was compiled against libxml 20417
 
 But I get no segfault with newer-but-not-the-latest version on another
 machine:
 
   Using libxml 20419, libxslt 10016 and libexslt 707
   xsltproc was compiled against libxml 20419, libxslt 10016 and libexslt 707
   libxslt 10016 was compiled against libxml 20419
   libexslt 707 was compiled against libxml 20419
 
 That's the latest version packaged for Debian. Don't know what the
 latest are for other distros are, but it looks like if they're = 1.0.16
 won't get the segfault at least.
 
   --Mike
 
 
 

Re: DOCBOOK-APPS: pdf rendering problems

[Camille Bégnis]

Baráth Gábor wrote:
 Hi!
 
 I have some questions about docbook dsssl pdf rendering with jade
 and openjade.

Hi,

Some of these problems have been addressed here:
http://linux-mandrake.com/en/doc/project/pascal/fixingproblems.html

[...]


 Ps: Norm - the dsssl 1.76 hungarian lang. modul contains
 some problems which was also in xsl 1.4x but already fixed in
 1.5, like:
 chapter 1. is 1. fejezet in hungarian not fejezet 1.

I have already posted a RFE about that: same problem in Basque (Euskara).

Camille.

DOCBOOK-APPS: some parameters ignored in chunk.xsl

[Camille Bégnis]

Hello,

With XSL 1.50.0, xsltproc, and the following customization:

1) only index.html goes into html/ The rest is written in current directory
2) chunk.quietly is ignored

Is something missing?

Also, I'm wondering what the using.chunker parameter is for??

Camille.


-

?xml version='1.0'?
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
 version='1.0'
 xmlns=http://www.w3.org/TR/xhtml1/transitional;
 exclude-result-prefixes=#default

   xsl:import 
href=/usr/share/sgml/docbook/xsl-stylesheets/xhtml/chunk.xsl/

xsl:param name=base.dirhtml//xsl:param
xsl:param name=use.id.as.filename select='1'/
xsl:param name=chunk.quietly select='1'/

/xsl:stylesheet

Re: DOCBOOK-APPS: Keeping entities in a transformation

[Camille Bégnis]

Hi Jeff,

Jeff Beal wrote:
 I?m working an an XSL script to clean up my DocBook XML.  I?m running 
 into problems because all of the entities are declared in a top-level 
 driver file, and the content resides in about 3,000 external entities, 
 which do not include DOCTYPE declarations.  I need to maintain our 
 current file structure and naming scheme (which unfortunately does not 
 correspond directly to the XML.).
 
  
 
 How can I get the XSL process to ?ignore? undeclared entities and copy 
 the reference through to the result tree?

The easier is to preprocess your files simply replacing all  by amp;

Camille.

DOCBOOK-APPS: set-titlepage-verso-elements

[Camille Bégnis]

Hello,

I have added the following in my DSSSL customization layer (1.76), but 
it has o effect (the revision history still shows up on book verso title 
page). Am I missing something?

Camille.



(define (set-titlepage-verso-elements)
   (list (normalize title)
 (normalize subtitle)
 (normalize edition)
 (normalize pubdate)
 (normalize copyright)
 (normalize legalnotice)))

Re: DOCBOOK-APPS: Manage project documents with docbook

[Camille Bégnis]

Hello,

That reminds me I had written a Project Management DTD inspired from
projectManageSchema.
It was intended to be used as a file format for MrProject
(http://mrproject.codefactory.se/) but has not been used so far.

Here it is if it can be of any use to someone.

Camille.

[EMAIL PROTECTED] a écrit :
 
 Nancy,
 
 this makes sense. Your answer triggered a search that produced the
 following.
 http://xml.coverpages.org/projectManageSchema.html
 I'll have to look into it.
 
 Eric
 

 
 From Nancy (Paisner) Harrison [EMAIL PROTECTED] on 22 March 2002
 18'21'03
 To : [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject : Re: DOCBOOK-APPS: Manage project documents with docbook
 
 Hi,
 
 I can think of a number of information types (e.g. 'effort' defined in
 hours/days/weeks to do a task) that would be needed in a project mgmt or
 requirements mgmt DTD, which would be out of place in the kind of technical
 document that DocBook was designed for.  I can also think of lots of
 elements they would have in common, and lots of DocBook that (IMHO) would
 be completely irrelevant to project management
 
 The first step would be to analyze the subject area and come up with the
 information types you'd need.  If your goal is easy tranferral of data
 between the project management space and the technical document space, you
 need to know what you need for each, and then see where the overlaps and
 uniqueness lie.  The analysis for 'what you need' has already been done in
 the tech doc space, and the result is DocBook.  It sounds from your
 question  that the analysis hasn't been done in the project mgmt space, but
 since I've heard from various sources the idea that project mgmt data needs
 to be stored in XML, it presumably needs to be done. Only once it's been
 done can you start looking at where information can be reused across
 spaces.
 
 A thought, are any of the OASIS TCs working on this area? [There are so
 many of them that anything seems possible...]
 
 Nancy
 
 It is up to us to journey forth in search of new practices and new ideas
 that will enable us to create lives and organizations worthy of human
 habitation.Margaret Wheatley



!-- .. --
!-- ProjectXChange XML DTD V0.0.2  --
!-- File projectxchange.dtd .. --
!-- .. --
 
!-- Copyright 2001 Camille Bégnis


This DTD is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
 
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
 
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

--

!-- .. --
 
!-- This is the driver file for V0.01 of the ProjectXChange DTD.
 Please use the following formal public identifier to identify it:
 
 -//CodeFactory//DTD ProjectXChange XML V0.0.2//EN
--

!-- .. --

!-- This DTD is designed to store the data used by project management 
 software. It is expecially structured in the hope that it will be
 useful to various open-source project management tools. If you have
 any comment or suggestion, please contact the current maintainer of
 the DTD at camilleatmandrakesoft.com

 In its current state the XML structre can hold basic information
 about three different entities: budgets, tasks, and ressources
 (human, material and equipment). It also allow basic
 relationships between those three entities allowing the processor
 to manage money, time, human and physical ressources. --

!-- .. --

!-- The root element, project --
!ELEMENT project (name,description?,owners,budgets,tasks,resourcepools)
  !ATTLIST project projectid CDATA #REQUIRED


  !ELEMENT owners (owner*)

!ELEMENT owner EMPTY
  !ATTLIST owner resourceid CDATA #REQUIRED


  !ELEMENT budgets (budget*)

!ELEMENT budget (name?,(budgetlabor|budgetmaterial|budgetequipment|budgetother)+)
  !ATTLIST budget budgetid CDATA #REQUIRED

  !ELEMENT budgetlabor (costs)
!ATTLIST budgetlabor budgetlaborid CDATA #REQUIRED
!ATTLIST budgetlabor resourcename CDATA

Re: DOCBOOK-APPS: Announce: DocBook XSL Stylesheets V1.50.0

[Camille Bégnis]

Hi,

To RPM packages users (and packagers):

Up to now, each new release of a DSSSL or XSL stylesheets had its
corresponding RPM package but with the same name (docbook-style-dsssl
resp. docbook-style-xsl). Therefore installing a new version would
overwrite the previous one.

Another policy, based on new version numbering scheme, is to suffix the
name with the version number minus the last dot (i.e.
docbook-style-xsl-1.50) so that different versions with different public
APIs could coexist on a single system.

Would that be of any use to someone?


Camille.

Norman Walsh a écrit :
 
 For more information, see
 
   http://docbook.sourceforge.net/release/xsl/1.50.0/WhatsNew
 
 (Some temporary problem at SF prevented me from uploading the changes
 to the files in the SF release area.)
 
 The new version numbering scheme is an attempt to address stability
 issues brought to my attention by some of the larger documentation
 groups. The new plan is that changes to the middle number (50)
 indicate that there are some public API differences that could break
 existing customization layers. Changes to only the last number (0),
 point releases, should be safe for existing customization layers.
 I'm not sure that will always be true for all customization layers,
 but that's the plan.
 
 API changes are summarized in
 
   http://docbook.sourceforge.net/release/xsl/1.50.0/RELEASE-NOTES.html
 
 Share and enjoy!
 
 Be seeing you,
   norm
 
 --
 Norman Walsh [EMAIL PROTECTED]  | Individuality seems to be Nature's
 http://www.oasis-open.org/docbook/ | whole aim--and she cares nothing
 Chair, DocBook Technical Committee | for individuals.--Goethe

Re: DOCBOOK-APPS: same text in different areas

[Camille Bégnis]

Christopher J. Graham a écrit :
 
 Hello all:
 
 Is it possible to have the same para (or any other element) content in two
 locations? I am trying to make sure that if it is edited in one location,
 then the other is also updated.

Simply define an entity:
http://docbook.org/tdg/en/html/ch01.html#s-entities

Camille.

 For instance,
 
 paratext-a/para
 .
 .
 .
 paratext-a/para
 
 Regards
 
 
 Christopher Graham
 [EMAIL PROTECTED]
 
 PGP Fingerprint: F765 CCB5 B9CF 1285 7E3E  8CB0 0B1B 8454 9D66 D411

DOCBOOK-APPS: Admonition graphics customization

[Camille Bégnis]

hi,

The following DSSSL customization allow to get admonitions the following
way in PS/PDF:

   ___
  |   |  Admonition text here and there Admonition text here and
there
  | Adm  |  Admonition text here and there Admonition text here and
there
  | Graph|  Admonition text here and there Admonition text here and
there
  |   |  Admonition text here and there Admonition text here and
there
  |___|  Admonition text here and there Admonition text here and
there
 Admonition text here and there Admonition text here and
there


I thaught it might be of interest to some of you
Many thanks to Pascal Lo Re

Camille



;; Define the size of the admonition picture
;; The size must be placed between quotes
(define %admonImageSize% 24pt)
;; Define the size of the space between the picture and the text
;; and the width of the text
(define %admonColumnSpace% 03cm)
(define %admonTextWidth% 9cm)
;; Redifine of the $graphical-admonition$ function
(define ($graphical-admonition$)
  (let* ((adm   (current-node))
 (title (select-elements (children adm)
 (normalize title)))
 (title?(not (node-list-empty? title)))
 (adm-title (if title?
(with-mode title-sosofo-mode
  (process-node-list (node-list-first title)))
(literal (gentext-element-name adm
 (f-child   (node-list-first (children (current-node
 (r-child   (node-list-rest (children (current-node)
(make display-group
  space-before: %block-sep%
  space-after: %block-sep%
  start-indent: (+ (inherited-start-indent) ($admon-graphic-width$))
  font-family-name: %admon-font-family%
  font-size: (- %bf-size% 1pt)
  font-weight: 'medium
  font-posture: 'upright
  line-spacing: (* (- %bf-size% 1pt) %line-spacing-factor%)
  (if title?
  (sosofo-append
(make paragraph
  font-family-name: %title-font-family%
  font-weight: 'bold
  adm-title)
(make formatting-instruction
  data: (string-append \\begin{tabular}{rc}\\parbox{
%admonImageSize% }{\\includegraphics[width= %admonImageSize%
,keepaspectratio=true]{ ($admon-graphic$) }}\\parbox{
%admonTextWidth% }{))
(process-children)
(process-children)
(make formatting-instruction
  data: }\\end{tabular})
  )
  (sosofo-append
(make formatting-instruction
  data: (string-append \\begin{tabular}{c@{\\hspace{
%admonColumnSpace% }}c}\\parbox{ %admonImageSize%
}{\\vspace{\\baselineskip}\\includegraphics[width= %admonImageSize%
,keepaspectratio=true]{ ($admon-graphic$) }}\\parbox[t]{
%admonTextWidth% }{))
(process-node-list (children f-child))
(process-node-list r-child)
(make formatting-instruction
  data: }\\end{tabular})
  )
  )
  )
 )
)