- oXygen-user - www.oxygenxml.com

Working with Subject Scheme Maps as Nested Lists
by Eliot Kimber 31 Jan '14

31 Jan '14

I'm experimenting with using subject scheme maps to capture outlines of subjects as part of some training planning I'm doing. To facilitate this I've whipped up a little CSS style sheet that renders the subject definitions as a bulleted list items. However, I don't get any collapse/expand handles in the edit view--I would really like to be able to expand and collapse the list in the main editor window (rather than using the outline view). Is there a way to do this through the CSS? Here is the CSS as I've got it so far: /* CSS to show a subject scheme map as nested lists*/ subjectdef { list-style-type: disc; display: block; } subjectdef > topicmeta { display: list-item; margin-left: 12pt; margin-top: 12pt; } subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 24pt; } subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 36pt; } subjectdef > subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 48pt; } subjectdef > subjectdef > subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 60pt; } shortdesc { display: block; margin-top: 1em; margin-left: 12pt; } /* End of CSS */ Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com <http://contrext.com/> -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

3 6

Fwd: Toggling @keyref with Tags Display Mode
by Wendell Piez 28 Jan '14

28 Jan '14

I'm always forgetting to reply to list ... ---------- Forwarded message ---------- From: Wendell Piez <wapiez(a)wendellpiez.com> Date: Tue, Jan 28, 2014 at 9:53 AM Subject: Re: [oXygen-user] Toggling @keyref with Tags Display Mode To: Roger Sheen <infotexture(a)gmail.com> Hi Roger, To bind this behavior to "No Tags Mode" raises all kinds of questions regarding exactly which behaviors are toggled when. Keep in mind that Tags Display functionality applies to all document types, not just DITA. Much simpler, and cleaner layering, is to deploy another CSS stylesheet alongside the generic one, with whatever customizations you want. oXygen lets you have as many CSS displays to choose from as you wish to configure. Users can switch between them with a pull-down menu. You can do this yourself. Your new CSS can import the old one and simply override where necessary. I can imagine other solutions, such as designating an attribute flag in the document that toggles display behavior. Using oXygen's forms widgetry, one could present this as a radio button widget (for example) and let the user toggle from inside the document. But this would mean both extending DITA to support it, and arguably crossing an architectural line, since the document is now being asked to carry display semantics specifically for the editing environment. And this raises questions for document interchange, etc. etc. I'm sure there are other ideas I haven't thought of. :-) Cheers, Wendell On Tue, Jan 28, 2014 at 7:33 AM, Roger Sheen <infotexture(a)gmail.com> wrote: > While working on Author mode CSS customizations today, I was looking for > a way to remove the @keyref values that are automatically displayed > before *keyword* elements when editing DITA topics. > > The content in this project makes heavy use of keywords, and many > authors find the extra text distracting. > > I found the relevant rule on line 1053 of the default `topic.css` file > and added an override in my custom CSS to remove `"[" attr(keyref) "]"` > from the inserted content (but still display the link). > > This solution works, but I was thinking it might be better if this could > be toggled along with the *Tags display mode*. When set to *No Tags*, it > would be nice if these values were hidden. I would expect them to be > displayed in other modes that progressively disclose additional visual > cues. > > Any thoughts? > > Regards, > > Roger > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 1

Toggling @keyref with Tags Display Mode
by Roger Sheen 28 Jan '14

28 Jan '14

While working on Author mode CSS customizations today, I was looking for a way to remove the @keyref values that are automatically displayed before *keyword* elements when editing DITA topics. The content in this project makes heavy use of keywords, and many authors find the extra text distracting. I found the relevant rule on line 1053 of the default `topic.css` file and added an override in my custom CSS to remove `"[" attr(keyref) "]"` from the inserted content (but still display the link). This solution works, but I was thinking it might be better if this could be toggled along with the *Tags display mode*. When set to *No Tags*, it would be nice if these values were hidden. I would expect them to be displayed in other modes that progressively disclose additional visual cues. Any thoughts? Regards, Roger

1 0

dita.temp.dir modified in Author 15.1
by Echlin, Robert 23 Jan '14

23 Jan '14

Hi I am using DITA-OT 1.5.4 I am using the dita2eclipsemap functionality. Some things use dita.temp.dir, which is set on the command line by oXygen. It is not set to the value I set in the dialog: - (my map dir)/temp, but rather to: - (my map dir)/temp/oxygen_dita_temp Can you explain why Author 15 adds the extra folder name to the end of the "Temporary Files Directory" value that I set in the "Edit DITA Scenario" dialog, in the "Output" tab? This is unexpected behavior for me. Is there a setting where I can turn off this behavior? All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River +1.613.270.5796 | Skype: rob.echlin.wr

2 1

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