Michael B. wrote:
 >
 > I'm currently evaluating XXE on an Ubuntu system and I'm having some
 > difficulty.  Our intention is to purchase 5-10 professional licenses,
 > but before I can be authorized to make that purchase I need to prove to
 > the company that the software serves the intended purpose.  I'm in day
 > two of the evaluation and my worry is that I'm not going to be able to
 > produce anything before it runs out.

No problem. Get you another evaluation key ( 
http://www.xmlmind.com/xmleditor/evaluate.html ) and install it in your 
running copy.



 >
 > I'm trying to setup a standardized company branded stylesheet for
 > DocBook.  This needs to include customized front page, headers/footers
 > and fonts.  My main focus at the moment is fonts (the rest is yet to
 > come).  I've been researching a number of different approaches to
 > getting "Maven Pro" and Tahoma to work with the xxe fop addon.

Though apparently not the same problem, the approach described in this FAQ:

---
When I convert documents written in Russian (or Polish or Czech or any 
non-western language) to PDF, almost all characters are replaced by the 
"#" character. Is there a workaround for this problem?
---
http://www.xmlmind.com/xmleditor/faq.html#custom_pdf_fonts

fully applies to your main problem, that is, instructing FOP to map 
"Maven Pro" and Tahoma to the serif and sans-serif generic font families.

Please note that only TTF fonts --not OpenType fonts-- are supported by 
the above facility.



 >  All leads inevitably point to me needing to edit a config file 
somewhere.

Not necessarily. See below.



 > I cannot find any such file on my system and I'm afraid if I just write
 > one from scratch it may not work with the fop addon.
 >
 > Are there any DECENT tutorials/links/guides that specifically describe
 > what I should be doing?

You'll not find such tutorial because creating  branded documentation is 
*not* the problem solved by XMLmind XML Editor. (Otherwise, we would 
have called our product "XMLmind Single Source Publishing Studio".)

More information in this FAQ:
---
How do I customize the HTML, PDF, RTF, etc, generated using the "Convert 
Document" menu?
---
http://www.xmlmind.com/xmleditor/faq.html#custom_deliverables



This being said, XMLmind XML Editor has a number of useful features 
allowing to customize the deliverables (to a certain extent) and this, 
without having to tweak cryptic configuration files by hand. Namely:

* Menu item Options|Customize Configuration|Customize Document 
Conversion Stylesheets

See 
http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.part.ConversionStylesheetsEditor.html

* Menu item Options|Customize Configuration|Change Document Conversion 
Parameters

See 
http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.part.ConversionParametersEditor.html




 > Aside from proving xxe can produce branded
 > documentation, I also need to convince a bunch of engineers with no
 > technical writing experience that this is better than Word - so
 > usability is key.
 >
 > These are the links I have already tried
 > http://sagehill.net/docbookxsl/AddFont.html
 >
 > http://xmlgraphics.apache.org/fop/0.95/fonts.html
 >
 > http://www.xmlmind.com/xmleditor/addons_doc.html
 >
 
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to