November 2009 - oXygen-user - www.oxygenxml.com

Selecting multiple XML file at once for the Schema Converter (trang)
by mozer 02 Jun '11

02 Jun '11

Hi, Problably I didn't see it, but there is no way for me to select a bunch of XML file and add them to generate a schema The only way is too select the file one by one which is tedious Any idea of how to circumvent that ? Xmlizer

3 10

Embedding fonts in Oxygen for FOP
by Mark Wilson 19 Feb '10

19 Feb '10

I am trying to embed a font containing Czech glyphs. Following Oxygen's instructions to embed a font in FOP for pdf output: On my Windows Vista system, with Apache FOP 0.95 and Oxygen 10.1, when I run ttfConvert.bat (see below), I get the error: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/fop/fonts/apps/TTFReader Caused by: java.lang.ClassNotFoundException: org.apache.fop.fonts.apps.TTFReader. When I look in that directory, there is an html file with that name, but no Java file. I do note at the head of the Oxygen document, it says for the built in FOP, but there is no org.apache... sub directory under oxygen Can you help? Thanks, Mark set LIB=lib set CMD=java -cp "%LIB%\fop.jar;%LIB%\avalon-framework-4.2.0.jar set CMD=%CMD%;%LIB%\xml-apis.jar;%LIB%\xercesImpl.jar;%LIB%\xalan.jar set CMD=%CMD%;%LIB%\serializerOxygen.jar" org.apache.fop.fonts.apps.TTFReader set FONT_DIR=C:\Windows\Fonts %CMD% %FONT_DIR%\Tleeur.ttf TLEastEurope.xml

3 3

Saxon configurations
by Wendell Piez 25 Dec '09

25 Dec '09

Hi, Among the recent changes in Saxon 9.2, the way it sets up support for numbering in languages other than English has changed. It comes with classes for German, French, Danish, Dutch and some others, but none of these work without being configured. The configuration is done by providing Saxon at runtime with a configuration file, or by modifying a class. Maybe oXygen hasn't caught up yet with these changes in Saxon, or maybe I don't know where to look, but I can't see where I can create or modify such a configuration file for Saxon in oXygen. Any ideas? Thanks, 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 8

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

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