- oXygen-user - www.oxygenxml.com

License of generate-xspec-tests-oxygen.xsl
by CIRULLI, Sandro 21 Feb '16

21 Feb '16

Hi, I posted a comment on the XSpec issue tracker related to this patch (https://github.com/expath/xspec/pull/74) I copy-paste it here below. Best, Sandro I tested the support for testing XSLT 3.0 with this XSpec test: <?xml version="1.0" encoding="UTF-8"?> <x:description xmlns:x="http://www.jenitennison.com/xslt/xspec" stylesheet="unit-converter.xsl" xslt-version="3.0"> <x:scenario label="When processing a data element with unit feet"> <x:context> <data> <altitude>1200</altitude> <unit>feet</unit> </data> </x:context> <x:expect label="convert feet to meters"> <data> <altitude>365.76</altitude> <unit>meters</unit> </data> </x:expect> </x:scenario> </x:description> It tests the following XSLT which makes use of high-order functions, a new feature of XSLT 3.0 (the example is adapted from www.xfront.com/Pearls-of-XSLT-and-XPath-3-0-Design.pdf<http://www.xfront.com/Pearls-of-XSLT-and-XPath-3-0-Design.pdf>). <?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:math="http://www.w3.org/2005/xpath-functions/math" exclude-result-prefixes="xs math" version="3.0"> <xsl:variable name="unit-converter" select="function( $value as xs:decimal, $f as function(item()*) as item()* ) as xs:decimal {$f($value)}"/> <xsl:variable name="feet-to-meters" select="function( $a as xs:decimal ) as xs:decimal {$a * 0.3048}"/> <xsl:template match="data[unit='feet']"> <xsl:copy> <altitude> <xsl:value-of select="$unit-converter(altitude, $feet-to-meters)"/> </altitude> <unit>meters</unit> </xsl:copy> </xsl:template> </xsl:stylesheet> I run this test with Oxygen 14.2 (which includes the Oxygen patch) and the test goes through successfully. However, I noticed that with this patch it is compulsory to specify the @xslt-versionwith the value '3.0' when testing an XSLT 3.0. If the attribute is not provided, the Oxygen ant file complains that XPath 3.0 is needed to run the test. If the patch is changed from: <stylesheet version="{( @xslt-version, '2.0' )[1]}"> to: <stylesheet version="{if ( @xslt-version, '3.0' ) then '3' else '2'}"> the XSpec test runs correctly even if @xslt-version is not provided. I wonder if this implementation may be more suitable as it does not force to specify the @xslt-version in the XSpec test, one only needs to specify the XSLT version in the actual XSL stylesheet. It also seems to me more consistent when writing XSpec tests for XSLT 2.0 as it is not required to specify @xslt-version in the XSpec test. Unfortunately I'm unable to test this implementation when running XSpec from the command line as XSLT 3.0 requires saxon9ee.jar (I only have saxon9he.jar available). Oxford University Press (UK) Disclaimer This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.

3 2

XSpec framework modification
by Christophe Marchand 21 Feb '16

21 Feb '16

After talk about this at #xmlprague, here is the project : https://github.com/cmarchand/oxygen-xspec-patch It only matches OUR needs, giving the project basedir to build.xml, but it can be enhanced to give a absolute catalog.xml URI... ;) Best, Christophe -- Christophe MARCHAND Consultant Formateur cmarchand(a)oxiane.com <mailto:cmarchand@oxiane.com> LD : (+33)1 84 19 19 76 GSM : +33 (0)6 23 41 09 17 oxiane 98, avenue du Général Leclerc 92100 Boulogne-Billancourt Standard : (+33)1 55 60 76 72 Fax : (+33)1 55 60 76 73 www.oxiane.com <http://www.oxiane.com> Notre catalogue formations 2016 Notre catalogue formations 2015 <http://www.oxiane.com/wp-content/uploads/2015/11/OXiane_Catalogue_2016.pdf>

2 2

change font in oXygen Web App?
by Yves Barbion 17 Feb '16

17 Feb '16

Hi The oXygen Web App currently displays the text of my (DITA) topics in Times New Roman. Is there a way to change the font, for example to something sans serif? Thanks Yves Barbion www.scripto.nu

2 1

[Ann] New maintenance build available for oXygen 17.1 (2016020417)
by Oxygen XML Editor Support (Adrian Buza) 08 Feb '16

08 Feb '16

Dear oXygen users, We announce the release of a new maintenance build (2016020417) for oXygen 17.1 (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#2016020417 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, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

math and color
by Ulrike Borinski 01 Feb '16

01 Feb '16

Good morning, in Author mode I work with math-Elements using Math-Flow. In some circumstances I would like to color some of the math Elements. Some of them should be black, as they are usually. Some of them should be blue – if they are descendants of the Element »Lösung«. I try to change the color in my css – but they remains black. What can I do? Kind regards Ulrike Borinski . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ulrike Borinski Dipl.-Designerin Koordination Servicestelle Mediengestaltung und Publishing Borinski(a)ifv-nrw.de 02331/9330-927 www.ifv-nrw.de/ifv_gest/lerneinheiten.htm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Institut für Verbundstudien der Fachhochschulen Nordrhein-Westfalens - IfV NRW Im Alten Holz 131 58093 Hagen

2 1

License of generate-xspec-tests-oxygen.xsl
by cmarchand＠oxiane.com 14 Jan '16

14 Jan '16

Hello Oxygen guys ! I would like to re-use generate-xspec-tests-oxygen.xsl in a separate project (xspec-maven-plugin enhancements, under MIT license). Oxygen team has made improvements to XSpec implementations (http://github.com/expath/xspec/) and have added this file. XSpec implementation is licensed under MIT license ; as there is no license header on this file, does generate-xspec-tests-oxygen.xsl is licensed under MIT license too, or is there another license for this particular file ? Thanks in advance, Christophe

2 2

Multilingual Schematron messages?
by Tony Graham 13 Jan '16

13 Jan '16

The "Schematron & Schematron Quick-Fix In oXygen" session at the oXygen Users Meetup at XML Prague 2016 (http://oxygenxml.com/events/2016/oXygen-user-meetup-Prague.html, but page title says "Prague 2015") is to include "multilingual messages". I can't find anything about that in the oXygen 17.1 manual. How is it done? Regards, Tony Graham. -- Senior Architect XML Division Antenna House, Inc. ---- Skerries, Ireland tgraham(a)antenna.co.jp

6 12

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

oXygen to WordPress
by Ben McGinnes 12 Jan '16

12 Jan '16

Hello, So I stumbled across this post from a couple of years ago: https://www.oxygenxml.com/pipermail/oxygen-user/2013-August/004754.html Basically just asking for a feature to update a WordPress blog and said request being forwarded along. I've got two questions: 1) Did it become a feature? 2) If not, now that WordPress supplies an optional JSON based REST API, could the request be revisited since it ought to make it easier to make the two things play nicely together? WordPress API documentation: http://v2.wp-api.org/ I've only looked at it briefly, but it's REST so it can't be that hard, not as far as communicating with the server is concerned, at any rate. I've done a few client-side interaction things like this at times; mainly grabbing Bitcoin and/or currency live data and playing with the Twitter API so from my perspective the worst case scenario is making the right HTML template to play nicely at the other end and adding a few Python scripts (well, of course, by now everyone saw *that* language preference coming). Still, there's a lot to be said for "point and click" if it just works. Although the Github repositories also include command line tools and a console for the thing, so chances are integration could be reduced to calling the relevant commands to do whatever. The rough edges at the moment appear to be limited to generating the OAuth credentials, but that's not a huge chore for most WordPress admins. Regards, Ben -- Ben McGinnes http://www.adversary.org/ Twitter: benmcginnes Writer, Systems Administrator, Trainer, ICT Consultant GPGME Python 3 API Maintainer, GNU Privacy Guard https://www.gnupg.org/ Encrypted email preferred, primary OpenPGP/GPG key: 0x321E4E2373590E5D OpenPGP/GPG key here: http://goo.gl/GVGwT and http://goo.gl/SDs0D OpenPGP/GPG key transition: http://www.adversary.org/keyswitch.txt.asc

3 9