[docbook-apps] Spell and grammar checking DocBook/ XML documents

[daniel . keyes]

Hi,
I´m probably not the first one to ask this question, but I still need to 
ask:
Is there any efficient, mostly MS-Word-like method to spell and grammar 
check XML documents and/ or their transformation results (HTML, Pdf, 
etc.)?
I admit that I´m pretty spoiled when it comes to spell checking. In 
private I use MS Word, but in my company we switched to Oxygen XML to 
maintain our user manual. We´re getting used to it, but there is still one 
major issue we need to handle: Spell and grammar checking.

Basically, our documents are available in thee formats: XML, HTML and PDF. 
Each document has approx 50 pages. (Some documents only have 20 pages, 
other more than 100). No matter how often we review a document, there will 
always be remaining mistakes.

So, is there any efficient way (workarounds included) to spell and grammar 
check our documents?

By the way, I´m already using the supplied Java spell checker, but it´s 
too simple. I also tried Hunspell Spell checker (Open Office spell 
checker), but it´s pretty useless since it won´t learn any words (Which is 
annoying since every second word is a technical term and therefore 
highlighted as a mistake. ).

Thanks for your help,

Daniel


===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] PDF transformation: Why is the right border of my inline "box" missing when I transform to PDF. It works for HTML and Oxygen XML Editor.

[daniel . keyes]

Hi,
thanks for your help Bob! 
At first, we first tried to run a transformation with fop 1.0. This didn´t 
work, so we used fop1.1rc1.

fop1.1.rc1 is still a release candidate, but it works just fine for our 
transformation. Each element / style is at its place and our PDFs finally 
show the right border of our buttons.

We really don´t what it was, but it looks like the FOP of our Oxygen 
version (13) couldn´t handle our style. 

If anyone has the same problem: You can download the latest FOP version on 
apache.org/dyn/closer.cgi/xmlgraphics/fop 


Thanks for your help!


Greetings,
Daniel




From:   "Bob Stayton" 
To: , , 
Date:   16.10.2012 20:18
Subject:Re: [docbook-apps] PDF transformation: Why is the right 
border of my inline "box" missing when I transform to PDF. It works for 
HTML  and Oxygen XML Editor.



I did some testing and found that the problem seems to be the FOP that 
ships with Oxygen 14.  Here is what I did.
 
I copied your customization and configured  an Oxygen 14 transformation to 
apply the customized stylesheet *and* run the built-in FOP processor.  For 
the Transformation Output tab, I said to Prompt for filename so I could 
keep track of the output.  That PDF file duplicated the result you were 
seeing with the missing right border.
 
Then I changed the transformation to just produce the FO output.  When I 
examined the FO output file, it looked ok.  When I subsequently processed 
that saved FO file with the FOP 1.0 I had installed separately on my 
system, the output showed the right border.
 
Then I changed the Oxygen configuration using Options > Preferences > XML 
> XSLT-FO-XQuery > FO Processors.  Under Apache FOP, I selected "Use other 
Apache FOP", and browsed to the fop.bat file that I had installed 
separately on my system.  I saved that configuration, and when I ran the 
transformation, the output showed the right border.
 
So I concluded that the version of FOP 1.0 that ships with Oxygen 14 seems 
to be the source of this problem.  Oddly, I compared the fop.jar in Oxygen 
14 to the fop.jar in my installation, and they are identical.  So I cannot 
explain why this happens.  But if you download FOP 1.0, install it, and 
point Oxygen 14 to use it, then you should get the right border.
 
And let Oxygen Support know about this (you can forward this information 
if you like).
 
Bob Stayton
Sagehill Enterprises
b...@sagehill.net

From: daniel.ke...@finaris.de 
Sent: Tuesday, October 16, 2012 5:22 AM
To: docbook-apps@lists.oasis-open.org 
Subject: Re: [docbook-apps] PDF transformation: Why is the right border of 
my inline "box" missing when I transform to PDF. It works for HTML and 
Oxygen XML Editor.

Hi, 

we tried to come up with a solution, but it didn´t work. 
After all, we considered that it would be best to reset the entire schema 
and stylesheet back to "factory settings". Starting from scratch seemed to 
be a good idea to find the error (we created a backup). All that remained 
was Oxygens supplied version of Docbook 5.0. 

We added our button style to the styelsheet: 



http://www.w3.org/1999/XSL/Transform";
xmlns:fo="http://www.w3.org/1999/XSL/Format";
xmlns:d = "http://docbook.org/ns/docbook";
xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns:exsl="http://exslt.org/common";
exclude-result-prefixes="d"
version="1.0">




 
 



 



as well as a matching counterpart to the schema docbookxi.rng. Everything 
else remained the same. 
However, the borders were still missing when transforming to PDF 

After all, the bottom line is that: 
- Except of the border, our custom style is working just fine. There is a 
link between stylesheet and schema 
- Its not Adobe Reader (Zoom etc.) 
- Its not our stylesheet or schema 

So what´s the problem? 
- Is it possible that Oxygen and its FO processor cannot handle our custom 
style? I know you told me that it´s propably not Saxxon, but is possible? 
- How did you (@Simon) manage to successfully transform our style to PDF? 
- Is is possible that Oxygen supplied an old or at least buggy version of 
DocBook 5.0? 
- How is it possible that our styles works if we use fo:block instead? We 
have several "boxes" in our manuals and their all rendered correctly. 


Thanks for your help. 



Greetings, 

Daniel Keyes 




From:DaveP  
To:docbook-apps@lists.oasis-open.org, 
Date:12.10.2012 16:04 
Subject:Re: [docbook-apps] PDF transformation: Why is the right 
border of my inline "box" missing when I transform to PDF. It works for 
HTML  and Oxygen XML Editor. 



On 10/12/2012 01:37 PM, daniel.ke...@finaris.de wrote:
> Hi Simon,
>
> we have implemented some custom styles in our style sheet and schema, so
> d:button shuld/ does match.
>
> As mentioned before, it is a custom style. It works for HTML and our
> Oxygen XML Editor

Re: [docbook-apps] PDF transformation: Why is the right border of my inline "box" missing when I transform to PDF. It works for HTML and Oxygen XML Editor.

[daniel . keyes]

Hi,

we tried to come up with a solution, but it didn´t work.
After all, we considered that it would be best to reset the entire schema 
and stylesheet back to "factory settings". Starting from scratch seemed to 
be a good idea to find the error (we created a backup). All that remained 
was Oxygens supplied version of Docbook 5.0.

We added our button style to the styelsheet:



http://www.w3.org/1999/XSL/Transform";
xmlns:fo="http://www.w3.org/1999/XSL/Format";
xmlns:d = "http://docbook.org/ns/docbook";
xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns:exsl="http://exslt.org/common";
exclude-result-prefixes="d"
version="1.0">




 
 







as well as a matching counterpart to the schema docbookxi.rng. Everything 
else remained the same.
However, the borders were still missing when transforming to PDF

After all, the bottom line is that:
- Except of the border, our custom style is working just fine. There is a 
link between stylesheet and schema
- Its not Adobe Reader (Zoom etc.)
- Its not our stylesheet or schema

So what´s the problem?
- Is it possible that Oxygen and its FO processor cannot handle our custom 
style? I know you told me that it´s propably not Saxxon, but is possible?
- How did you (@Simon) manage to successfully transform our style to PDF?
- Is is possible that Oxygen supplied an old or at least buggy version of 
DocBook 5.0?
- How is it possible that our styles works if we use fo:block instead? We 
have several "boxes" in our manuals and their all rendered correctly. 


Thanks for your help.



Greetings, 

Daniel Keyes




From:   DaveP 
To: docbook-apps@lists.oasis-open.org, 
Date:   12.10.2012 16:04
Subject:Re: [docbook-apps] PDF transformation: Why is the right 
border of my inline "box" missing when I transform to PDF. It works for 
HTML  and Oxygen XML Editor.



On 10/12/2012 01:37 PM, daniel.ke...@finaris.de wrote:
> Hi Simon,
>
> we have implemented some custom styles in our style sheet and schema, so
> d:button shuld/ does match.
>
> As mentioned before, it is a custom style. It works for HTML and our
> Oxygen XML Editor, but not for PDF.
>
> Is it possible that our FO processor, i.e. Saxxon, does not work?
>
>
> Daniel


No Daniel, very unlikely. Saxon is probably the most conformant
and well tested processor.




regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

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




===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] PDF transformation: Why is the right border of my inline "box" missing when I transform to PDF. It works for HTML and Oxygen XML Editor.

[daniel . keyes]

Hi Simon,

we have implemented some custom styles in our style sheet and schema, so 
d:button shuld/ does match.

As mentioned before, it is a custom style. It works for HTML and our 
Oxygen XML Editor, but not for PDF.

Is it possible that our FO processor, i.e. Saxxon, does not work?


Daniel






From:   "Dew, Simon" 
To: "docbook-apps@lists.oasis-open.org" 
, 
Date:   12.10.2012 12:43
Subject:Re: [docbook-apps] PDF transformation: Why is the right 
border of my inline "box" missing when I transform to PDF. It works for 
HTML  and Oxygen XML Editor.



Hi Daniel

A couple of suggestions. Have you looked at the .fo file to see if the 
borders are defined correctly? (I don't know Oxygen XML, but presumably 
there's an option to keep the .fo file when you transform to PDF.)

Secondly, I just looked at your customisation more closely.

 > 

Shouldn't that be d:guibutton? As it is, this template won't match 
anything, in which case the formatting that you're seeing must be coming 
from somewhere else. Is there another template in your custom layer 
which matches guibuttons?

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

simon@sbdinc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 10:47, daniel.ke...@finaris.de wrote:

> Hi Simon,
>
> your question isn´t stupid at all. Adobe Acrobat has some problems
> displaying thin borders or details. It really depends on the 
magnification.
>
> I tried your advice. The border is thicker, but the right border is
> still missing. I checked it with Adobe Acrobat ( zooming in and out), as
> well as simply printing a page.
>
>
> Greetings
>
> Daniel

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




===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] PDF transformation: Why is the right border of my inline "box" missing when I transform to PDF. It works for HTML and Oxygen XML Editor.

[daniel . keyes]

Hi Simon,

your question isn´t stupid at all. Adobe Acrobat has some problems 
displaying thin borders or details. It really depends on the 
magnification.

I tried your advice. The border is thicker, but the right border is still 
missing. I checked it with Adobe Acrobat ( zooming in and out), as well as 
simply printing a page.


Greetings

Daniel



From:   "Dew, Simon" 
To: "docbook-apps@lists.oasis-open.org" 
, 
Date:   12.10.2012 11:35
Subject:Re: [docbook-apps] PDF transformation: Why is the right 
border of my inline "box" missing when I transform to PDF. It works for 
HTML  and Oxygen XML Editor.



Hi Daniel

Sorry if this is a stupid question, but could the problem come from your 
PDF viewer?

Sometimes I find that Adobe Acrobat does not display all thin borders 
around a shaded area at 100% magnification. But they are there; you can 
see them if you increase the magnification or if you print the page.

If this is the case making the border a little thicker may help. Try 
border-width="1pt".

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

simon@sbdinc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 09:41, daniel.ke...@finaris.de wrote:

> Hello,
> my last request had some substantial mistakes. The problem still exists
> and a solution is not yet in sight. I´m afraid that I still need your 
help.
>
> We use Oxygen and DocBook to write and maintain our user manuals.
> Since these manuals describe various software applications, we often
> insert "buttons".
> Until recently, these buttons were inserted as screen shots, taken from
> the original application.
>
> In the course of time, we realized that the effort maintaining the
> amount of screens shots was to high, so we decided to add a new style to
> our XSL style sheet to imitate the original buttons. Basically what we
> did is to create a format for an inline "box" with a solid border.:
>
> 
>  font-family="Courier New" font-weight="bold" text-align="start"
> border-style="solid" border-width="thin" padding="1pt" >
> 
> 
> 
>
> The expected result was a solid box to indicate that its content was a
> "button":
>
> -
> | Button |
> -
>
> It worked out fine for the HTML output, as well as the editor View.
>
> However, transforming to PDF results in
>
> -
> | Button
> -
>
> The right border is missing, and we can´t figure out why.
> The strange thing is, it works when we replace the fo:inline by a
> fo:block. Nevertheless, this is not a solution, since the button is
> supposed to be an in-line element:
>
>
>   -
> Click on | Button | to 
>  -
>
> The FO transformer is Saxon 6.5.5. The entire documentation, including
> the transformation is done with Oxygen XML editor.
>
>
>
> Thanks for your help,
>
> Daniel 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
> Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
> Registered at Frankfurt/Main, HRB 52873
>
> Managing Directors:
> Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner 
Märkl
> ===

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




===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] PDF transformation: Why is the right border of my inline "box" missing when I transform to PDF. It works for HTML and Oxygen XML Editor.

[daniel . keyes]

Hello,
my last request had some substantial mistakes. The problem still exists 
and a solution is not yet in sight. I´m afraid that I still need your 
help.

We use Oxygen and DocBook to write and maintain our user manuals.
Since these manuals describe various software applications, we often 
insert "buttons".
Until recently, these buttons were inserted as screen shots, taken from 
the original application.

In the course of time, we realized that the effort maintaining the amount 
of screens shots was to high, so we decided to add a new style to our XSL 
style sheet to imitate the original buttons. Basically what we did is to 
create a format for an inline "box" with a solid border.:


 
 



The expected result was a solid box to indicate that its content was a 
"button":

- 
| Button |
-

It worked out fine for the HTML output, as well as the editor View.

However, transforming to PDF results in

- 
| Button 
-

The right border is missing, and we can´t figure out why. 
The strange thing is, it works when we replace the fo:inline by a 
fo:block. Nevertheless, this is not a solution, since the button is 
supposed to be an in-line element:


   - 
Click on | Button | to 
 -

The FO transformer is Saxon 6.5.5. The entire documentation, including the 
transformation is done with Oxygen XML editor.



Thanks for your help,

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] Wrong PDF output: Custom button-format is only displayed in the Oxygen Editor and HTML, but not in PDF. Frame is missing.

[daniel . keyes]

Thanks for the help, but it is still not working.

Maybe this will help:

Definition:


 
 



Editor: Oxygen 
FO- transformator: Saxon 6.5.5
Sketch(actual state):
- 
| Button
-

As you can see in the sketch above, the right border is missing. This 
problem only occurs in fo:inline, but not in fo:block.


Greetings,

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] Wrong PDF output: Custom button-format is only displayed in the Oxygen Editor and HTML, but not in PDF. Frame is missing.

[daniel . keyes]

Hello Aaron,

thanks for the help. The border is now solid, but the right margin is 
still missing. I tried finding the error by eliminating the other 
properties, but it didn't work.
Any other suggestions how I could fix the problem? 


Greetings,
Daniel Keyes




From:   Aaron DaMommio 
To: daniel.ke...@finaris.de, 
Cc: docbook-apps@lists.oasis-open.org
Date:   04.10.2012 15:59
Subject:Re: [docbook-apps] Wrong PDF output: Custom button-format 
is only displayed in the Oxygen Editor and HTML, but not in PDF. Frame is 
missing.
Sent by:aarondamom...@gmail.com



Looks like you're most of the way there, but I don't see any properties in 
 your fo:inline element to add a border. The rest look okay, and work fine 
in my environment.

In the line that starts:
 wrote:
> Hello,
>
> We are currently trying to make our user manual a bit more flexible
> regarding its maintenance. In this process, we replaced buttons that 
have
> previously been inserted as screenshots by a new format in Oxygen/ 
Docbook,
> basically imitating the original buttons. The new buttons have a 
light-grey
> background, use a purple font, have a purple frame and are based on a 
custom
> style in our Style sheet.
> Oxygen and the HTML transformation display the buttons correctly, but 
the
> the purple frame disappears when we transform the document to PDF.
>
>
> I have to admit that I´m not the master of code, but my responsible
> co-worker is currently out of office. The code in the XSL stylesheet for 
the
> PDF transformation looks like this:
>
> 
>  font-family="Courier New" font-weight="bold" text-align="start" >
> 
> 
> 
>
> I can´t see the frame, but it should be there. Did we forget something?
> Maybe this is a mistake simply resulting from the missing link between 
the
> various output forms (Editor vs. Html vs. PDF)
>
> Can anybody help us fixing the problem?
>
> Thanks.
>
>
> Greetings,
>
> Daniel 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
> Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
> Registered at Frankfurt/Main, HRB 52873
>
> Managing Directors:
> Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner 
Märkl
> ===



-- 
--
Aaron DaMommio: Husband, father, writer, juggler, and expert washer of 
dishes.
- My blog: http://aarondamommio.blogspot.com
- Need a juggler?  http://amazingaaronjuggler.blogspot.com/
===


===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] Wrong PDF output: Custom button-format is only displayed in the Oxygen Editor and HTML, but not in PDF. Frame is missing.

[daniel . keyes]

Hello,

We are currently trying to make our user manual a bit more flexible 
regarding its maintenance. In this process, we replaced buttons that have 
previously been inserted as screenshots by a new format in Oxygen/ 
Docbook, basically imitating the original buttons. The new buttons have a 
light-grey background, use a purple font, have a purple frame and are 
based on a custom style in our Style sheet.
Oxygen and the HTML transformation display the buttons correctly, but the 
the purple frame disappears when we transform the document to PDF.


I have to admit that I´m not the master of code, but my responsible 
co-worker is currently out of office. The code in the XSL stylesheet for 
the PDF transformation looks like this:


 
 



I can´t see the frame, but it should be there. Did we forget something? 
Maybe this is a mistake simply resulting from the missing link between the 
various output forms (Editor vs. Html vs. PDF)

Can anybody help us fixing the problem?

Thanks.


Greetings,

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] XML Table Structure, color and text direction with DocBook and Oxygen

[daniel . keyes]

Hello,,
we recently started transferring our user manuals from Word do DocBook.
We realized on our first pages that we had problems structuring our tables 
in the same manner as we did with word.



As an example:

Purpose|Document 
Purpose|Application
Purpose|Application 
Purpose|App1|  App2
|Content|Content
Purpose|App1|  App2
|Content|   Content

The purposes on the left side occupy the entire left side of the table 
without any disruptions, whereas the documents on the right side have a 
subdivision into additional purposes or application. As an e.g., one 
application is used for testing, the other one is used for reporting. But 
both are used for automatization. As a consequence

"Purpose|Application" turns into"Purpose|App1|  App2"
|Content| Content
 
Since most "purposes" consist of at least two cells that have been merged, 
we cannot simply leave cells empty. Additionally, there is not only one, 
but usually two ore more application fulfilling a certain purpose. Also, 
and this it what makes it pretty hard for us, "Purpose", "App", and 
Document have a grey background and are written bold.

As you can see there is pretty much to take care of:
- How can you structure a table similar as in word, e.g. by merging and 
subdividing/ splitting cells?
- How can you define a cells background color? Purpose and Document (at 
the top of the table) are the table headings and thus have a different 
format than the rest of the table.
- Is it possible to change a cells/ tables text direction, so that a table
? In some cases, the text direction of a text within a tables has to be 
changed ( e.g. 90°) 


Thanks for the help!





Yours sincerely,
Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] Preparing a stylesheet for HTML and PDF Output/ Stating the base.dir for HTML and PDF: How can you define the base.dir PDF, using the same relative path as used for HTML

[daniel . keyes]

Hey,



Currently we are finalizing our HTML stylesheet for DocBook. Since our 
documents are to be released as HTML and PDF and our documentation 
consists of about 20 different documents with more than 1000 pages total, 
we need to find a way to state a relative path in our stylesheet as the 
base.dir that will work out for both. We do not want to store all files, 
PDF and HTML, in the same folder. What we need is a nice and easy way to 
define where the output is to be stored.

For HTML we used .
This won´t work for PDF.

We had a similar problem with the role attribute regarding screenshots 
that had to be scaled differently according if we had a PDF or HTML output 
, but we managed to define "when to use what".

Is there any solution for our problem?









Greetings,

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] ANT HMTL Conversion with Oxygen: Shifting theList of Figures and List of Tables into an appendix in webhelp

[daniel . keyes]

Hi,

during our DB customisation we realised it would be best to shift the LoT and 
LoF to the appendix/ attachment in the back of our documents.

Therefore, we customized the template d:appendix from /xsl/fo :














 
  

This worked out pretty well, but now, since we are customizing the HTML/ XHTML 
output webhelp using ANT transformation to meet our expectations,  
d:appendix does not seem the  right place to make the adjustment. 

Does anyone have a clue how to shift the LoT and LoF to the "Back" or, 
precisely speaking, to a custom destination?

Greetings,

Daniel

===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] PDF Output with Oxygen and Custom XSL Stylesheet: One color is defined but when transforming to Pdf two colors appear

[daniel . keyes]

Hello,

a new problem occured whil generating PDFs with our custom XSL stylesheet.
For our user manual we have designed an example box, designed for specific code 
examples etc., It is basically a text box with a dark green border and a 
light-green background:












The problem is that its appearance varies, depending if inserted in a chapter 
or section ( in this case it was sect1).
The example box seems waymore darker if applied in a chapter compared to an 
example box in section 1, even though there is only one definition.

Any clues what the problem might be and how we can solve it?

Greetings,

Daniel


===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] Table of Content: Wrong space between Label/ number and title

[daniel . keyes]

Hello, thanks for the fast answer,

we solved the problem using a table for the TOC. All elements are in a 
corresponding column and therefore in one line as they should be.




Liebe Grüße
Daniel Keyes





From:
"Bob Stayton" 
To:
, 
Date:
31.01.2012 17:43
Subject:
Re: [docbook-apps] Table of Content: Wrong space between Label/ number and 
title



Hi Daniel,
It is hard to tell what is going wrong here without more information about 
how you customized it.  One thing you want to make sure of is that your 
customization layer for PDF output does not set indent="yes" in the 
xsl:output element.  It should be:
 

 
When indent is set to "yes", the processor inserts white space into the 
output, sometimes in locations where it is not desired.  I sometimes set 
it to "yes" when debugging FO output so I can more easily read it, but I 
always set it back to "no" when I'm done.
 
If that is not the problem, take a peek inside the FO output and see what 
exactly is appearing in the space between the number and the title.  That 
might give you a clue.
 
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
 
 
- Original Message - 
From: daniel.ke...@finaris.de 
To: docbook-apps@lists.oasis-open.org 
Sent: Tuesday, January 31, 2012 5:03 AM
Subject: [docbook-apps] Table of Content: Wrong space between Label/ 
number and title 

Hello, 

another problem occurred: 

The elements of the TOC have wrong spacings between the label/number and 
the title: 
Basically it looks like this (a bit exaggerated): 


1.1 XYZ 
1.2   XYZ 
1.3   XYZ 
1.4XYZ 

The only modification to the TOC is that now it is 1.1 instead of 1.1. . 
Have you seen this before and is there any solution to it? As said before, 
the TOC is pretty much still default and the changes occur on the same 
level. 

I hope i pointed out correctly what the problem is;) 

Thanks for the support! 





Liebe Grüße 
Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===


===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

Re: [docbook-apps] Oxygen XML Editor: Docbook XML to HTML using CSS

[daniel . keyes]

Hello Bob,

the error message you mentioned and the code you have stated is correct.

As an example:

chapter>sect1>title,
sect1>sect2>title,
sect2>sect3>title,
chapter>title
{
   font-size: 16pt;
   text-align: left;
   font-weight: bold;
   padding-bottom: 24pt;
}


As you can see we re-defined some default styles in our custom css 
stylesheet, the question is if we have to re-define them as well inside 
our custom xsl stylesheet for creating HTML in our custom style.
If so, do we need a css stylesheet at all or is it simply for the display 
in our Editor ( Oxygen).



Liebe Grüße
Daniel Keyes


F I N A R I S
Financial Software Partner GmbH
Sömmerringstr. 23
60322 Frankfurt

Fon: +49-(0)69-25498-16
Fax: +49-(0)69-25498-50
E-Mail: daniel.ke...@finaris.de
www: http://www.finaris.de
www: http://www.rapidrep.com



From:
"Bob Stayton" 
To:
, 
Date:
31.01.2012 17:55
Subject:
Re: [docbook-apps] Oxygen XML Editor: Docbook XML to HTML using CSS



Hi Daniel,
I'm not clear what the problem is here.  You say you are generating HTML 
output, but your example in red is not an HTML output element, and you 
show the element markup itself as being displayed in the browser in red. 
 
I suspect this is displaying an error-flagging feature of the DocBook XSL 
stylesheet.  When the stylesheet encounters an input element it does not 
recognize, it generates an error message along the lines of:
 
 Element body_text in namespace '' encountered in chapter, but no 
template matches.
 
and then outputs the element as escaped markup in red, with the intent of 
making it visible so it can be fixed:
 
<body_text>test</body_text>
 
Can you peek inside your HTML and see if that is what you are getting?  If 
so, then your customization layer needs to add a template with 
match="body_text" to process that element.
 
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
 
 
- Original Message - 
From: daniel.ke...@finaris.de 
To: docbook-apps@lists.oasis-open.org 
Sent: Tuesday, January 31, 2012 2:43 AM
Subject: [docbook-apps] Oxygen XML Editor: Docbook XML to HTML using CSS

Hello, 

currently we are having some problems customizing the respective XSL 
stylesheet for transforming our documents into Html ( and if it works also 
XHTML, webhelp etc.). 
The problems seems to be that Oxygen in a way is blocking our CSS 
stylesheet, since it is obviously recognized by the XSL stylesheet: 

 
 
&css; 
 
 

The code staed above is working out pretty fine, but still the result we 
we see is not what we configured. 


As a consequence, the ouput is not what it should be. 

Instead applying what was specified: 

body_text{ 
   font-family: Ariel; 
   font-size: 10pt; 
   line-height: 100%; 
   text-align: left; 
   padding-bottom: 12pt; 
} 

the result is test . It is red instead of black. 


Can anyone give me a hint what the problem is? Have I configured Oxygen 
incorrectly or is it the XSL Stylesheet. 

Thanks! 

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===


===
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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] Table of Content: Wrong space between Label/ number and title

[daniel . keyes]

Hello,

another problem occurred:

The elements of the TOC have wrong spacings between the label/number and 
the title:
Basically it looks like this (a bit exaggerated):


1.1 XYZ
1.2XYZ
1.3XYZ
1.4 XYZ

The only modification to the TOC is that now it is 1.1 instead of 1.1. . 
Have you seen this before and is there any solution to it? As said before, 
the TOC is pretty much still default and the changes occur on the same 
level.

I hope i pointed out correctly what the problem is;)

Thanks for the support!





Liebe Grüße
Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

[docbook-apps] Oxygen XML Editor: Docbook XML to HTML using CSS

[daniel . keyes]

Hello,

currently we are having some problems customizing the respective XSL 
stylesheet for transforming our documents into Html ( and if it works also 
XHTML, webhelp etc.).
The problems seems to be that Oxygen in a way is blocking our CSS 
stylesheet, since it is obviously recognized by the XSL stylesheet:



&css;



The code staed above is working out pretty fine, but still the result we 
we see is not what we configured.


As a consequence, the ouput is not what it should be.

Instead applying what was specified:

body_text{
   font-family: Ariel;
   font-size: 10pt;
   line-height: 100%;
   text-align: left;
   padding-bottom: 12pt;
}

the result is test . It is red instead of black.


Can anyone give me a hint what the problem is? Have I configured Oxygen 
incorrectly or is it the XSL Stylesheet.

Thanks! 

Daniel 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

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

[daniel . keyes]

Hey,

we finally managed to customize the PDF output. Some aspects still seem a 
bit mysterious, but we´ve got it. Thanks for the hint Bob!
Nevertheless, we are not yet running out of questions:

We are pretty much finished customizing our stylesheet, but still have a 
problem moving the list of figures and list of tables towards the 
appendix/ back of the document.. Our Documents are structured into:
- Frontpage
- Legal Notices
-Table of content
- Typographical conventions
- Preface
-Main body
-Appendix ( shortcuts, glossary etc.)
-List of figures
- List of tables

The problem is that we haven´t figured out yet how to shift the list of 
tables and list of figures from the front of the document ( between 
frontpage and legal notices ) to the back of the document ( after the 
appendix).
The Appendix including the tables have a Heading TOC formatting ( A XYZ, B 
XYZ etc.) 
We have used 


 
appendix  title,figure
article   title
book  toc,title
chapter   title
part  title
preface   title
reference title
sect1 title
sect2 title
sect3 title
sect4 title
sect5 title
section   title


to specify the location of the tables, but it didn´t work out. Can anyone 
give us a clue? Per default, the tables are rendered into the front part 
of the document.

Thanks!

Daniel



From:
Jason Zech 
To:
Bob Stayton , "docbook-apps@lists.oasis-open.org" 
, "daniel.ke...@finaris.de" 

Date:
24.01.2012 17:43
Subject:
RE: [docbook-apps] Customizing and creating a stylesheet for docbook using 
the XML Mind or Oxygen XML Editor



I’m also a fan of PrinceXML, which generates PDF from any structured 
content using fairly robust CSS styles. I transform from DocBook to HTML 
(using the stylesheets) and from HTML to PDF with Prince (CSS for styles). 
I’m very impressed with the results.
 
www.princexml.com
 
 
From: Bob Stayton [mailto:b...@sagehill.net] 
Sent: Tuesday, January 24, 2012 10:40 AM
To: docbook-apps@lists.oasis-open.org; daniel.ke...@finaris.de
Subject: Re: [docbook-apps] Customizing and creating a stylesheet for 
docbook using the XML Mind or Oxygen XML Editor
 
Hi Daniel,
CSS has progressed to the point where it can format printed output, and I 
know of at least one product that can use CSS to generate PDF output 
(Antenna House XSL Formatter http://www.antennahouse.com/product.htm). But 
most people use DocBook's XSL-FO output (fo/docbook.xsl) and an XSL-FO 
processor such as FOP to generate PDFs from DocBook content.
 
I believe someone pointed you to my online book DocBook XSL: The Complete 
Guide at http://www.sagehill.net/docbookxsl/index.html.  I believe it has 
the information you need to customize your PDF output.  This link will get 
you started with parameter setting:
 
http://www.sagehill.net/docbookxsl/PrintOutput.html
 
and this one with titlepage customization:
 
http://www.sagehill.net/docbookxsl/HTMLTitlePage.html
 
and this one will help with further customizations:
 
http://www.sagehill.net/docbookxsl/PrintCustomEx.html
 
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
 
 
- Original Message - 
From: daniel.ke...@finaris.de 
To: docbook-apps@lists.oasis-open.org 
Sent: Monday, January 23, 2012 4:38 AM
Subject: Re: [docbook-apps] Customizing and creating a stylesheet for 
docbook using the XML Mind or Oxygen XML Editor
 
Hello, 

sorry that it took so long, but I was quite busy. 
Thanks for all the response - it made things easier for us. 

The customization process is getting along pretty well, but we still have 
some questions regarding the PDF Output: 

As said before, we customized Docbook to match our requirements. We 
basically added a few elements to the schema and blocked those we didn’t 
want. The font size etc. is determined by an css style sheet. 

One problem is, that most of our new styles are not recognized if we 
output a document as a PDF. We already found the param.xml and 
pagesetup.xsl file, but were not sure if it is necessary to customize them 
as well. Did we go wrong using css instead of xsl as a stylesheet? Oxygen 
handles both, but it seems like only xls is supported for creating a PDF. 

Another problem that we have is, that we can´t really figure out how to 
influence the general page layout (header, footer, graphic on the front 
page etc.). Is there any tutorial or something? 

Finally, at least for now, we are wondering how to insert text boxes in 
line with the text, since in our current configuration text boxes are 
always inserted below the paragraph. 



Thanks for the help and sorry if some questions might seem unnecessary. 
I´m not one of the XML guys in the company, but rather one of those who 
write and translate. 

Greetings, 

Daniel 

From: 
daniel.ke...@finaris.de 
To: 
docbook-apps@lists.oasis-open.org 
Date: 
17.01.2012 09:44 
Subject: 
[docbook-apps] Customizing and creating a stylesheet for docbook using the 
XML Mind

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

[daniel . keyes]

Hello,

sorry that it took so long, but I was quite busy.
Thanks for all the response - it made things easier for us.

The customization process is getting along pretty well, but we still have 
some questions regarding the PDF Output:

As said before, we customized Docbook to match our requirements. We 
basically added a few elements to the schema and blocked those we didn’t 
want. The font size etc. is determined by an css style sheet.

One problem is, that most of our new styles are not recognized if we 
output a document as a PDF. We already found the param.xml and 
pagesetup.xsl file, but were not sure if it is necessary to customize them 
as well. Did we go wrong using css instead of xsl as a stylesheet? Oxygen 
handles both, but it seems like only xls is supported for creating a PDF.

Another problem that we have is, that we can´t really figure out how to 
influence the general page layout (header, footer, graphic on the front 
page etc.). Is there any tutorial or something?

Finally, at least for now, we are wondering how to insert text boxes in 
line with the text, since in our current configuration text boxes are 
always inserted below the paragraph.



Thanks for the help and sorry if some questions might seem unnecessary. 
I´m not one of the XML guys in the company, but rather one of those who 
write and translate.

Greetings,

Daniel


From:
daniel.ke...@finaris.de
To:
docbook-apps@lists.oasis-open.org
Date:
17.01.2012 09:44
Subject:
[docbook-apps] Customizing and creating a stylesheet for docbook using the 
XML Mind or Oxygen XML Editor



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 Walsh´s "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 don´t 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===

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

[daniel . keyes]

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 Walsh´s "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 don´t 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
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873

Managing Directors: 
Dipl. Inf. Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
===