- oXygen-user - www.oxygenxml.com

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

Defect in SVG viewer
by Timothy Reaves 30 Jun '15

30 Jun '15

I created an SVG document with - I believe - a version of oXygen in the 15.x series, about two years ago. I just opened it in oXygen to edit it, and it no longer renders correctly in oXygen. In the Mac Finder, Safari, and Firefox, it still does render correctly. Are there any known defects? If not, whom should I send the SVG to to create a defect report? Thanks.

2 1

Whitespace-only text nodes in XSLT
by Wendell Piez 29 Jun '15

29 Jun '15

Hi, Given this stylesheet: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:variable name="mixed" as="element()"> <mixed>Here is mixed content, including <one>children</one> <two>with nothing</two> but whitespace between them.</mixed> </xsl:variable> <xsl:template match="/"> <xsl:apply-templates select="$mixed"/> </xsl:template> <xsl:template match="node() | @*"> <xsl:copy> <xsl:apply-templates select="node() | @*"/> </xsl:copy> </xsl:template> </xsl:stylesheet> I run it on itself in oXygen, and get <?xml version="1.0" encoding="UTF-8"?><mixed>Here is mixed content, including <one>children</one><two>with nothing</two> but whitespace between them.</mixed> I would expect whitespace between the </one><two>. What am I missing? Have things changed wrt whitespace-handling rules? (As I see it, the temporary tree $mixed should contain a whitespace-only text node between the 'one' and 'two' elements.) Thanks for any insights, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

4 6

Oh icon my icon!
by Syd Bauman 29 Jun '15

29 Jun '15

Apologies if this is a FAQ. I'm working on some "do this in oXygen" documentation, and would like to show the reader which button to click, e.g., for configuring a transformation scenario. I could, of course, use my computer's capture-a-snippet-of- the-screen utility. But it seems better (IMHO) to just use the original graphic, if readily available. Where in my oXygen/ directory would I find the icons? (I'm looking in version 16 either in Mac OS X or in GNU/Linux -- I don't have easy access to a Windows machine w/ oXygen.) (And yes, I use version 17, but this documentation is aimed at users of v 16. :-) Thanks.

2 1

transform "body rows" <tbody> to "heading rows" <thead>
by Yves Barbion 25 Jun '15

25 Jun '15

Hi group Is there an easy way in oXygen 17 to select the first row in a table and make that row a "heading row" (thead)? <feature_request> I think it would be nice to have some kind of content menu command which says: "Transform to heading row".</feature_request> Thanks -- Yves Barbion www.scripto.nu

3 2

DITA workshops using oXygen XML Editor
by George Bina 24 Jun '15

24 Jun '15

Hi all, Comtech Services, the company that organizes the DITA North America and DITA Europe conferences organizes also a number of DITA workshops and they use oXygen XML Editor to complete the different exercises, so these workshops may be a good opportunity to learn DITA and the oXygen DITA functionality. Here it is a description from Comtech Services of available workshops: *** DITA Getting Started: July 21-22 in Wakefield, MA This workshop is designed as an introduction to Darwin Information Typing Architecture (DITA). During the workshop you will learn to design and create information using a topic/task-based structured-authoring approach. You will also learn how to use XML markup with DITA elements and the importance of the DITA elements to information development. Optimizing the DITA Authoring Experience: July 23-24 in Wakefield, MA In this workshop, you are guided through the process of customizing your authoring environment using each of the following technologies: shells, specializations, constraints, templates, subject scheme maps, and publishing scenarios. With ample time for applying what you have learned, you will leave the workshop with the necessary tools to optimize the authoring experience for your authoring team. Advanced Publishing for DITA: August 3-7 in San Jose, CA In this workshop, attendees are provided a walk-through of the essential DITA fundamentals, programming skills, and DITA Open Toolkit configurations required to assemble, style, and publish DITA XML source. After a brief overview of the DITA framework, course lectures and exercises will focus on the key pieces of a DITA publishing architecture, how to set it up, and how to optimize its publishing capabilities using customizations and plug-ins. Attendees will learn to set up a publishing architecture using the pipeline provided by the DITA-OT and learn how to configure and debug the DITA-OT. For more information visit Comtech Services web site at http://comtech-serv.com/url/upcoming or contact Comtach Services at 303-232-7586. *** Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

Last chance to book! Digital Humanities at Oxford Summer School 2015
by James Cummings 19 Jun '15

19 Jun '15

Please Forward! ==== It is your last chance to book for the Digital Humanities at Oxford Summer School 2015! http://dhoxss.humanities.ox.ac.uk/2015/ Booking closes on 29 June, and some workshops will be sold out before then! Can't make it to the DHOxSS 2015? Sign up to our announcement mailing list for 2016 at http://dhoxss.humanities.ox.ac.uk/2016/ ==== Digital Humanities at Oxford Summer School 20 - 24 July 2015 Scholarship -- Application -- Community http://dhoxss.humanities.ox.ac.uk/2015/ml/ Do you work in the Humanities or support people who do? Are you interested in how the digital can help your research? Come and learn from experts with participants from around the world, from every field and career stage, to develop your knowledge and acquire new skills Immerse yourself for a week in one of our 8 workshop strands, and widen your horizons through the keynote and additional sessions Workshops: - An Introduction to Digital Humanities - Crowdsourcing for Academic, Library and Museum Environments - Digital Approaches in Medieval and Renaissance Studies - Digital Musicology - From Text to Tech - Humanities Data: Curation, Analysis, Access, and Reuse - Leveraging the Text Encoding Initiative - Linked Data for the Humanities Keynote Speakers: - Jane Winters, Institute of Historical Research, University of London - James Loxley, University of Edinburgh Additional Lectures: Supplement your chosen workshop with a choice from 9 additional morning sessions covering a variety of Digital Humanities topics. Evening Events: Join us for events every evening, include a research poster and drinks reception, guided walking tour of Oxford, the annual TORCH Digital Humanities lecture, and a dinner at Exeter College. For more information see: http://dhoxss.humanities.ox.ac.uk/2015/ml/ Directors of DHOxSS, James Cummings Pip Willcox -- Dr James Cummings,James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0