- oXygen-user - www.oxygenxml.com

Fwd: Escaping markup, preserving contents in XProc
by Wendell Piez 22 Jan '14

22 Jan '14

Gerrit, thanks, this is useful info. It is oXygen v15.1. Sorry about that! The error isn't just with the results pane, however; it's also in the file written to disk. Hm. :-) Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ On Mon, Jan 20, 2014 at 5:58 PM, Imsieke, Gerrit, le-tex <gerrit.imsieke(a)le-tex.de> wrote: > Hi Wendell, > > this works for me both with p:escape-markup and without when I’m running > Calabash 1.0.13 and 1.0.16 standalone (Saxon 9.4). The version that’s > bundled with oXygen 15.1 seems to be 1.0.13. I don’t know what’s bundled > with oXygen 15.2. Wait – did you say 15.2? With 15.1, I get the same > results as you, i.e., a mangled bullet for p:escape-markup. It seems as > if the assumed encoding for the results window is incorrect in oXygen. > > Gerrit > > On 20.01.2014 21:25, Wendell Piez wrote: >> Hi, >> >> Don't ask why I'm doing this; I'd rather not say. :-) >> >> Running this XProc: >> >> <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> >> >> <p:serialization port="result" method="text"/> >> >> <p:input port="source"> >> <p:inline> >> <doc>Hello bullet: •</doc> >> </p:inline> >> </p:input> >> >> <p:output port="result"/> >> >> <p:wrap name="wrap" match="/" wrapper="wrapper"/> >> >> <p:escape-markup name="escape-wrapped-contents"/> >> >> </p:declare-step> >> >> I am getting: >> >> <doc>Hello bullet: â€¢</doc> >> >> As you can imagine, I'd like to see an honest bullet (U-2022) in the results. >> >> By commenting out the 'escape-markup' step I can see my bullet makes >> it through to that point. >> >> I am using Calabash inside oXygen 15.2. >> >> What am I doing wrong? Any hints? >> >> Cheers, Wendell >> >> Wendell Piez | http://www.wendellpiez.com >> XML | XSLT | electronic publishing >> Eat Your Vegetables >> _____oo_________o_o___ooooo____ooooooo_^ >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> > > -- > Gerrit Imsieke > Geschäftsführer / Managing Director > le-tex publishing services GmbH > Weissenfelser Str. 84, 04229 Leipzig, Germany > Phone +49 341 355356 110, Fax +49 341 355356 510 > gerrit.imsieke(a)le-tex.de, http://www.le-tex.de > > Registergericht / Commercial Register: Amtsgericht Leipzig > Registernummer / Registration Number: HRB 24930 > > Geschäftsführer: Gerrit Imsieke, Svea Jelonek, > Thomas Schmidt, Dr. Reinhard Vöckler > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Re: [oXygen-user] High contrast accessiblity
by Henry Gorbsky 21 Jan '14

21 Jan '14

Hi Adrian, I appreciate your quick response. I will work on configuring the editor in the coming days to get the right color combinations, but at least now I know how to do it. Thanks again for all your help! *regards* Hank D. Gorbsky Internet e-mail: gorbsky(a)us.ibm.com From: oxygen-user-request(a)oxygenxml.com To: oxygen-user(a)oxygenxml.com, Date: 01/21/2014 01:00 PM Subject: oXygen-user Digest, Vol 39, Issue 12 Sent by: oxygen-user-bounces(a)oxygenxml.com Send oXygen-user mailing list submissions to oxygen-user(a)oxygenxml.com To subscribe or unsubscribe via the World Wide Web, visit http://www.oxygenxml.com/mailman/listinfo/oxygen-user or, via email, send a message with subject or body 'help' to oxygen-user-request(a)oxygenxml.com You can reach the person managing the list at oxygen-user-owner(a)oxygenxml.com When replying, please edit your Subject line so it is more specific than "Re: Contents of oXygen-user digest..." Today's Topics: 1. Escaping markup, preserving contents in XProc (Wendell Piez) 2. Re: Escaping markup, preserving contents in XProc (Imsieke, Gerrit, le-tex) 3. Fwd: Escaping markup, preserving contents in XProc (Wendell Piez) 4. High contrast accessiblity (Henry Gorbsky) 5. Re: High contrast accessiblity (Oxygen XML Editor Support) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Jan 2014 15:25:36 -0500 From: Wendell Piez <wapiez(a)wendellpiez.com> Subject: [oXygen-user] Escaping markup, preserving contents in XProc To: "oxygen-user(a)oxygenxml.com" <oxygen-user(a)oxygenxml.com> Message-ID: <CAAO_-xycAT=_sZhdK-qgqPg0FweqbX0xPuE770LRZ=Q +56O2ow(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi, Don't ask why I'm doing this; I'd rather not say. :-) Running this XProc: <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> <p:serialization port="result" method="text"/> <p:input port="source"> <p:inline> <doc>Hello bullet: •</doc> </p:inline> </p:input> <p:output port="result"/> <p:wrap name="wrap" match="/" wrapper="wrapper"/> <p:escape-markup name="escape-wrapped-contents"/> </p:declare-step> I am getting: <doc>Hello bullet: ???</doc> As you can imagine, I'd like to see an honest bullet (U-2022) in the results. By commenting out the 'escape-markup' step I can see my bullet makes it through to that point. I am using Calabash inside oXygen 15.2. What am I doing wrong? Any hints? Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ ------------------------------ Message: 2 Date: Mon, 20 Jan 2014 23:58:54 +0100 From: "Imsieke, Gerrit, le-tex" <gerrit.imsieke(a)le-tex.de> Subject: Re: [oXygen-user] Escaping markup, preserving contents in XProc To: oxygen-user(a)oxygenxml.com Message-ID: <52DDAA2E.1000002(a)le-tex.de> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Wendell, this works for me both with p:escape-markup and without when I?m running Calabash 1.0.13 and 1.0.16 standalone (Saxon 9.4). The version that?s bundled with oXygen 15.1 seems to be 1.0.13. I don?t know what?s bundled with oXygen 15.2. Wait ? did you say 15.2? With 15.1, I get the same results as you, i.e., a mangled bullet for p:escape-markup. It seems as if the assumed encoding for the results window is incorrect in oXygen. Gerrit On 20.01.2014 21:25, Wendell Piez wrote: > Hi, > > Don't ask why I'm doing this; I'd rather not say. :-) > > Running this XProc: > > <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> > > <p:serialization port="result" method="text"/> > > <p:input port="source"> > <p:inline> > <doc>Hello bullet: •</doc> > </p:inline> > </p:input> > > <p:output port="result"/> > > <p:wrap name="wrap" match="/" wrapper="wrapper"/> > > <p:escape-markup name="escape-wrapped-contents"/> > > </p:declare-step> > > I am getting: > > <doc>Hello bullet: ???</doc> > > As you can imagine, I'd like to see an honest bullet (U-2022) in the results. > > By commenting out the 'escape-markup' step I can see my bullet makes > it through to that point. > > I am using Calabash inside oXygen 15.2. > > What am I doing wrong? Any hints? > > Cheers, Wendell > > Wendell Piez | http://www.wendellpiez.com > XML | XSLT | electronic publishing > Eat Your Vegetables > _____oo_________o_o___ooooo____ooooooo_^ > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > -- Gerrit Imsieke Gesch?ftsf?hrer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke(a)le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Gesch?ftsf?hrer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard V?ckler ------------------------------ Message: 3 Date: Mon, 20 Jan 2014 21:53:03 -0500 From: Wendell Piez <wapiez(a)wendellpiez.com> Subject: [oXygen-user] Fwd: Escaping markup, preserving contents in XProc To: "oxygen-user(a)oxygenxml.com" <oxygen-user(a)oxygenxml.com> Message-ID: <CAAO_-xxdxs6X-P0PqUaiimoRX+P +CyRe8E4R15D=5Rk5n8ACBA(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Gerrit, thanks, this is useful info. It is oXygen v15.1. Sorry about that! The error isn't just with the results pane, however; it's also in the file written to disk. Hm. :-) Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ On Mon, Jan 20, 2014 at 5:58 PM, Imsieke, Gerrit, le-tex <gerrit.imsieke(a)le-tex.de> wrote: > Hi Wendell, > > this works for me both with p:escape-markup and without when I?m running > Calabash 1.0.13 and 1.0.16 standalone (Saxon 9.4). The version that?s > bundled with oXygen 15.1 seems to be 1.0.13. I don?t know what?s bundled > with oXygen 15.2. Wait ? did you say 15.2? With 15.1, I get the same > results as you, i.e., a mangled bullet for p:escape-markup. It seems as > if the assumed encoding for the results window is incorrect in oXygen. > > Gerrit > > On 20.01.2014 21:25, Wendell Piez wrote: >> Hi, >> >> Don't ask why I'm doing this; I'd rather not say. :-) >> >> Running this XProc: >> >> <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> >> >> <p:serialization port="result" method="text"/> >> >> <p:input port="source"> >> <p:inline> >> <doc>Hello bullet: •</doc> >> </p:inline> >> </p:input> >> >> <p:output port="result"/> >> >> <p:wrap name="wrap" match="/" wrapper="wrapper"/> >> >> <p:escape-markup name="escape-wrapped-contents"/> >> >> </p:declare-step> >> >> I am getting: >> >> <doc>Hello bullet: ???</doc> >> >> As you can imagine, I'd like to see an honest bullet (U-2022) in the results. >> >> By commenting out the 'escape-markup' step I can see my bullet makes >> it through to that point. >> >> I am using Calabash inside oXygen 15.2. >> >> What am I doing wrong? Any hints? >> >> Cheers, Wendell >> >> Wendell Piez | http://www.wendellpiez.com >> XML | XSLT | electronic publishing >> Eat Your Vegetables >> _____oo_________o_o___ooooo____ooooooo_^ >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> > > -- > Gerrit Imsieke > Gesch?ftsf?hrer / Managing Director > le-tex publishing services GmbH > Weissenfelser Str. 84, 04229 Leipzig, Germany > Phone +49 341 355356 110, Fax +49 341 355356 510 > gerrit.imsieke(a)le-tex.de, http://www.le-tex.de > > Registergericht / Commercial Register: Amtsgericht Leipzig > Registernummer / Registration Number: HRB 24930 > > Gesch?ftsf?hrer: Gerrit Imsieke, Svea Jelonek, > Thomas Schmidt, Dr. Reinhard V?ckler > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user ------------------------------ Message: 4 Date: Tue, 21 Jan 2014 09:23:22 -0500 From: Henry Gorbsky <gorbsky(a)us.ibm.com> Subject: [oXygen-user] High contrast accessiblity To: oxygen-user(a)oxygenxml.com Message-ID: <OF01CB622C.5D6C9FA8-ON85257C67.004E30D8-85257C67.004F0B70(a)us.ibm.com> Content-Type: text/plain; charset="us-ascii" Hello, I have a question regarding the accessibility features of the editor. I am a low vision user and require high contrast (white-on-black) setting. I am on Windows 7 with the global high contrast mode setting activated. However, when I load the Oxygen editor, the document edit window does not display with high-contrast. The document window shows typical black font on white background, which is not accessible. I've gone into settings to try to change background/font colors, hoping to achieve a high contrast effect to no avail. Any thoughts on why this is occurring and suggestions on how to remedy? Thanks. *regards* Hank D. Gorbsky Internet e-mail: gorbsky(a)us.ibm.com

1 0

High contrast accessiblity
by Henry Gorbsky 21 Jan '14

21 Jan '14

Hello, I have a question regarding the accessibility features of the editor. I am a low vision user and require high contrast (white-on-black) setting. I am on Windows 7 with the global high contrast mode setting activated. However, when I load the Oxygen editor, the document edit window does not display with high-contrast. The document window shows typical black font on white background, which is not accessible. I've gone into settings to try to change background/font colors, hoping to achieve a high contrast effect to no avail. Any thoughts on why this is occurring and suggestions on how to remedy? Thanks. *regards* Hank D. Gorbsky Internet e-mail: gorbsky(a)us.ibm.com

2 1

Escaping markup, preserving contents in XProc
by Wendell Piez 20 Jan '14

20 Jan '14

Hi, Don't ask why I'm doing this; I'd rather not say. :-) Running this XProc: <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> <p:serialization port="result" method="text"/> <p:input port="source"> <p:inline> <doc>Hello bullet: •</doc> </p:inline> </p:input> <p:output port="result"/> <p:wrap name="wrap" match="/" wrapper="wrapper"/> <p:escape-markup name="escape-wrapped-contents"/> </p:declare-step> I am getting: <doc>Hello bullet: â€¢</doc> As you can imagine, I'd like to see an honest bullet (U-2022) in the results. By commenting out the 'escape-markup' step I can see my bullet makes it through to that point. I am using Calabash inside oXygen 15.2. What am I doing wrong? Any hints? Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 1

Adding a Google Analytics code for our xHTML output
by Scott Barney 20 Jan '14

20 Jan '14

We are using DITA and DITA-OT with the oXygen WebHelp plug-in to create our online documentation (with a customized DTD). We would like to use Google Analytics to track our Web page usage. According to my webmistress, we will need to include our Google Analytics tracking code (which looks something like UA-99999999-9) in each page output. The code that we've added for our other Web pages appears similar to this (account number has been modified in this example): <script type="text/javascript" async="" src= <http://www.google-analytics.com/ga.js> "http://www.google-analytics.com/ga.js"> <script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-29999999-2']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script> Is there an option in the WebHelp plug-in that would allow us to simply add this type of code to the <head> element? Or could it possibly be as simple as adding proper metadata to our DITA files? Thanks, Scott Description: Four Js - The Power of Simplicity Scott Barney - Content Manager / Information Architect / Technical Writer / Instructional Designer Description: Telephone: +1 972 786 0926 Description: Mobile: +1 415 336 7748 Description: Fax: N/A Description: Email: <mailto:sbarney@4js.com> sbarney(a)4js.com Description: Skype: scott.barney Description: Web: <http://www.4js.com/> http://www.4js.com Four Js Development Tools, Inc. 1968 15th St, San Francisco CA 94114 , USA <http://www.linkedin.com/groups/Genero-Community-4105129> Description: LinkedIn <http://www.youtube.com/user/FourJsGenero> Description: YouTube

2 1

How to match across multiple lines using regex?
by Eliot Kimber 17 Jan '14

17 Jan '14

I’m trying to a regular expression search and replace for things like this: doc: text text next line next line</a:documentation> What I can’t figure out is how to do this multi-line regular expression match. If use “dot matches all” then my match is not limited to just what’s shown but everything between the first doc: and the last </a:documentation>. If do e.g. “doc:(.)</a:documentation>” then it matches cases where it all happens to be on one line. Is this possible? What bit of regex fu am I missing? Thanks, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

4 6

Ant syntax highlighting?
by Tom Cleghorn 17 Jan '14

17 Jan '14

Hi, I'd very much like to tweak Oxygen's Ant syntax highlighting - specifically, I'd like to be able to highlight variables in attribute values, which are currently displayed as red text from start to finish. It seems like this ought to be relatively easy to specify (i.e. anything between "${" and "}" is styled differently), but is this possible with the framework functionality, or in any other way at all? Thanks!

2 1

Line breaks in DITA source
by KAATMAN Matthew 16 Jan '14

16 Jan '14

Hey Guys, How does Oxygen decide where to add line breaks in the source? I've got a strange situation where I'll have some content like: (Note the literal space between </i> and <tm) <i>Stenotrophomonas maltophilia</i> <tm tmtype="tm"><tm tmtype="reg" translate="no">ATCC</tm> 17666</tm> Oxygen often formats it like: (Note the lack of a space after </i>) <i>Stenotrophomonas maltophilia</i> <tab><tab><tab><tab><tm tmtype="tm"><tm tmtype="reg" translate="no">ATCC</tm> 17666</tm> So far so good. Rendering this to PDF produces a space between the </i> and <tm. However, when we send these files to our translation vendor (they're using Trados), the content comes back as: (Note lack of space) <i>Stenotrophomonas maltophilia</i><tm tmtype="tm"><tm tmtype="reg" translate="no">ATCC</tm> 17666</tm> One solution (and maybe the best one!) would be for the translation vendor to preserve whitespace. However, I was curious if there was a way to set rules that define how Oxygen saves the file. If so, another thing I'd probably do is never break a tag across lines. I see this fairly often too. Which 99.99% of the time is no problem, but we've run into some issues due to complexity we've introduced. <uicontrol >Test</uicontrol> 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

New pricing for XSLT, XSL-FO, UBL and code list classes in Australia
by G. Ken Holman 10 Jan '14

10 Jan '14

For those who were considering my upcoming training delivery in Melbourne Australia, the web site had incorrect Euro pricing and has been repaired with the more affordable Australian dollar pricing. Please forgive my oversight and I hope you will reconsider your attendance based on the corrected pricing. Please let me know off list if you have any questions. . . . . . . . Ken cc: XML-Dev, XML-L, XML-Doc, Oxygen User list, Mulberry XSL, W3C-XSL-FO, Antenna House list, RenderX list, UBL-Dev, CLR-Dev (apologies for duplicates to those who subscribe to multiple lists) Four in-depth, intensive, hands-on XML classes, separately subscribed: XSLT/XPath, XSL-FO, UBL and code lists May 5, 2014 (week 19) to May 16, 2014 (Week 20) Melbourne, Australia Hosted by Absolute Data Group http://www.absolutedata.com/ This event requires registration: http://www.CraneSoftwrights.com/forms/register.php Practical Transformation Using XSLT and XPath (5 days) May 5-9, 2014 - covering every element, every attribute and every function of XSLT and XPath versions 1.0 and 2.0, used in creating new transformations of existing structured information Syllabus: http://www.CraneSoftwrights.com/training/ptux/ptuxsyl.htm Event: https://plus.google.com/events/cs2ljt4u5l3emnll0a6441fbtvs Practical Formatting Using XSL-FO (3 days) May 12-14, 2014 - covering every formatting object of XSL-FO 1.0 and 1.1; used in creating printed renditions and PDF files from XML documents Syllabus: http://www.CraneSoftwrights.com/training/pfux/pfuxsyl.htm Event: https://plus.google.com/events/cbtnjbhpogebsdlubanefof96vk Practical Universal Business Language Deployment (1 day version) May 15, 2014 - for understanding the artefacts published for OASIS UBL 2.1 and practice in the application of the models and XSD schema files Syllabus: http://www.CraneSoftwrights.com/training/publd/publdsyl.htm Event: https://plus.google.com/events/cvj4o6uqu88mjmf91g18gauuukc Practical Code List Implementation (1 day) May 16, 2014 - for business vocabularies and any vocabulary design that requires flexible implementation of code lists without changing schema files (this will be of interest to UBL users as this technique is used in the UBL committee for the definition and application of code lists) Syllabus: http://www.CraneSoftwrights.com/training/pcli/pclisyl.htm Event: https://plus.google.com/events/c4mi6v1mk4dlcjvk0ns9h4np070 Instructor: G. Ken Holman http://www.CraneSoftwrights.com/bio/gkholman.htm Event host: Absolute Data Group http://www.absolutedata.com/ Early-bird date for registration discounts: April 14, 2014 Labels: code lists, OASIS UBL, Universal Business Language, XML, XSL, XSL-FO, XSLT -- Public XSLT, XSL-FO, UBL & code list classes: Melbourne, AU May 2014 | Contact us for world-wide XML consulting and instructor-led training | Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm | Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ | G. Ken Holman mailto:gkholman@CraneSoftwrights.com | Google+ profile: http://plus.google.com/+GKenHolman-Crane/about | Legal business disclaimers: http://www.CraneSoftwrights.com/legal |

1 0

Preventing oXygen XML Author to start a new "instance"
by Yves Barbion 09 Jan '14

09 Jan '14

Hi group When I have oXygen XML Author open and double-click an xml file in Windows Explorer, a new "instance" of oXygen XML Author is started in which this file is opened. Isn't there a way to prevent this, so that the xml file is opened in the instance which is currently running? Thanks -- Yves Barbion www.scripto.nu

2 2