October 2013 - oXygen-user - www.oxygenxml.com

Improving usability of bundled FOP
by Jirka Kosek 11 Oct '13

11 Oct '13

Hi, quality of FOP improved over the past years and in many situations it's viable option to commercial engines like XEP and Antenna House. However oXygen by default provides FOP with its default configuration which is not that useful for real work. I see two main issues: 1) Only standard 14 fonts are supported and these fonts are not containing glyphs used outside Western Europe scripts. With the recent versions of FOP solution is easy. By using configuration file with <auto-detect/> directive inside <fonts> element all locally installed fonts are available to FOP. Users are not forced to register fonts manually and generate metrics as in a past. 2) FOP doesn't contain hyphenation patterns. They can be downloaded from http://sourceforge.net/projects/offo/files/latest/download?source=dlp (file with patterns is fop-hyph.jar and it's sufficient to put it on a classpath). I think it would be great if future releases of oXygen can contain this additional library with hyphenation patterns and enable fonts by providing custom configuration file out of the box. Thanks, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

3 3

Oxygen metrics report
by KAATMAN Matthew 08 Oct '13

08 Oct '13

Does the Oxygen metrics report only count conref in the reuse section or also conkeyref? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 1

Linking uicontrol with a collection topic
by KAATMAN Matthew 04 Oct '13

04 Oct '13

I have a topic with a collection of uicontrol elements. I generate this topic from a java properties file for software strings using a script I wrote. Is there any way for me to force the writers to conkeyref to this file anytime they add a uicontrol? Or even if Oxygen could push them towards using conkeyref instead of entering text directly, that might be sufficient to remind them of what they need to do. I can't think of a practical way to make this happen (and maybe it's even too rigid to be practical) but I thought I'd ask and see if anyone had ideas. Thanks, Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 2