- oXygen-user - www.oxygenxml.com

format-and-indent nukes trailing PI or comment
by Syd Bauman 11 Dec '09

11 Dec '09

Using "XML Editor 11.0, build 2009101212", I find that choosing Document > XML Document > Format and Indent (actually, pressing cmd-shift-P) deletes any and all comments and processing instructions that occur after the root element end tag. (And per production 1 of the XML Spec, they're allowed. But even if they weren't, they shouldn't be summarily deleted! :-) Apologies if this is a known bug that has already been reported.

2 2

Connecting oXygen to Mark Logic using XDBC
by Andrew Welch 09 Dec '09

09 Dec '09

Hi, Just to let you know, the only way I could get oXygen to connect to Mark Logic 4.1 through XDBC was to change the authentication from "digest" to "basic" for the XDBC server in ML. I wonder if oXygen should be using "digest" by default, or if not you might need to add a note to your guide: http://www.oxygenxml.com/MarkLogic_support.html thanks andrew -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/

2 1

Schematron validation "errors" enhancement
by Wendell Piez 09 Dec '09

09 Dec '09

Hi, Currently, Schematron is regarded by oXygen as a validation technology, and it uses many of the same interfaces as XSD, RNG and DTD, including having its results reported in a validation results window. This is fine, but additionally, a distinction is made between Schematron messages emitted by Schematron 'assert' elements and those emitted by 'report' elements; the latter are classed as warnings, not errors. They are formatted differently, with a yellow icon instead of a red one, plus the word "warning". However, in my experience working with Schematron, more often than not this distinction does not hold. "Errors" or "warnings" or simple "alerts" or messages of any status whatever can be the results of either a Schematron 'assert' or 'report'; that is, which Schematron element is used to generate a message has nothing to do with the severity of the condition being reported. Or even whether it's good or bad: sometimes the message emitted by either an 'assert' or 'report' represents not failure but success. I wonder if in oXygen, this distinction could be removed, and the results of all Schematron assertions (both 'assert' and 'report', i.e "positive and negative assertions of a constraint") could be represented the same. If you really wanted to get fancy, the status of a Schematron message in oXygen might be configurable. Maybe the assignment of "error" or "warning" (or whatever else: blue or green icons?) could be made on the basis of a regular expression matching the message. It's pretty common practice for Schematron messages to be internally structured with their own language about errors, warnings, alerts, info, etc., with structurer error codes and the like. The same thing applies to the inline iconography, i.e., having errors from 'assert' underlined in red in the editor view, while 'report' results are colored yellow. For Schematron developers who are deploying oXygen as a validation platform for non-experts -- who are sometimes prone to be alarmed unnecessarily by iconography -- it would be really nice to be able to control this. If not, I think oXygen might at least be neutral on the question of which Schematron messages are at which level of severity. What do you think? Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

4 12

Re: [oXygen-user] Schematron validation "errors" enhancement
by Wendell Piez 09 Dec '09

09 Dec '09

Hi again, While we're on the topic, does oXygen ever make use of the 'Info' field in the Validation results pane when validating with Schematron? Inquiring minds want to know. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

2 1

Re: [oXygen-user] Visual editor for XML file mapping (xslt)
by George Cristian Bina 03 Dec '09

03 Dec '09

Dear Ingo, Such an editor is on our todo list. However it is not scheduled for implementation yet and it requires a substantial implementation effort so it is a long term project. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Ingo Freitag wrote: > Hello, > > Do you plan for a future release to add a graphical editor for creation of XML -> XML mappings with xslt? > Currently I'm using MapForce, but I would like to use Oxygen, because the handling is much better (from my point of view). > > Best regards, > > Ingo Freitag > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

verbose logging in dita transforms
by Ted Kuster 03 Dec '09

03 Dec '09

I've noticed that the stdout content that scrolls by when I run a DITA transform with Oxygen 11 is a lot more verbose than it was with previous Oxygen versions. I get way more info than I need. Where is the verbosity level set for that? Thanks Ted Kuster help.collab.net

3 2

Visual editor for XML file mapping (xslt)
by Ingo Freitag 03 Dec '09

03 Dec '09

Hello, Do you plan for a future release to add a graphical editor for creation of XML -> XML mappings with xslt? Currently I'm using MapForce, but I would like to use Oxygen, because the handling is much better (from my point of view). Best regards, Ingo Freitag

1 0

Special field for setting the transtype for DITA transform scenarios?
by Eliot Kimber 03 Dec '09

03 Dec '09

I have created a custom XHTML transformation type as a Toolkit plugin. In poking around the DITA transformation scenario dialog there doesn't appear to be a direct way to specify what becomes the -Dtranstype={transtype} parameter in the Java command that runs Ant. I realize I can set the parameter in the Advanced tab or use the effective ant target in the Build target field, but I think it would be helpful to have a dedicated field for custom trans types. Or have I missed something in the UI? Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 3

Modifying start parameters in Mac OS X?
by Espen S. Ore 03 Dec '09

03 Dec '09

According to the Oxygen (Oxygen 11) documentation, this should be done by right clicking the application icon in Finder. Now right clicking is not something the Mac Os X-system (10.5.8) is built for, or at least not the Mac mouse. Usually right clicking a one button Mac-mouse is done by holding down the CTRL and the Apple-key while mouseclicking. But this does not work on my Mac, there is no reaction except for selecting the file. Do I misunderstand the instructions, or is there some other way to do this? I have tried to edit the included oxygen.sh-file but this doesn't seem to do anything, I still get an errormessage about stack-memory requirements. Espen Ore Holmestrand, Norway

4 4

how to create an exclusion list from a variable?
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

HI all, i've this xml and i'm tryng to change the value of the attributes. This is what i have: <mets:div LABEL="Canto I"> <mets:div LABEL="Pagina 7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Pagina 8"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Pagina 9"> <mets:fptr FILEID="file.00012"/> </mets:div> <mets:div LABEL="Pagina 10"> <mets:fptr FILEID="file.00013"/> </mets:div> <mets:div LABEL="Pagina 11"> <mets:fptr FILEID="file.00014"/> </mets:div> <mets:div LABEL="Pagina 12"> <mets:fptr FILEID="file.00015"/> </mets:div> <mets:div LABEL="Pagina 13"> <mets:fptr FILEID="file.00016"/> </mets:div> <mets:div LABEL="Pagina 14"> <mets:fptr FILEID="file.00017"/> </mets:div> <mets:div LABEL="Pagina 15"> <mets:fptr FILEID="file.00018"/> </mets:div> <mets:div LABEL="Pagina 16"> <mets:fptr FILEID="file.00019"/> </mets:div> <mets:div LABEL="Pagina 17"> <mets:fptr FILEID="file.00020"/> </mets:div> </mets:div> this is what i would like to obtain: <mets:div LABEL="Canto I"> <mets:div LABEL="Pagina 7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Carta [1r]"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Carta [1v]"> <mets:fptr FILEID="file.00012"/> </mets:div> <mets:div LABEL="Carta [2r]"> <mets:fptr FILEID="file.00013"/> </mets:div> <mets:div LABEL="Carta [2v]"> <mets:fptr FILEID="file.00014"/> </mets:div> <mets:div LABEL="Carta [3r]"> <mets:fptr FILEID="file.00015"/> </mets:div> <mets:div LABEL="Pagina 13"> <mets:fptr FILEID="file.00016"/> </mets:div> <mets:div LABEL="Carta [3v]"> <mets:fptr FILEID="file.00017"/> </mets:div> <mets:div LABEL="Carta [4r]"> <mets:fptr FILEID="file.00018"/> </mets:div> <mets:div LABEL="Carta [4v]"> <mets:fptr FILEID="file.00019"/> </mets:div> <mets:div LABEL="Carta [5r]"> <mets:fptr FILEID="file.00020"/> </mets:div> </mets:div> Hannon helped me to create this xsl that trasforms the values of all the attributes (Michael Kay suggested me another way to do it, but it's difficult to me to use it -he uses functions and namespaces- and it doesn't work), but, now, i need to exclude some of these, in this case "Pagina 7" and "Pagina 13". How can i build an exclusion list in the variable? thank you a lot to everyone. i promise i will start to study Kay's manual early, and disturbing no more. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output indent="yes" method="xml"/> <xsl:template match="@* | node()"> <xsl:copy> <xsl:apply-templates select="@*, node()"/> </xsl:copy> </xsl:template> <xsl:template match="mets:div/@LABEL[matches(., '^Pagina [0-9]+$')]"> <xsl:variable name="n"> <xsl:number level="any" count="mets:div[@LABEL[matches(., '^Pagina [0-9]+$')]]"/> </xsl:variable> <xsl:attribute name="LABEL" select="concat('Carta [', if ($n mod 2 = 0) then concat(($n + 1) idiv 2, 'v]') else concat(($n + 1) idiv 2, 'r]'))"/> </xsl:template> </xsl:stylesheet>

1 0

new2: how to change the values of a list of attribute excluding one or more of these.
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

i confuse parts of xml, but my problem remains the same: i want to change this XML: <mets:div LABEL="Canto III" ORDER="5" ORDERLABEL="1"> <mets:div LABEL="Pagina 26" ORDER="1" ORDERLABEL="26"> <mets:fptr FILEID="file.00029"/> </mets:div> <mets:div LABEL="Pagina 27" ORDER="2" ORDERLABEL="27"> <mets:fptr FILEID="file.00030"/> </mets:div> <mets:div LABEL="Pagina 28" ORDER="3" ORDERLABEL="28"> <mets:fptr FILEID="file.00031"/> </mets:div> <mets:div LABEL="Pagina 29" ORDER="4" ORDERLABEL="29"> <mets:fptr FILEID="file.00032"/> </mets:div> <mets:div LABEL="Pagina 30" ORDER="5" ORDERLABEL="30"> <mets:fptr FILEID="file.00033"/> </mets:div> <mets:div LABEL="Pagina 31" ORDER="6" ORDERLABEL="31"> <mets:fptr FILEID="file.00034"/> </mets:div> <mets:div LABEL="Pagina 32" ORDER="7" ORDERLABEL="32"> <mets:fptr FILEID="file.00035"/> </mets:div> <mets:div LABEL="Pagina 33" ORDER="8" ORDERLABEL="33"> <mets:fptr FILEID="file.00036"/> </mets:div> <mets:div LABEL="Pagina 34" ORDER="9" ORDERLABEL="34"> <mets:fptr FILEID="file.00037"/> </mets:div> <mets:div LABEL="Pagina 35" ORDER="10" ORDERLABEL="35"> <mets:fptr FILEID="file.00038"/> </mets:div> <mets:div LABEL="Pagina 36" ORDER="11" ORDERLABEL="36"> <mets:fptr FILEID="file.00039"/> </mets:div> </mets:div> in this XML: <mets:div LABEL="Canto III" ORDER="5" ORDERLABEL="1"> <mets:div LABEL="Carta [12v]" ORDER="1" ORDERLABEL="26"> <mets:fptr FILEID="file.00029"/> </mets:div> <mets:div LABEL="Carta [13r]" ORDER="2" ORDERLABEL="27"> <mets:fptr FILEID="file.00030"/> </mets:div> <mets:div LABEL="Carta [13v]" ORDER="3" ORDERLABEL="28"> <mets:fptr FILEID="file.00031"/> </mets:div> <mets:div LABEL="Carta [14r]" ORDER="4" ORDERLABEL="29"> <mets:fptr FILEID="file.00032"/> </mets:div> <mets:div LABEL="Carta [14v]" ORDER="5" ORDERLABEL="30"> <mets:fptr FILEID="file.00033"/> </mets:div> <mets:div LABEL="Carta [15r]" ORDER="6" ORDERLABEL="31"> <mets:fptr FILEID="file.00034"/> </mets:div> <mets:div LABEL="Carta [15v]" ORDER="7" ORDERLABEL="32"> <mets:fptr FILEID="file.00035"/> </mets:div> <mets:div LABEL="Carta [16r]" ORDER="8" ORDERLABEL="33"> <mets:fptr FILEID="file.00036"/> </mets:div> <mets:div LABEL="Carta [16v]" ORDER="9" ORDERLABEL="34"> <mets:fptr FILEID="file.00037"/> </mets:div> <mets:div LABEL="Carta [17r]" ORDER="10" ORDERLABEL="35"> <mets:fptr FILEID="file.00038"/> </mets:div> <mets:div LABEL="Carta [17v]" ORDER="11" ORDERLABEL="36"> <mets:fptr FILEID="file.00039"/> </mets:div> </mets:div> this XSL doesn't work. Why? (i obtained that result in another way, not with this XSL). <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:f="http://example.com/f"> <xsl:output indent="yes" method="xml"/> <xsl:template match="@* | node()"> <xsl:copy> <xsl:apply-templates select="@*, node()"/> </xsl:copy> </xsl:template> <xsl:variable name="g" select="//mets:div[matches(@LABEL, '^Pagina [0-9]+$')]"/> <xsl:template match="*[. intersect $g]/@LABEL"> <xsl:variable name="n" select="f:index-of-node($g, ..)"/> <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> </xsl:template> <xsl:function name="f:index-of-node" as="xs:integer*"> <xsl:param name="nodes" as="node()*"/> <xsl:param name="node" as="node()"/> <xsl:sequence select="1 to count($nodes)[subsequence($nodes, ., 1) is $node]"/> </xsl:function> </xsl:stylesheet>

1 0

new: how to change the values of a list of attribute excluding one or more of these.
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

i've forgot to delete unnecessary attribute from the result XML. so, i've this xsl file suggested by mikael kay that doesn't works to change my xml that follows the xsl file. the result that i wolud obtain is posted to the end. XSL file <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:f="http://example.com/f"> <xsl:output indent="yes" method="xml"/> <xsl:template match="@* | node()"> <xsl:copy> <xsl:apply-templates select="@*, node()"/> </xsl:copy> </xsl:template> <xsl:variable name="g" select="//mets:div[matches(@LABEL, '^Pagina [0-9]+$')]"/> <xsl:template match="*[. intersect $g]/@LABEL"> <xsl:variable name="n" select="f:index-of-node($g, ..)"/> <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> </xsl:template> <xsl:function name="f:index-of-node" as="xs:integer*"> <xsl:param name="nodes" as="node()*"/> <xsl:param name="node" as="node()"/> <xsl:sequence select="1 to count($nodes)[subsequence($nodes, ., 1) is $node]"/> </xsl:function> </xsl:stylesheet> XML file <mets:div LABEL="Canto VI"> <mets:div LABEL="Pagina 56"> <mets:fptr FILEID="file.00059"/> </mets:div> <mets:div LABEL="Pagina 57"> <mets:fptr FILEID="file.00060"/> </mets:div> <mets:div LABEL="Pagina 58"> <mets:fptr FILEID="file.00061"/> </mets:div> <mets:div LABEL="Pagina 59"> <mets:fptr FILEID="file.00062"/> </mets:div> <mets:div LABEL="Pagina 60"> <mets:fptr FILEID="file.00063"/> </mets:div> <mets:div LABEL="Pagina 61"> <mets:fptr FILEID="file.00064"/> </mets:div> <mets:div LABEL="Pagina 62"> <mets:fptr FILEID="file.00065"/> </mets:div> <mets:div LABEL="Pagina 63"> <mets:fptr FILEID="file.00066"/> </mets:div> <mets:div LABEL="Pagina 64"> <mets:fptr FILEID="file.00067"/> </mets:div> <mets:div LABEL="Pagina 65"> <mets:fptr FILEID="file.00068"/> </mets:div> <mets:div LABEL="Pagina 66"> <mets:fptr FILEID="file.00069"/> </mets:div> </mets:div> XML that i would obtain <mets:div LABEL="Canto XI"> <mets:div LABEL="Pagina 59"> <mets:fptr FILEID="file.00116"/> </mets:div> <mets:div LABEL="Carta [59v]"> <mets:fptr FILEID="file.00117"/> </mets:div> <mets:div LABEL="Carta [60r]"> <mets:fptr FILEID="file.00118"/> </mets:div> <mets:div LABEL="Carta [60v]"> <mets:fptr FILEID="file.00119"/> </mets:div> <mets:div LABEL="Carta [61r]"> <mets:fptr FILEID="file.00120"/> </mets:div> <mets:div LABEL="Carta [61v]"> <mets:fptr FILEID="file.00121"/> </mets:div> <mets:div LABEL="Carta [62r]"> <mets:fptr FILEID="file.00122"/> </mets:div> <mets:div LABEL="Carta [62v]"> <mets:fptr FILEID="file.00123"/> </mets:div> <mets:div LABEL="Carta [63r]"> <mets:fptr FILEID="file.00124"/> </mets:div> <mets:div LABEL="Carta [63v]"> <mets:fptr FILEID="file.00125"/> </mets:div> <mets:div LABEL="Carta [64r]"> <mets:fptr FILEID="file.00126"/> </mets:div> </mets:div>

1 0

how to change the values of a list of attribute excluding one or more of these.
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

i've this xsl file suggested by mikael kay that doesn't works to change my xml that follows the xsl file. the result that i wolud obtain is posted to the end. XSL file <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:f="http://example.com/f"> <xsl:output indent="yes" method="xml"/> <xsl:template match="@* | node()"> <xsl:copy> <xsl:apply-templates select="@*, node()"/> </xsl:copy> </xsl:template> <xsl:variable name="g" select="//mets:div[matches(@LABEL, '^Pagina [0-9]+$')]"/> <xsl:template match="*[. intersect $g]/@LABEL"> <xsl:variable name="n" select="f:index-of-node($g, ..)"/> <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> </xsl:template> <xsl:function name="f:index-of-node" as="xs:integer*"> <xsl:param name="nodes" as="node()*"/> <xsl:param name="node" as="node()"/> <xsl:sequence select="1 to count($nodes)[subsequence($nodes, ., 1) is $node]"/> </xsl:function> </xsl:stylesheet> XML file <mets:div LABEL="Canto VI" ORDER="8" ORDERLABEL="1"> <mets:div LABEL="Pagina 56"> <mets:fptr FILEID="file.00059"/> </mets:div> <mets:div LABEL="Pagina 57"> <mets:fptr FILEID="file.00060"/> </mets:div> <mets:div LABEL="Pagina 58"> <mets:fptr FILEID="file.00061"/> </mets:div> <mets:div LABEL="Pagina 59"> <mets:fptr FILEID="file.00062"/> </mets:div> <mets:div LABEL="Pagina 60"> <mets:fptr FILEID="file.00063"/> </mets:div> <mets:div LABEL="Pagina 61"> <mets:fptr FILEID="file.00064"/> </mets:div> <mets:div LABEL="Pagina 62"> <mets:fptr FILEID="file.00065"/> </mets:div> <mets:div LABEL="Pagina 63"> <mets:fptr FILEID="file.00066"/> </mets:div> <mets:div LABEL="Pagina 64"> <mets:fptr FILEID="file.00067"/> </mets:div> <mets:div LABEL="Pagina 65"> <mets:fptr FILEID="file.00068"/> </mets:div> <mets:div LABEL="Pagina 66"> <mets:fptr FILEID="file.00069"/> </mets:div> </mets:div> XML that i would obtain <mets:div LABEL="Canto XI"> <mets:div LABEL="Pagina 59"> <mets:fptr FILEID="file.00116"/> </mets:div> <mets:div LABEL="Carta [59v]" ORDER="2" ORDERLABEL="114"> <mets:fptr FILEID="file.00117"/> </mets:div> <mets:div LABEL="Carta [60r]" ORDER="3" ORDERLABEL="115"> <mets:fptr FILEID="file.00118"/> </mets:div> <mets:div LABEL="Carta [60v]" ORDER="4" ORDERLABEL="116"> <mets:fptr FILEID="file.00119"/> </mets:div> <mets:div LABEL="Carta [61r]" ORDER="5" ORDERLABEL="117"> <mets:fptr FILEID="file.00120"/> </mets:div> <mets:div LABEL="Carta [61v]" ORDER="6" ORDERLABEL="118"> <mets:fptr FILEID="file.00121"/> </mets:div> <mets:div LABEL="Carta [62r]" ORDER="7" ORDERLABEL="119"> <mets:fptr FILEID="file.00122"/> </mets:div> <mets:div LABEL="Carta [62v]" ORDER="8" ORDERLABEL="120"> <mets:fptr FILEID="file.00123"/> </mets:div> <mets:div LABEL="Carta [63r]" ORDER="9" ORDERLABEL="121"> <mets:fptr FILEID="file.00124"/> </mets:div> <mets:div LABEL="Carta [63v]" ORDER="10" ORDERLABEL="122"> <mets:fptr FILEID="file.00125"/> </mets:div> <mets:div LABEL="Carta [64r]" ORDER="11" ORDERLABEL="123"> <mets:fptr FILEID="file.00126"/> </mets:div> </mets:div>

1 0

Re: [oXygen-user] [xsl] new: how to change value of attributes
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

your first suggestion about changes of list works fine. <xsl:template match="mets:div/@LABEL[matches(., '^Pagina [0-9]+$')]"> <xsl:variable name="n"> <xsl:number level="any" count="mets:div[@LABEL[matches(., '^Pagina [0-9]+$')]]"/> </xsl:variable> <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> </xsl:template> what can i do if i want to modify your suggestion with the new needs that you wrote to change Kay's suggestion? Or if you want to exclude the first found element then <xsl:variable name="g" select="(//mets:div[matches(@LABEL, '^Pagina [0-9]+$')])[position() gt 1]"/> i would prefer to don't add new namespaces, but to adopt linear solution even if it has more redoundancy...

1 0

Re: [oXygen-user] [xsl] new: how to change value of attributes
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

thank you Martin but but when you wrote >To define your own functions you are free to choose a >namespace but you need to choose one. i don't know how to declare my own functions. ---------- Initial Header ----------- >From : "Martin Honnen" Martin.Honnen(a)gmx.de To : xsl-list(a)lists.mulberrytech.com Cc : Date : Fri, 27 Nov 2009 18:16:26 +0100 Subject : Re: [xsl] new: how to change value of attributes > ivanmacculi(a)libero.it wrote: > > I've problems with Michael Kay suggestion: > > 1) Oxygen tells me to declare f: namespace and xs: namespace: > > <xsl:function name="f:index-of-node" as="xs:integer*">. > > The xs namespace needs to be http://www.w3.org/2001/XMLSchema so put > xmlns:xs="http://www.w3.org/2001/XMLSchema" > on your xsl:stylesheet element. > To define your own functions you are free to choose a namespace but you > need to choose one. > > > 2) <xsl:template match="*[. intersect $g]/@LABEL"> is open but not closed. Where can i close it? thank you so much. > > I think Michael's suggestion is to replace > > <xsl:template match="mets:div/@LABEL[matches(., '^Pagina [0-9]+$')]"> > <xsl:variable name="n"> > <xsl:number level="any" count="mets:div[@LABEL[matches(., > '^Pagina [0-9]+$')]]"/> > </xsl:variable> > <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = > 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> > </xsl:template> > > in the solution I posted with > > <xsl:variable name="g" select="//mets:div[matches(@LABEL, '^Pagina > [0-9]+$')]"/> > > <xsl:template match="*[. intersect $g]/@LABEL"> > <xsl:variable name="n" select="f:index-of-node($g, ..)"/> > <xsl:attribute name="LABEL" select="concat('Carta ', if ($n mod 2 = > 0) then concat(($n + 1) idiv 2, 'v') else concat(($n + 1) idiv 2, 'r'))"/> > </xsl:template> > > plus the function he posted. > > > > -- > > Martin Honnen > http://msmvps.com/blogs/martin_honnen/ > > --~------------------------------------------------------------------ > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/ > or e-mail: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> > --~-- > >

1 0

Fwd:RE: [xsl] new: how to change value of attributes
by ivanmacculi＠libero.it 27 Nov '09

27 Nov '09

I've problems with Michael Kay suggestion: 1) Oxygen tells me to declare f: namespace and xs: namespace: <xsl:function name="f:index-of-node" as="xs:integer*">. 2) <xsl:template match="*[. intersect $g]/@LABEL"> is open but not closed. Where can i close it? thank you so much. > > An idiom I have used in such cases is: > > <xsl:variable name="g" select="//mets:div[matches(@LABEL, '^Pagina > [0-9]+$')]"/> > > <xsl:template match="*[. intersect $g]/@LABEL"> > <xsl:variable name="n" select="f:index-of-node($g, .)"/> > > where > > <xsl:function name="f:index-of-node" as="xs:integer*"> > <xsl:param name="nodes" as="node()*"/> > <xsl:param name="node" as="node()"/> > <xsl:for-each select="$nodes"> > <xsl:sequence select="position()[current() is $node]"/> > </xsl:for-each> > </xsl:function> > > which still isn't ideal, but it feels a bit better. > > > Regards, > > Michael Kay > http://www.saxonica.com/ > http://twitter.com/michaelhkay > > > > > --~------------------------------------------------------------------ > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/ > or e-mail: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> > --~-- > > --~------------------------------------------------------------------ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/ or e-mail: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> --~--

1 0

Xsd to pdf, HTML
by LAUN, Wolfgang 26 Nov '09

26 Nov '09

Hi, I'm evaluating the documentation generation features (of oXygen 11.0, build 2009110412), and there are 2 questions: (1) For a complexType the PDF generated from an XML schema may contain an entry "Attributes", featuring a table with columns QName, Type, etc. Occasionally attribute names are longer than the width of the 1st column so that the text overlaps with the Type in column 2. How can this be corrected? (We could sacrifice the Fixed column.) (2) xs:annotation/documentation added to types etc. is contained in PDF and HTML output Is there a way to add markup to this text, e.g. for producing <ol>/<ul> lists and other basic formatting? Thanks Wolfgang

2 1

Re: [oXygen-user] how to change value of attributes
by ivanmacculi＠libero.it 26 Nov '09

26 Nov '09

Sorry for my english. i will try to explain you better. in another occasion i prepared this .xsl <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output indent="yes" method="xml"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 1]"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:attribute name="LABEL"> <xsl:text>Carta [</xsl:text><xsl:number count="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 1]" format="1"/>r]</xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 0]"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:attribute name="LABEL"> <xsl:text>Carta [</xsl:text><xsl:number count="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 0]" format="1"/>v]</xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> </xsl:stylesheet> in that case <mets:div LABEL="Pagina #"> was sub-element of <mets:div LABEL="testo">; instead, in this case, it's subelement of another element, like <mets:div LABEL="frontespizio". i need to select only <mets:div> elements that have LABEL="Pagina #", and change the value in LABEL="Carta". then i need to add a count of these elements: one count for even elements, one for odd elements. but it's difficult for me to select this group of element.

2 1

how to change value of attributes
by ivanmacculi＠libero.it 25 Nov '09

25 Nov '09

Hi all, i'm a librarian with a problem: i've to change the value of attribute for each element of a group that i'm not able to select and count. i've something like this: <mets:div LABEL="Testo" ORDER="4" ORDERLABEL="1"> <mets:div LABEL="Frontespizio" ORDER="1" ORDERLABEL="1"> <mets:div LABEL="Pagina 5" ORDER="1" ORDERLABEL="5"> <mets:fptr FILEID="file.00008"/> </mets:div> </mets:div> <mets:div LABEL="Dedica" ORDER="2" ORDERLABEL="1"> <mets:div LABEL="Pagina 6" ORDER="1" ORDERLABEL="6"> <mets:fptr FILEID="file.00009"/> </mets:div> </mets:div> <mets:div LABEL="Canto I" ORDER="3" ORDERLABEL="1"> <mets:div LABEL="Pagina 7" ORDER="1" ORDERLABEL="7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Pagina 8" ORDER="2" ORDERLABEL="8"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Pagina 9" ORDER="3" ORDERLABEL="9"> <mets:fptr FILEID="file.00012"/> </mets:div> </mets:div> </mets:div> i have to change the value of LABEL from "pagina 5, pagina 6, pagina 7, pagina 8, etc..." to "carta 1r, carta 1v, carta 2r, carta 2v, etc". It will be something like this: <mets:div LABEL="Testo" ORDER="4" ORDERLABEL="1"> <mets:div LABEL="Frontespizio" ORDER="1" ORDERLABEL="1"> <mets:div LABEL="Carta 1r" ORDER="1" ORDERLABEL="5"> <mets:fptr FILEID="file.00008"/> </mets:div> </mets:div> <mets:div LABEL="Dedica" ORDER="2" ORDERLABEL="1"> <mets:div LABEL="Carta 1v" ORDER="1" ORDERLABEL="6"> <mets:fptr FILEID="file.00009"/> </mets:div> </mets:div> <mets:div LABEL="Canto I" ORDER="3" ORDERLABEL="1"> <mets:div LABEL="Carta 2r" ORDER="1" ORDERLABEL="7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Carta 2v" ORDER="2" ORDERLABEL="8"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Carta 3r" ORDER="3" ORDERLABEL="9"> <mets:fptr FILEID="file.00012"/> </mets:div> </mets:div> </mets:div> thanks a lot to everyone.

3 2

how to change value of attributes
by ivanmacculi＠libero.it 25 Nov '09

25 Nov '09

Hi all, i'm a librarian with a problem: i've to change the value of attribute for each element of a group that i'm not able to select and count. i've something like this: <mets:div LABEL="Testo" ORDER="4" ORDERLABEL="1"> <mets:div LABEL="Frontespizio" ORDER="1" ORDERLABEL="1"> <mets:div LABEL="Pagina 5" ORDER="1" ORDERLABEL="5"> <mets:fptr FILEID="file.00008"/> </mets:div> </mets:div> <mets:div LABEL="Dedica" ORDER="2" ORDERLABEL="1"> <mets:div LABEL="Pagina 6" ORDER="1" ORDERLABEL="6"> <mets:fptr FILEID="file.00009"/> </mets:div> </mets:div> <mets:div LABEL="Canto I" ORDER="3" ORDERLABEL="1"> <mets:div LABEL="Pagina 7" ORDER="1" ORDERLABEL="7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Pagina 8" ORDER="2" ORDERLABEL="8"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Pagina 9" ORDER="3" ORDERLABEL="9"> <mets:fptr FILEID="file.00012"/> </mets:div> </mets:div> </mets:div> i have to change the value of LABEL from "pagina 5, pagina 6, pagina 7, pagina 8, etc..." to "carta 1r, carta 1v, carta 2r, carta 2v, etc". So the problem is that i've a order of pages with a kind of enumeration, and it will became a list of a double enumeration. each number is repeated. It will be something like this: <mets:div LABEL="Testo" ORDER="4" ORDERLABEL="1"> <mets:div LABEL="Frontespizio" ORDER="1" ORDERLABEL="1"> <mets:div LABEL="Carta 1r" ORDER="1" ORDERLABEL="5"> <mets:fptr FILEID="file.00008"/> </mets:div> </mets:div> <mets:div LABEL="Dedica" ORDER="2" ORDERLABEL="1"> <mets:div LABEL="Carta 1v" ORDER="1" ORDERLABEL="6"> <mets:fptr FILEID="file.00009"/> </mets:div> </mets:div> <mets:div LABEL="Canto I" ORDER="3" ORDERLABEL="1"> <mets:div LABEL="Carta 2r" ORDER="1" ORDERLABEL="7"> <mets:fptr FILEID="file.00010"/> </mets:div> <mets:div LABEL="Carta 2v" ORDER="2" ORDERLABEL="8"> <mets:fptr FILEID="file.00011"/> </mets:div> <mets:div LABEL="Carta 3r" ORDER="3" ORDERLABEL="9"> <mets:fptr FILEID="file.00012"/> </mets:div> </mets:div> </mets:div> in another occasion i prepared this .xsl, but in that case <mets:div LABEL="Pagina #"> was subelement of text and not subelement of another element. so this's my problem. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet exclude-result-prefixes="#all" version="2.0" xmlns:mets="http://www.loc.gov/METS/" xmlns:mix="http://www.loc.gov/mix/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rd="http://cosimo.stanford.edu/sdr/metsrights/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output indent="yes" method="xml"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 1]"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:attribute name="LABEL"> <xsl:text>Carta [</xsl:text><xsl:number count="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 1]" format="1"/>r]</xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 0]"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:attribute name="LABEL"> <xsl:text>Carta [</xsl:text><xsl:number count="mets:div[@LABEL='Testo']/mets:div[position() mod 2 = 0]" format="1"/>v]</xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="mets:div[@LABEL='Fogli di guardia posteriori']/mets:div"> <xsl:copy> <xsl:apply-templates select="@*"/> <xsl:attribute name="LABEL"> <xsl:number count="mets:div[@LABEL='Fogli di guardia posteriori']/mets:div" format="I"/></xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> </xsl:stylesheet> thanks a lot to everyone.

1 0

[Fwd: Re: Another TEI/XSL -> FO problem. Oxygen or TEI?]
by Sorin Ristache 25 Nov '09

25 Nov '09

1 0

Locating modules for MarkLogic on app server
by Lee, David 24 Nov '09

24 Nov '09

I have an XQuery file running on MarkLogic which includes a module. import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ; When I run this using ML's App Server it locates this module in the same directory as the master file. But when I try to run the xquery from within Oxygen it cant find the module. Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ? ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com <mailto:dlee@epocrates.com> 812-482-5224

4 5

Can't force DITA processor to use local DTD instead of OASIS site DTD
by Ted Kuster 24 Nov '09

24 Nov '09

(Using Oxygen 11, Eclipse plugin version, on Ubuntu 9.10, with output to Eclipse Help.) I'm trying to speed up processing by pointing to the catalog file, but it seems clear that the processor is instead going to the OASIS site. I noticed this when I suddenly started getting 403 errors from the OASIS site. Here's some OT processor output that seems to confirm my suspicion: [pipeline] [DOTJ013E][ERROR] Failed to parse the referenced file 'reference/api_cubitmethods.xml' due to below exception. Please correct the reference base on the exception message. [pipeline] Server returned HTTP response code: 403 for URL: http://docs.oasis-open.org/dita/v1.1/OS/dtd/reference.dtd Here's the catalog entry that I think should tell the processor to use the local resource before going to the OASIS site. This is copied from /com.oxygenxml.author_11.0.0/frameworks/dita/DITA-OT/catalog-dita.xml <public publicId="-//OASIS//DTD DITA Reference//EN" uri="reference.dtd"/> <public publicId="-//OASIS//DTD DITA 1.x Reference//EN" uri="reference.dtd"/> <public publicId="-//OASIS//DTD DITA 1.2 Reference//EN" uri="reference.dtd"/> And here is the setting in Preferences > Author > XML > XML Catalog that, as I understand it, points the processor to the local copy of the DTD rather than the OASIS copy: ${frameworks}/dita/catalog.xml So (leaving aside for the moment the question of why I suddenly started getting 4.3 errors from the OASIS site), what setting have I set incorrectly and how can I get the processor to use the local copy of the DTDs? Thanks Ted Kuster help.collab.net

2 1

How to get Oxygen to open files in Text view
by Ted Kuster 24 Nov '09

24 Nov '09

Under Preferences > Author > Editor > Pages, I have set the initial page to Text, then saved and restarted Eclipse. I expected that this would have the effect of making new files open in Text view. However, new files still open in Author view. Why is that, and what can I do to make my files open in Text view? Thanks Ted Kuster help.collab.net P.S. Sorry, meant to add that this is Oxygen 11 running on Ubuntu 9.10.

2 1

How to get Oxygen to open files in Text view
by Ted Kuster 23 Nov '09

23 Nov '09

Under Preferences > Author > Editor > Pages, I have set the initial page to Text, then saved and restarted Eclipse. I expected that this would have the effect of making new files open in Text view. However, new files still open in Author view. Why is that, and what can I do to make my files open in Text view? Thanks Ted Kuster help.collab.net

1 0