August 2015 - oXygen-user - www.oxygenxml.com

Multi-row tabs?
by Jostein Austvik Jacobsen 02 Oct '17

02 Oct '17

I often have a lot of XML-files open simultaneously. Is it possible to configure multiple rows of tabs? Something similar to this: http://winaero.com/blog/wp-content/uploads/2013/10/Firefox-with-multi-row-t… Jostein

5 9

Re: [oXygen-user] Pretty Print <lb/> in Oxygen
by Syd Bauman 12 Jan '16

12 Jan '16

A few hours ago Ute Recker-Hamm posted a wonderful question to TEI-L, the main list for the Text Encoding Initiative.[1] She basically asked "what do y'all do to get your physical lines, as encoded with the empty TEI <lb> element, to line up nicely in oXygen?". I remember asking a similar question a few years ago, and vaguely recall being told that manipulating the options under "Preferences > Editor / Format / XML" (in particular the "Preserve space" and "Default space" lists) should get format-and-indent to do the trick. However, I recall that I never got it working to my satisfaction, and when I look through the archives of this list now, I can't find the answer I recall. So what is "it" that I want format-and-indent to do? When given a text that looks like this: view A ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. I'd like it to end up formatted as it is now -- with each <lb> starting a new line. If the desired line length were long enough, it wouldn't be changed at all. If the desired line length were shorter, it might look like this: view B ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. What I *don't* want is for format-and-indent to make it look like this: view C ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. In fact, if I had my druthers, an input document that looked like view C would come out of the processing looking like view A or B. Note ---- [1] Those of you who are members of a TEI list at Brown can find it at https://listserv.brown.edu/?A2=ind1410&L=tei-l&F=&S=&P=64155. I have not re-produced it here because I did not get the original poster's permission to do so. (Not that I think it is illegal or immoral to re-post without such permission, only that it's rude.)

7 9

Not indent elements with 'linefeed-treatment="preserve"'?
by Tony Graham 12 Jan '16

12 Jan '16

Is there a way that a framework can make oXygen not reindent elements that have 'linefeed-treatment="preserve"'? http://www.oxygenxml.com/doc/versions/17.0/ug-editor/#topics/preferences-ed… says that elements can be added to the 'Preserve space' list, but "*[@linefeed-treatment='preserve']" isn't a 'simple node test' and seems to be being silently ignored. Even if it did work, it can't be set by the 'focheck' framework. (Separately, the ability to edit an item in the list, rather than having to make a new item based on an existing item then deleting the old item, seems to me to be useful.) http://www.oxygenxml.com/doc/versions/17.0/ug-editor/#topics/format-and-ind… says that it can be done with CSS using 'white-space: pre', but *[linefeed-treatment=preserve] { white-space: pre; } is having no effect on Text mode 'Format and Indent Element' results. (Separately again, is there a key combination to insert a line break that doesn't also insert indenting white-space?) Regards, Tony Graham. -- Senior Architect XML Division Antenna House, Inc. ---- Skerries, Ireland tgraham(a)antenna.co.jp

3 2

Odd webhelp with feedback error message
by Jim Henderson 01 Sep '15

01 Sep '15

I'm receiving the following e-mail from a testing server that I'm using feedback on: [73.53.13.170] - 2015-08-26 10:27:46: Unknown error type: [8] Undefined property: RecordSet::$m_CurrentRow on line 200 in file /var/www/html/PingID-API/oxygen-webhelp/resources/php/classes/db/RecordSet.php , PHP 5.4.16 (Linux) This happens when I submit a comment in the comment system. Doesn't seem to matter if I'm authenticated or not. I've tried this on CentOS 7.0 and SUSE Linux Enterprise 11 SP3, and both of them are generating this message for some reason. The output was generated with Oxygen 17. I've got other webhelp with feedback that works OK (in fact, I can use the same output set on another server and it works just fine). I've got mysql installed and the php mysql extension is present as well. I've set up the database fine, and I can see the comments in the UI, but the e-mails being sent only contain this error. I'm not even sure where to start to troubleshoot this - anyone have any ideas? Thanks, Jim -- [image: Ping Identity logo] <https://www.pingidentity.com/> Jim Henderson Technical Writer @ jhenderson(a)pingidentity.com [image: phone] +1 720.390.3443 Connect with us… [image: twitter logo] <https://twitter.com/pingidentity> [image: youtube logo] <https://www.youtube.com/user/PingIdentityTV> [image: LinkedIn logo] <https://www.linkedin.com/company/21870> [image: Facebook logo] <https://www.facebook.com/pingidentitypage> [image: Google+ logo] <https://plus.google.com/u/0/114266977739397708540> [image: slideshare logo] <http://www.slideshare.net/PingIdentity> [image: flipboard logo] <http://flip.it/vjBF7> [image: rss feed icon] <https://www.pingidentity.com/blogs/>

2 3

About oXygen XML Editor
by About oXygen XML Editor 28 Aug '15

28 Aug '15

About oXygen XML Editor /////////////////////////////////////////// DITA 1.3 Implementation Status in upcoming Oxygen XML Editor 17.1 Posted: 26 Aug 2015 10:48 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/yUZ8D06g8Zo/dita-13-… We plan to release Oxygen 17.1 in about a month or two, probably at the beginning of October this year. Starting with version 17.1, Oxygen includes experimental support for editing and publishing using some of the DITA 1.3 features. If you want to test this support and give us feedback please contact us directly to obtain an Oxygen 17.1 beta kit. To enable DITA 1.3 editing support in Oxygen 17.1 and use the custom bundled DITA Open Toolkit 2.1 for publishing, open the Preferences dialog box, go to DITA, and select the Built-in DITA OT 2.x radio button. The following table is a list of DITA 1.3 features and their implementation status: DITA 1.3 Features Implementation Status Feature Editing Publishing [Latest DITA Open Toolkit 2.x is used.] DITA 1.3 DTD, XML Schema, and Relax NG-based maps/topics/tasks/references, etc. New DITA 1.3 file templates. Also by default DITA topics and maps which do not specify version in the DOCTYPE declaration are also considered to be DITA 1.3. Specific annotations presented in the content completion window and documentation tooltips for all new DITA 1.3 elements. See below Learning Object and Group maps New file templates No specific support implemented Troubleshooting specialization Create and edit new troubleshooting topics No specific support implemented XML markup domain Validation and Content Completion Special rendering in PDF and XHTML-based outputs. Equation and MathML domain Validation and content completion Display and Insert equations Special rendering in PDF and XHTML-based outputs. SVG domain Validation and content completion Display referenced SVG content Special rendering in PDF and XHTML-based outputs. Other new DITA 1.3 elements (div, strike-through, overline, etc) Validation and Content Completion. Special rendering in PDF and XHTML-based outputs. Release management domain Validation and Content Completion No specific support implemented. Scoped keys Define key scopes Validate and check for completeness Resolve keyrefs and conkeyrefs taking key scopes into account. Partially implemented. Various issues may still be encountered. Branch filtering Display, create and edit ditavalref elements. Partially implemented. Various issues may still be encountered. Shorthand to address syntax that identifies elements in the same topic Properly resolved for validation, links, and conrefs. Implemented. Various table attributes (orientation, rotation, scope, and headers on cells) Not implemented in the Table Properties action support. But attributes can be changed from the Attributes view. Not implemented. New Map topicref attributes (cascade, deliveryTarget) Allow setting new attributes, propose proper values for them. Implemented. -- You are subscribed to email updates from "About oXygen XML Editor." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

bug report: repeated schema-declared element content
by Syd Bauman 26 Aug '15

26 Aug '15

Assignment: write a RELAX NG schema for Keats _On first looking into Chapman's Homer_. I (deliberately) wrote a ridiculously literalist schema, attached. When I create a new XML document that uses this schema, oXygen properly inserts the required elements, including all 14 required <pLine> elements. When I ask for auto-completion (CTL-space) of the <head> or any of the @n, oXygen does the right thing and gives me the one and only correct choice as the only possible value in the pop-up. But when I ask for auto-completion of <pLine>s 2 through 14, the one and only possible value in the pop-up is the content for the first <pLine>! Worth noting that jing gets it right. After filling in the content using auto-completion, validation will say of <pLine> 2, e.g., character content of element "pLine" invalid; must be equal to "And many goodly states and kingdoms seen;" Details: <oXygen/> XML Developer 17.0, build 2015052917 Mac OS X 10.6.8 error occurs using XML syntax or compact syntax Also tested on: <oXygen/> XML Developer 17.0, build 2015051321 Ubuntu 12.04 only tested compact syntax start = element poem { element head { "On first looking into Chapman's Homer" }, element sonnet { element pLine { attribute num { "01" }, "Much have I travell'd in the realms of gold," }, element pLine { attribute num { "02" }, "And many goodly states and kingdoms seen;" }, element pLine { attribute num { "03" }, "Round many western islands have I been" }, element pLine { attribute num { "04" }, "Which bards in fealty to Apollo hold." }, element pLine { attribute num { "05" }, "Oft of one wide expanse had I been told" }, element pLine { attribute num { "06" }, "That deep-brow'd Homer rules as his demesne;" }, element pLine { attribute num { "07" }, "Yet did I never breathe its pure serene" }, element pLine { attribute num { "08" }, "Till I heard Chapman speak out loud and bold:" }, element pLine { attribute num { "09" }, "Then felt I like some watcher of the skies" }, element pLine { attribute num { "10" }, "When a new planet swims into his ken;" }, element pLine { attribute num { "11" }, "Or like stout Cortez when with eagle eyes" }, element pLine { attribute num { "12" }, "He star'd at the Pacific — and all his men" }, element pLine { attribute num { "13" }, "Look'd at each other with a wild surmise —" }, element pLine { attribute num { "14" }, "Silent, upon a peak in Darien." } } } -- Syd Bauman, EMT-Paramedic Senior XML Programmer/Analyst Northeastern University Women Writers Project s.bauman(a)neu.edu or Syd_Bauman(a)alumni.Brown.edu

4 5

About oXygen XML Editor
by About oXygen XML Editor 25 Aug '15

25 Aug '15

About oXygen XML Editor /////////////////////////////////////////// DITA 1.3 Key Scopes - Next Generation of Reuse Posted: 24 Aug 2015 03:34 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/eupu2DkD4is/dita-13-… Thanks to the hard working OASIS DITA TC Group the DITA 1.3 standard is quite close to being released. Oxygen 17.1 which will be released probably in September this year will have experimental DITA 1.3 support. This will include publishing using a custom build of the latest DITA Open Toolkit 2.x engine in which the main developer Jarno Elovirta has already added incipient support for key scopes and branch filtering. In this blog post I'm going to give you a small example of how key scopes can benefit simple cases of reuse which could not be done previously. Let's say you have a simple DITA task in which you have described how a certain task can be performed for a certain product. In our case, the task describes peeling a potato: The task works and at some point in your Vegetables Soup publication you realise you need to write a similar task about peeling cucumbers. The task is exactly the same, except the product name. So naturally you want to reuse the existing written task. For this we re-write the task so that instead of of the product potatoes it contains a key reference:<ph keyref="vegetable"/> Next we need to define in our DITA Map the vegetable key and bind it to a specific value in the potatoes context: <topicref href="potatoes_overview.dita" keyscope="potatoes">  <keydef keys="vegetable"> <topicmeta> <keywords> <keyword>potatoes</keyword> </keywords> </topicmeta> </keydef>  <topicref href="peeling.dita"/> </topicref>and add in our DITA Map another key scope with the overview and the task which deal with cucumbers peeling: <topicref href="cucumbers_overview.dita" keyscope="cucumbers">  <keydef keys="vegetable"> <topicmeta> <keywords> <keyword>cucumbers</keyword> </keywords> </topicmeta> </keydef>  <topicref href="peeling.dita"/> </topicref> As you may have noticed, we have not used the key scope names for anything. Just by defining the key scopes, we made the product name to be expanded differently in both contexts. But our Vegetables Soup publication may also contain a topic which lists all possible vegetables. This topic is defined in a context outside any key scope:<topicref href="vegetables_over.dita"/>and this overview topic can refer to each product name using the full keyscope key reference value:<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="vegetables_over"> <title>Vegetables Overview</title> <body> This is an overview of all vegetables necessary to make soup. You will learn how to use vegetables like <ph keyref="potatoes.vegetable"/> and <ph keyref="cucumbers.vegetable"/> to make a great starter soup. </body> </topic> As stated before, this kind of reuse was not possible using the standard DITA 1.2 standard constructs. As it turns out, with DITA 1.3 we can also implement this kind of reuse using branch filtering. The DITA samples for this post can be downloaded from http://www.oxygenxml.com/forum/files/keyscopesBlogSamples.zip. As usual any feedback is welcomed. If you would like to beta test Oxygen XML Editor 17.1 with experimental DITA 1.3 support please contact us to support(a)oxygenxml.com. -- You are subscribed to email updates from "About oXygen XML Editor." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

Mac OSX, single instance of diffFiles?
by Steven Anderson 21 Aug '15

21 Aug '15

I've got a Mac and I'd like to have a single instance of diffFiles running. I tried to add -Dcom.oxygenxml.MultipleInstances=false\ to the shell script invocation, but that didn't seem to help. Is there a way to specify this? -- Steve

2 2

Schematron for Multi-Lingual Schemas?
by Tony Graham 21 Aug '15

21 Aug '15

I'm looking at localising the Schematron messages in 'focheck' (https://github.com/AntennaHouse/focheck) The non-normative advice in Annex G, "Use of Schematron for Multi-Lingual Schemas", in the Schematron spec is to use multiple <diagnostic>, one for each translation of the text from an <assert> or <report>. oXygen, unsurprisingly, shows every applicable <diagnostic>. This gets a bit cluttered and, for some user, puts the readable version of the message right at the very end. Is there a way to put multiple, localised versions of a message in a Schematron file and have only the preferred one show? Is there an alternative to making multiple single-language versions of the Schematron? And, while I'm at it, what can be done about l10n of the annotations in Relax NG schema that become tool-tips in oXygen? Regards, Tony Graham. -- Senior Architect XML Division Antenna House, Inc. ---- Skerries, Ireland tgraham(a)antenna.co.jp

3 5

About oXygen XML Editor
by About oXygen XML Editor 13 Aug '15

13 Aug '15

About oXygen XML Editor /////////////////////////////////////////// Document Type Extension Sharing Posted: 12 Aug 2015 04:41 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/CruPt7osXjg/document… You can extend a default bundled document type (like DITA or Docbook) in the Document Type Association preferences page, make modifications and then share the extension with your team. The steps below describe how an extension of the DITA framework which removes certain elements from the content completion list can be constructed and shared: Create somewhere on your disk, in a place where you have full write access a folder structure like: custom_frameworks/dita-extension. In the Document Type Association / Locations preferences page add in your Additional frameworks directories list the path to your custom_frameworks folder. In the Document Type Association preferences page select the DITA document type configuration and use the Extend button to create an extension for it. Give a custom name to the extension, for example DITA - Custom and then change its Storage to external, then save it to a path like: path/to/.../custom_frameworks/dita-extension/dita-extension.framework. Make changes to the extension, for example go to the Author->Content completion tab and add in the Filter - Remove content completion items list elements which should not be presented to the end users. Click OK to close the dialog and then either OK or Apply to save the preferences changes. After you perform the steps above you will have in the dita-extension folder a fully functioning framework which can be shared with others. The framework can then be shared with others in several ways: Copy it to their [OXYGEN_DIR]/frameworks directory. Create somewhere on disk a custom_frameworks folder, copy the framework there and then from the Document Type Association / Locations preferences page add in your Additional frameworks directories list the path to the custom_frameworks folder. Distribute the framework along with a project. Follow these steps: On your local drive, create a directory with full write access, containing the project files and a custom_frameworks folder containing your dita-extension. Start the application, go to the Project view and create a project. Save it in the newly created directory. In the Document Type Association / Locations preferences page, select Project Options at the bottom of the page. Add in the additional framework directories list an entry like ${pd}/custom_frameworks. Add other resources to your project, for example you can have all your DITA content located inside the project folder. You can then share the new project directory with other users. For example you can commit it to your version control system and have they update their working copy. When they open the customized project file in the Project view, the new document type becomes available in the list of Document Types. Deploy the framework/document type configuration as an add-on. After your team members install the framework they can check in Document Type Association preferences page in the list of Document Types to see if the framework is present and if it appears before the bundled DITA framework (meaning that it has higher priority). -- You are subscribed to email updates from "About oXygen XML Editor." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0