July 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

draft-comment without @author?
by Yves Barbion 27 Jul '15

27 Jul '15

Hi group When I insert a draft-comment in a DITA topic, I see that the name of the author of the draft-comment is filled in automatically, which is nice. But is there also an easy way (a setting in the preferences maybe) to insert a draft-comment without the author's name? Thanks -- Yves Barbion www.scripto.nu

2 2

adding namespace prefix to autocomplete list
by Erik Zander 23 Jul '15

23 Jul '15

Hi, I have been searching for some information (but not found) on how I can add my own prefixes to XSLT editor like the one for xmlns:saxon="http://saxon.sf.net/" where you get the autocomplete alternative xmlns:saxon. This when activating autocomplete in the xsl:stylesheet element attribute list. Looking forward to any help. Regards Erik

2 2

[Ann] New maintenance build available for oXygen 17.0 (2015071312)
by oXygen XML Editor Support (Ionela Istodor) 20 Jul '15

20 Jul '15

Dear oXygen users, We announce the release of a new maintenance build (2015071312) for oXygen 17.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2015071312 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Ionela -- Ionela Istodor oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.301 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

About oXygen XML Editor
by About oXygen XML Editor 18 Jul '15

18 Jul '15

About oXygen XML Editor /////////////////////////////////////////// Controlled Attribute Values (Part 2 - Advanced) Posted: 17 Jul 2015 03:42 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/NE2VjDi24KA/controll… As already presented in Controlled Attribute Values for your DITA Project, Oxygen allows you to add or replace possible values for attributes or elements based on a simple configuration file. A more complex scenario is one in which in order to decide which values to provide, you need more context information. Let's take this DITA fragment: <metadata> <othermeta name="name" content="value"/> </metadata> What we want is to offer proposals for @content but the possible values for @content depend on the value of @name. We will see how we can solve this dependency. The configuration file The configuration file (cc_value_config.xml) allows calling an XSLT stylesheet and that's just what we will do:<match elementName="othermeta" attributeName="content"> <xslt href="meta.xsl" useCache="false"/> </match> As you can see, we can't express the dependency between @content and @name inside the configuration file . I also want to mention that because the values for @content are dynamic, we want the XSLT script to execute every time the values are requested (we shouldn't cache the results). We enforce this by setting @useCache to false. The XSLT script The XSLT script has access to the XML document (through the documentSystemID parameter) but it lacks any context information, we can't really tell for which othermeta element was the script invoked. To counter this limitation, we will use Java extension functions and we will call Oxygen's Java-based API from the XSLT. Here how it looks:<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" xmlns:tei="http://www.oxygenxml.com/ns/doc/xsl" xmlns:prov="java:ro.sync.exml.workspace.api.PluginWorkspaceProvider" xmlns:work="java:ro.sync.exml.workspace.api.PluginWorkspace" xmlns:editorAccess="java:ro.sync.exml.workspace.api.editor.WSEditor" xmlns:saxon="http://saxon.sf.net/" xmlns:textpage="java:ro.sync.exml.workspace.api.editor.page.text.xml.WSXMLTextEditorPage" xmlns:authorPage="java:ro.sync.exml.workspace.api.editor.page.author.WSAuthorEditorPage" xmlns:ctrl="java:ro.sync.ecss.extensions.api.AuthorDocumentController" exclude-result-prefixes="xs xd" version="2.0"> <xsl:param name="documentSystemID" as="xs:string"></xsl:param> <xsl:template name="start"> <xsl:variable name="workspace" select="prov:getPluginWorkspace()"/> <xsl:variable name="editorAccess" select="work:getEditorAccess($workspace, xs:anyURI($documentSystemID), 0)"/> <xsl:variable name="pageID" as="xs:string" select="editorAccess:getCurrentPageID($editorAccess)"/> <xsl:variable name="name" as="xs:string"> <xsl:choose> <xsl:when test="$pageID='Text'"> <xsl:variable name="textpage" select="editorAccess:getCurrentPage($editorAccess)"/>  <xsl:value-of select="textpage:evaluateXPath($textpage, 'xs:string(./parent::node()/@name)')"/> </xsl:when> <xsl:when test="$pageID='Author'"> <xsl:variable name="authorPage" select="editorAccess:getCurrentPage($editorAccess)"/> <xsl:variable name="caretOffset" select="authorPage:getCaretOffset($authorPage)"/> <xsl:variable name="ctrl" select="authorPage:getDocumentController($authorPage)"/> <xsl:variable name="contextNode" select="ctrl:getNodeAtOffset($ctrl, $caretOffset)"/>  <xsl:value-of select="ctrl:evaluateXPath($ctrl, 'xs:string(@name)', $contextNode, false(), false(), false(), false())[1]"/> </xsl:when> </xsl:choose> </xsl:variable> <items> <xsl:choose> <xsl:when test="$name = 'temperatureScale'"> <item value="Celsius" annotation="(symbol C)"/> <item value="Fahrenheit" annotation="(symbol F)"/> </xsl:when> <xsl:when test="$name = 'measurement'"> <item value="Metric" annotation="Metric system"/> <item value="Imperial" annotation="Also known as British Imperial"/> </xsl:when> </xsl:choose> </items> </xsl:template> </xsl:stylesheet> It is also worth mentioning that in the next Oxygen version (17.1) we will provide a more elegant solution to this situation. The XSLT script will receive a new parameter, an XPath expression that will identify the element for which content completion was invoked. But maybe we will talk about that in a future post... -- 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

About oXygen XML Editor
by About oXygen XML Editor 16 Jul '15

16 Jul '15

About oXygen XML Editor /////////////////////////////////////////// Controlled Attribute Values for your DITA Project Posted: 15 Jul 2015 03:31 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/AGTBTAnCxA0/controll… Frequently when editing DITA content you will feel the need to enforce a controlled set of values when editing certain attributes. For example you may want to impose that the values for the @outputclass attribute on the element codeblock are either language-xml or language-css. This is useful in order to remind writers that any other value will not be interpreted by the build process in a significant manner. Oxygen has a couple of easy ways in which controlled values can be imposed for certain attributes: You can edit the XML configuration file OXYGEN_INSTALL_DIR/frameworks/dita/resources/cc_value_config.xml and provide additional entries. In the case of our small example for providing controlled values for the @attribute the configuration file should contain an additional entry:<match elementName="codeblock" attributeName="outputclass"> <items action="addIfEmpty"> <item value="language-xml" annotation="XML Syntax Highlight"/> <item value="language-css" annotation="CSS Syntax Highlight"/> </items> </match>Besides providing a hard-coded list of values the content completion configuration file is flexible enough to allow calling an XSLT stylesheet which could retrieve those values from other sources (for example via HTTP from an Exist database). Provide those controlled values via a Subject Scheme Map (my favorite). Coming back to our example, you can create a small Subject Scheme map with the file name controlledValues.ditamap and the content:<!DOCTYPE subjectScheme PUBLIC "-//OASIS//DTD DITA Subject Scheme Map//EN""map.dtd"> <subjectScheme> <subjectHead> <subjectHeadMeta> <navtitle>Provide controlled attributes</navtitle> </subjectHeadMeta> </subjectHead> <hasInstance> <subjectdef keys="languageTypeKey"> <subjectdef keys="language-xml"> <topicmeta> <navtitle>XML Syntax Highlight</navtitle> </topicmeta> </subjectdef> <subjectdef keys="language-css"> <topicmeta> <navtitle>CSS Syntax Highlight</navtitle> </topicmeta> </subjectdef> </subjectdef> </hasInstance> <enumerationdef> <elementdef name="codeblock"/> <attributedef name="outputclass"/> <subjectdef keyref="languageTypeKey"/> </enumerationdef> </subjectScheme>then you can refer to it from your main DITA Map like:<topicref href="controlledValues.ditamap" format="ditamap" type="subjectScheme"/> If the attributes on which you want to impose certain values are DITA profiling attributes, you can go to the Oxygen Preferences->Editor / Edit modes / Author / Profiling/Conditional Text page and define the set of allowed values for them. The only problem with the first approach is the fact that validation will not impose those values and writers will not receive validation error messages if they set another value for the specific attribute. So you will probably need to add a Schematron check in order to signal errors when a certain attribute's value does not match the list of controlled attribute values. For both the second and third approaches, validation will warn the writers if certain attribute values do not match values in the controller values list. -- 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

Possible standalone WebDAV client with oXygen?
by David Sewell 13 Jul '15

13 Jul '15

I and a couple of other people in my department often need to read and write files via WebDAV connections (specifically, to MarkLogic's WebDAV server interface to its database). We all use OS X as our platform, and we have often found that the built-in WebDAV mounting support in OS X Finder is unreliable. We have used an alternative standalone client (Transmission), but lately it has had some performance problems as well. The internal WebDAV client within oXygen has always been solidly reliable. Is there any chance that it could be bundled or sold separately as a standalone WebDAV client? Would other oXygen users find that useful? (Or does anyone have suggestions about other OS X WebDAV clients to try?) David -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400318, Charlottesville, VA 22904-4314 USA Email: dsewell(a)virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/

3 2

Problems with copy and paste from Firfox
by Sascha Manns 10 Jul '15

10 Jul '15

Hello List, actually i'm writing with XML-Editor a document. Sometimes i'm using copy and paste from Firefox to XML-Editor in Author-Mode. The problem is, after STRG+V the text is inserted on the wished place, but the umlauts are broken. So the german word "Beträge" looks like "Betrýge". I've seen in the sourcecode of the website UTF-8 is set as charset. Inside the XML Editors settings i have set: Fallback Charset: UTF-8. Also my docbook file begins with: <?xml version="1.0" encoding="utf-8"?>. So i don't understand why this broken char happens. Maybe anyone knows more? Greetings Sascha -- Yours sincerly Sascha Manns *** XCOM AG Legal Disclaimer *** Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allein für den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir bitten, eine fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns eine Nachricht zukommen zu lassen. This email may contain material that is confidential and for the sole use of the intended recipient. Any review, distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Hauptsitz: Allee 8, D-47877 Willich, USt-IdNr.: DE 812 885 664 Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900, www.xcom.de Handelsregister: Amtsgericht Krefeld, HRB 10340 Vorstand: Dirk Franzmeyer, Marco Marty, Dirk Werner, Sascha Bochartz Vorsitzender des Aufsichtsrates: Stefan H. Tarach

2 1