Ulrike Borinski | 1 Feb 10:01 2016
Picon

math and color

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 <at> 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

_______________________________________________
oXygen-user mailing list
(Continue reading)

cmarchand | 13 Jan 14:43 2016

License of generate-xspec-tests-oxygen.xsl

 

 

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

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Alex Jitianu | 12 Jan 10:53 2016
Picon

Re: Pretty Print <lb/> in Oxygen

Dear all,

In Oxygen version 17.1 you have the possibility to specify "Line break" elements [1], that is to say elements for which we have to break the line before (or after) serializing them. The entries from this new list are a form of simplified XPath expressions that also accept one attribute condition (default attribute values are not taken into account):

- element[ <at> attr] - Matches all instances of the specified element that include the specified attribute.
- element[not( <at> attr)] - Matches all instances of the specified element that do not include the specified attribute.
- element[ <at> attr = "value"] - Matches all instances of the specified element that include the specified attribute with the given value.
- element[ <at> attr != "value"] - Matches all instances of the specified element that include the specified attribute and its value is different than the one given.

We only accept one attribute condition because we want these expressions to run as fast as possible but nevertheless, it should suffice for writing expression that take into account the <at> break attribute. Hope it helps!

[1] https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/preferences-editor-format-xml.html
Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 12/17/2014 7:09 PM, Wendell Piez wrote:
Syd and Gerrit, I am so behind! (on old messages to mailing lists) -- In the meantime, until oXygen does everything perfectly, could one perhaps introduce the LF characters you want (in your mixed content) using XQuery update (which works in oXygen's XQuery Builder), or (gasp!) plain-text s/r over the raw XML? Cheers, Wendell On Tue, Oct 28, 2014 at 5:06 PM, Syd Bauman <syd-Ljp0bcNj9r7NGNIkOW1XXOCmf2DRS9x2@public.gmane.org> wrote:
I agree with Gerrit; while all Andreas says is true, it is not an argument against having an option for format-and-indent to intelligently insert specific whitespace in front of (or after) desired elements. (Not only are we suggesting this as an option, I suspect all of us on the "I like this feature" side would agree it should be an option that is off by default, for the very reasons Andreas articulates :-) E.g., adding two new tabs to Options > Preferences / Editor / Format / XML / Element Spacing: 1) Starts new line: Element names or XPath expressions for which the start-tag (or empty-element tag) should be forced to start on a new line (and then indented appropriately) 2) Ends line: Element names or XPath expressions for which the start-tag (or empty-element tag) should be made the last token on a line Both lists should start out empty, of course. P.S. IIRC, last I checked (years ago) those were not "XPath expressions", they were not even full XSLT patterns, but rather were a very limited set of XSLT patterns. If that is still true, I would strongly recommend changing the wording slightly and putting some pop-up help or information right there.
I share Ute's wish for a format-and-indent in the text mode that puts <lb> at the beginning of each line. xml:space does not seem satisfying to me because it prevents Oxygen from doing any format-and-indent. Find/replace is neither very elegant nor will it give the result Syd has described. I admit that the addition of whitespace in mixed content elements where no whitespace exists is generally critical (and I like Oxygen for not doing this!). However, any whitespace preceding or following an <lb> can be treated as insignificant. Even Oxy<lb break="no">gen Oxy <lb break="no">gen are equivalent, except that a little more processing is needed to extract the token "Oxygen" from such an encoding. So I find it responsible to allow Oxygen---on explicit request---to add whitespace befor <lb> elements. At least, it would be nice to get Oxygen to put all the <lb>s at the beginning of the line that *already have* whitespace before them.
_______________________________________________ oXygen-user mailing list oXygen-user-xj0E2L9sap8S+FvcfC7Uqw@public.gmane.org http://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Alex Jitianu | 12 Jan 10:02 2016
Picon

Re: Not indent elements with 'linefeed-treatment="preserve"'?

Hello Tony,

In Oxygen version 17.1 you can use one attribute condition inside the 'Preserve space' entries. So an entry like: *[ <at> linefeed-treatment='preserve'] should now work.

The XPath expressions can accept one of these type of attribute conditions (default attribute values are not taken into account):
  • element[ <at> attr] - Matches all instances of the specified element that include the specified attribute.
  • element[not( <at> attr)] - Matches all instances of the specified element that do not include the specified attribute.
  • element[ <at> attr = "value"] - Matches all instances of the specified element that include the specified attribute with the given value.
  • element[ <at> attr != "value"] - Matches all instances of the specified element that include the specified attribute and its value is different than the one given.

All the above restrictions and limitations are because we want these expressions to run as fast as possible.

Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 8/27/2015 2:30 PM, Tony Graham wrote:
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-editor-format-xml.html
says that elements can be added to the 'Preserve space' list, but
"*[ <at> 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-indent-xml.html
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.

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Tony Graham | 11 Jan 13:27 2016
Picon

Multilingual Schematron messages?

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@...
George Bina | 11 Jan 09:32 2016
Gravatar

Re: XSLT Processor under XProc

Dear David,

You can find the engine used when running XProc scripts with Calabash 
simply by invoking a stylesheet from XProc that outputs the processor 
name and version, like the one below:

<p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
     xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0">
     <p:input port="source">
         <p:inline>
             <doc>Hello world!</doc>
         </p:inline>
     </p:input>
     <p:output port="result"/>
     <p:xslt>
         <p:input port="parameters">
             <p:empty/>
         </p:input>
         <p:input port="stylesheet">
             <p:inline>
                 <xsl:stylesheet 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
                     <xsl:template match="/">
                         <result>
                             <xsl:value-of 
select="system-property('xsl:product-name')"/>
                             <xsl:value-of 
select="system-property('xsl:product-version')"/>
                         </result>
                     </xsl:template>
                 </xsl:stylesheet>
             </p:inline>
         </p:input>
     </p:xslt>
</p:declare-step>

This should output "SAXONEE 9.6.0.7".

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 11/01/16 02:25, David Levy wrote:
> I have just started to experiment with XProc.
>
> Prior to using XProc, I have been transforming XML with XSLT and the
> transformation scenario lets me select among a number of transformation
> engines such as various flavors of Saxon. When I run the transformation
> under XProc as a p:xslt step, I am getting some errors that didn’t
> appear with Saxon. These are easily solved, but I wonder:
>
> (1)What XSLT engine is being used with XProc? Does Calabash provide its
> own engine?
>
> (2)Can I control which engine is being used within XProc?
>
> With thanks,
>
> David
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user@...
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>

Re: XSLT Processor under XProc

Hello David,

When I run the transformation under XProc as a p:xslt step, I am getting some errors that didn’t appear with Saxon.
Try running the same transformation in Oxygen with Saxon-EE and check if you see the same errors. It's possible that Saxon-EE shows you a different set of errors.

(1)    What XSLT engine is being used with XProc? Does Calabash provide its own engine?
XML Calabash (within Oxygen) is configured to use Saxon-EE. A Saxon configuration file is located in Oxygen\lib\xproc\calabash\lib\saxon.config. This can be used to set the edition of Saxon (EE/PE/HE) and various Saxon settings.
AFAIK, the command line XML Calabash bundles and uses Saxon-HE, but can probably be configured to use other XSLT engine implementations (Java).


(2)    Can I control which engine is being used within XProc?
For XML Calabash within Oxygen you can only control the edition of Saxon being used. See the saxon.config file I mentioned above. You can set configuration/ <at> edition="PE" or configuration/ <at> edition="HE".

If you're using XML Calabash in the command line (independently from Oxygen) I suspect it's possible to use various javax.xml.transform.TransformerFactory implementations, but don't have a clear configuration path for that. In theory, if the XSLT engine implements the javax.xml.transform.TransformerFactory service, it should also advertise it, so it should work by simply replacing one XSLT engine .jar library with another in the Java classpath.

Regards,
Adrian
Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482
On 11.01.2016 02:25, David Levy wrote:
<!-- /* Font Definitions */ <at> font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} <at> font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only;} <at> page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} /* List Definitions */ <at> list l0 {mso-list-id:1649289023; mso-list-type:hybrid; mso-list-template-ids:544346552 1151350672 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} <at> list l0:level1 {mso-level-text:"\(%1\)"; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} -->

I have just started to experiment with XProc.

 

Prior to using XProc, I have been transforming XML with XSLT and the transformation scenario lets me select among a number of transformation engines such as various flavors of Saxon. When I run the transformation under XProc as a p:xslt step, I am getting some errors that didn’t appear with Saxon. These are easily solved, but I wonder:

 

(1)    What XSLT engine is being used with XProc? Does Calabash provide its own engine?

(2)    Can I control which engine is being used within XProc?

 

With thanks,

 

David



_______________________________________________ oXygen-user mailing list oXygen-user-xj0E2L9sap8S+FvcfC7Uqw@public.gmane.org https://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
David Levy | 11 Jan 01:25 2016
Picon
Picon

XSLT Processor under XProc

I have just started to experiment with XProc.

 

Prior to using XProc, I have been transforming XML with XSLT and the transformation scenario lets me select among a number of transformation engines such as various flavors of Saxon. When I run the transformation under XProc as a p:xslt step, I am getting some errors that didn’t appear with Saxon. These are easily solved, but I wonder:

 

(1)    What XSLT engine is being used with XProc? Does Calabash provide its own engine?

(2)    Can I control which engine is being used within XProc?

 

With thanks,

 

David

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Ben McGinnes | 4 Jan 23:33 2016

oXygen to WordPress

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

_______________________________________________
oXygen-user mailing list
oXygen-user@...
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Gioele Barabucci | 3 Jan 20:24 2016
Picon

Debugger says that watched variable is in "Slot -1"

Hello,

while debugging an XSLT function, I added a watch on the parameter
`$origin` and another on `string($origin//key)`. The former works
flawlessly, the latter always displays the following error:

> Error: Local variable $origin uses slot -1 but only 3 slots
> are allocated on the stack frame

I get this error when the debugger stops at the breakpoint I have placed
on the `xsl:if` instruction of the following function:

    <xsl:function name="f:siblings-until">
        <xsl:param name="origin" as="element()"/>
        <xsl:param name="stopper" as="xs:QName"/>

        <xsl:variable name="next-sibling"
select="$origin/following-sibling::*[1]"/>

        <xsl:variable name="is-stopper" as="xs:boolean"
select="node-name($origin) eq $stopper"/>
        <xsl:variable name="is-last" as="xs:boolean"
select="not($next-sibling)"/>

        <xsl:if test="not($is-stopper) and not($is-last)">
            <xsl:sequence select="$origin,
f:siblings-until($next-sibling, $stopper)"/>
        </xsl:if>
    </xsl:function>

Regards,

--

-- 
Gioele Barabucci <gioele@...>
Gioele Barabucci | 24 Dec 13:37 2015
Picon

Re: Using a different (minor) version of Saxon with oXygen?

On 24/12/2015 13:22, Oxygen XML Editor Support (Adrian Buza) wrote:
> Hello,
> 
> Because of the tight integration (validation, debugging, etc), you
> cannot upgrade the version of Saxon 9 that comes bundled with Oxygen.

Thank you for your response.

I understand that oXygen hooks very deep inside Saxon, but I suppose
(maybe naively) that none of these low-level APIs have changed between
9.6.0.7 and 9.6.0.8.

> However, you can use a different version of Saxon in Oxygen as a custom
> (command line) XSLT or XQuery engine for transformations (NOT for
> debugging),

I need to use XSLT as part of a XProc pipeline, so that route is not
practicable for me.

Regards,

--

-- 
Gioele Barabucci <gioele@...>

Gmane