xmlstar-devel — XMLStarlet Toolkit Developers list

Re: [Xmlstar-devel] enhanced_select branch

[Noam P. <npo...@us...>]

André Kaplan <ak...@la...> writes:

> Hi all,
>
> I've put an "enhanced" xml select version in the 'enhanced_select'  
> branch.
>
> The most useful switches to me currently are --var, --key and -- 
> choose/--when/--otherwise. But --import might be useful also.
> The --function/--param/--call-template/--with-param needs some  
> thinking since it's too verbose to my taste.
>
> I use variables mostly for clarity, and since they can hold nodesets,  
> it makes it easier to collect data from several places in an xml  
> document (or even several times from the same place).

Is it worth adding all these options? Your example shell commands look
like XSL with shorter tags (<tagname></tagname> becomes --tagname or
-t).

>
> Here's a little script which dumps the structure of an XML document  
> and demonsrates the use of --var and --choose/--when/--otherwise  
> switches.

I couldn't get this one to work. I got a whole bunch of warnings like:

warning: failed to load external entity "b"
warning: failed to load external entity "--when"


Noam

Re: [Xmlstar-devel] XMLStarlet 1.0.3 released

[Noam P. <npo...@us...>]

"Weddington, Eric" <Eri...@at...> writes:

>> -----Original Message-----
>> From: Noam Postavsky [mailto:npo...@us...]
[...]
>> Although given that distro (eg Debian's, probably others') packages
>> link with shared libraries,
>> perhaps insisting on static linking isn't worthwhile.
>> 
>
>
> Note that static linking is preferred when building for Windows
> (host=mingw). It makes it easier to redistribute.

Well yes, what I meant was it's not worth the trouble of putting code in
configure to compute /path/to/libxml.a, when -lxml would work fine. When
building the Windows release I didn't build the shared libraries so
using -lxml there would link with libxml.a anyways.

Noam

Re: [Xmlstar-devel] [SOLVED] parsing problem

[msacks <nt...@gm...>]

This does the trick. Thank you.


On Sat, Nov 20, 2010 at 5:16 PM, André Kaplan <ak...@la...> wrote:
>
>> Le 21 nov. 10 à 00:42, msacks a écrit :
>>
>>
>> I did try the various combinations you recommended. i.e.
>>
>> xmlstarlet sel -t -c "//category/....
>> "/category
>> "category
>>
>> So there must be something else I'm missing here.
>>
>>
>> On Fri, Nov 19, 2010 at 4:17 PM, André Kaplan <ak...@la...>
>> wrote:
>>>> On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
>>>>> Hello,
>>>>> I am having trouble doing some really basic things using xmlstar.
>>>>> I am executing this command  /usr/bin/xmlstarlet sel -t -c
>>>>> "category/structure/property[@name='productNumber']" -v "@value"
>>>>> ~user/Downloads/hp.USE808N6DS.xml
>>>>>
>
>
> Yes, there are no name attribute with 'productNumber' as value in your
> example.
> There are 'productName', there are 'serialNumber', so you have to make
> a choice!
>
> $ xmlstarlet sel \
>     --text \
> -t \
> -m "//category/structure/property[@name='productName']" \
>     -v '@value' -n \
> -b \
> -b \
> hp.USE808N6DS.xml
> ProLiant DL580 G5
> ProLiant DL580 G5
> ProLiant DL580 G5
>
> Regards,
> André
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> _______________________________________________
> xmlstar-devel mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlstar-devel
>

[Xmlstar-devel] enhanced_select branch

[André K. <ak...@la...>]

Hi all,

I've put an "enhanced" xml select version in the 'enhanced_select'  
branch.

The most useful switches to me currently are --var, --key and -- 
choose/--when/--otherwise. But --import might be useful also.
The --function/--param/--call-template/--with-param needs some  
thinking since it's too verbose to my taste.

I use variables mostly for clarity, and since they can hold nodesets,  
it makes it easier to collect data from several places in an xml  
document (or even several times from the same place).

A basic example (multiplication tables above 2)
$ cat a.xml
<x>
<n>0</n>
<n>1</n>
<n>2</n>
<n>3</n>
<n>4</n>
<n>5</n>
<n>6</n>
<n>7</n>
<n>8</n>
<n>9</n>
</x>

$ cat a.xml \
| xml sel \
     --text \
     --var numbers='//n' \
-t \
-m '$numbers[. >= 2]' \
     --var i='.' \
     -o '== Multiplication table of ' -v '$i' -o ' ==' -n \
     -m '$numbers' \
         --var j='.' \
         -v '$i' -o ' * ' -v '$j' -o ' = ' -v '$i * $j' -n \
     -b \
-b \
-b
== Multiplication table of 2 ==
2 * 0 = 0
2 * 1 = 2
2 * 2 = 4
2 * 3 = 6
2 * 4 = 8
...
== Multiplication table of 9 ==
...
9 * 6 = 54
9 * 7 = 63
9 * 8 = 72
9 * 9 = 81

Here's a little script which dumps the structure of an XML document  
and demonsrates the use of --var and --choose/--when/--otherwise  
switches.

$ cat struct.sh
#!/bin/sh

struct() {
     "${xml:-xml}" sel \
         "$@" \
         --text \
         --var empty="''" \
         --var dot="'.'" \
         --var plus="'+'" \
     -t \
         --var nl -n -b \
         --var PI   -o 'PI  ' -b \
         --var comm -o 'Comm' -b \
         --var text -o 'Text' -b \
         --var NS   -o 'NS  ' -b \
         --var attr -o 'Attr' -b \
         --var elem -o 'Elem' -b \
         --var root -o 'Root' -b \
         --var NA   -o 'N/A ' -b \
     -m '/|//node()|//@*' \
         --var path \
             -o '/' \
             -m 'ancestor-or-self::*' \
             -i 'position() > 1' -o '/' -b \
             -v 'name()' \
             -b \
         -b \
         --var indent \
             -m 'ancestor-or-self::*' -v '$plus' -b \
             -m 'ancestor-or-self::*' -v 'concat($dot, $dot, $dot)' -b \
         -b \
         --var type \
             --var ns='../namespace::*' \
             --choose \
                 --when './self::processing-instruction()' -v '$PI'   - 
b \
                 --when 'count(.|$ns) = count($ns)'        -v '$NS'   - 
b \
                 --when './self::comment()'                -v '$comm' - 
b \
                 --when './self::text()'                   -v '$text' - 
b \
                 --when 'count(.|../@*) = count(../@*)'    -v '$attr' - 
b \
                 --when './self::*'                        -v '$elem' - 
b \
                 --when 'not(./parent::*)'                 -v '$root' - 
b \
                 --otherwise -v '$NA' -b \
             -b \
         -b \
         --choose \
             --when '$type = $PI' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v 'name()' -o '][' -v '.' \
                 -o ']' -n \
             -b \
             --when '$type = $comm' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v '.' -o ']' -n \
             -b \
             --when '$type = $text' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v '$path' -o '][' -v 'str:replace(., $nl,  
&quot;\n&quot;)' -o ']' -n \
             -b \
             --when '$type = $attr' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v '$path' -o '][@' -v 'name()' -o '][' -v '.'  
-o ']' -n \
             -b \
             --when '$type = $root' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v '$path' -o ']' -n \
             -b \
             --when '$type = $elem' \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -v '$path' -o ']' \
                 -n \
                 --var nslist \
                     -m 'namespace::*[name() != &quot;xml&quot;]' \
                     -s 'A:T:U' 'name()' \
                         -i 'position() > 1' -o ', ' -b \
                         --choose \
                             --when 'name() = $empty' -o '<def>' -b \
                             --otherwise -v 'name()' -b \
                         -b \
                         -o '=' -v '.' \
                     -b \
                 -b \
                 -o 'NS  ' -o ': ' -v '$indent' \
                 -o '[' -v '$path' -o '][' -v '$nslist' -o ']' -n \
             -b \
             --otherwise \
                 -v '$type' -o ': ' -v '$indent' \
                 -o '[' -c '.' -o ']' -n \
             -b \
         -b \
     -b
}


struct "$@"

$ cat eg.xml
<?xml version="1.0"?>
<?pi  value="3.141592"?>
<x xmlns="http://a.org">
   <!-- Sample -->
   <t id="1">Text 1 <b>Text 2</b> Text 3</t>
   <t id="2">
Multi
       Line
            Text
</t>
   <ns xmlns:b="http://b.net" xmlns:c="http://c.com">
     <b:s>1</b:s>
     <c:s>2</c:s>
   </ns>
</x>

$ cat eg.xml | struct.sh
Root: [/]
PI  : [pi][value="3.141592"]
Elem: +...[/x]
NS  : +...[/x][<def>=http://a.org]
Text: +...[/x][\n  ]
Comm: +...[ Sample ]
Text: +...[/x][\n  ]
Elem: ++......[/x/t]
NS  : ++......[/x/t][<def>=http://a.org]
Attr: ++......[/x/t][@id][1]
Text: ++......[/x/t][Text 1 ]
Text: +...[/x][\n  ]
Elem: +++.........[/x/t/b]
NS  : +++.........[/x/t/b][<def>=http://a.org]
Text: +++.........[/x/t/b][Text 2]
Text: ++......[/x/t][ Text 3]
Elem: ++......[/x/t]
NS  : ++......[/x/t][<def>=http://a.org]
Attr: ++......[/x/t][@id][2]
Text: ++......[/x/t][\nMulti\n      Line\n           Text\n]
Text: +...[/x][\n  ]
Elem: ++......[/x/ns]
NS  : ++......[/x/ns][<def>=http://a.org, b=http://b.net, c=http:// 
c.com]
Text: ++......[/x/ns][\n    ]
Text: +++.........[/x/ns/b:s][1]
Text: ++......[/x/ns][\n    ]
Elem: +++.........[/x/ns/c:s]
NS  : +++.........[/x/ns/c:s][<def>=http://a.org, b=http://b.net, c=http://c.com 
]
Text: +++.........[/x/ns/c:s][2]
Text: ++......[/x/ns][\n  ]
Text: +...[/x][\n]
Elem: +++.........[/x/ns/b:s]
NS  : +++.........[/x/ns/b:s][<def>=http://a.org, b=http://b.net, c=http://c.com 
]

Note there seems to be a misplaced 'Text: +...[/x][\n  ]' right after  
'Text: ++......[/x/t][Text 1 ]'
It should be right after 'Text: ++......[/x/t][ Text 3]' but probably  
the order of nodes in a nodeset is not guaranteed.

With other XSLT processors, the result may be different.

I can provide some examples on how to use key and function switches.

Regards,
André

Re: [Xmlstar-devel] XMLStarlet 1.0.3 released

[Noam P. <npo...@us...>]

On Sat, Nov 20, 2010 at 6:55 PM, André Kaplan <ak...@la...> wrote:
> Is there a reason with xmlstarlet is linked statically?
>
> Regards,
> André

According to
http://sourceforge.net/tracker/index.php?func=detail&aid=820996&group_id=66612&atid=515109

> I'm not planning to support linking with shared libraries.
> I think having it statically liked make it self contained,
> and easier
> to handle for a user.
> It also helps to avoid incomatibility problems in cases when
> shared libraries are upgraded. Binaries which are released
> pass regression testing with particular version of libxml2
> and libxslt.

> Thanks
> --MG

Although given that distro (eg Debian's, probably others') packages
link with shared libraries,
perhaps insisting on static linking isn't worthwhile.

Noam

Re: [Xmlstar-devel] parsing problem

[André K. <ak...@la...>]

> Le 21 nov. 10 à 00:42, msacks a écrit :
>
>
> I did try the various combinations you recommended. i.e.
>
> xmlstarlet sel -t -c "//category/....
> "/category
> "category
>
> So there must be something else I'm missing here.
>
>
> On Fri, Nov 19, 2010 at 4:17 PM, André Kaplan <ak...@la...>  
> wrote:
>>> On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
>>>> Hello,
>>>> I am having trouble doing some really basic things using xmlstar.
>>>> I am executing this command  /usr/bin/xmlstarlet sel -t -c
>>>> "category/structure/property[@name='productNumber']" -v "@value"
>>>> ~user/Downloads/hp.USE808N6DS.xml
>>>>


Yes, there are no name attribute with 'productNumber' as value in your  
example.
There are 'productName', there are 'serialNumber', so you have to make  
a choice!

$ xmlstarlet sel \
     --text \
-t \
-m "//category/structure/property[@name='productName']" \
     -v '@value' -n \
-b \
-b \
hp.USE808N6DS.xml
ProLiant DL580 G5
ProLiant DL580 G5
ProLiant DL580 G5

Regards,
André

Re: [Xmlstar-devel] XMLStarlet 1.0.3 released

[André K. <ak...@la...>]

>
> Sorry about that, I should have removed autogen.sh, just use
> $ autoreconf -si
>

No problem, I was focusing on my branch and getting to know git.
But this looks nicer with autoreconf.
Is there a reason with xmlstarlet is linked statically?

Regards,
André

Re: [Xmlstar-devel] parsing problem

[msacks <nt...@gm...>]

I did try the various combinations you recommended. i.e.

xmlstarlet sel -t -c "//category/....
"/category
"category

So there must be something else I'm missing here.


On Fri, Nov 19, 2010 at 4:17 PM, André Kaplan <ak...@la...> wrote:
>> On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
>>> Hello,
>>> I am having trouble doing some really basic things using xmlstar.
>>> I am executing this command  /usr/bin/xmlstarlet sel -t -c
>>> "category/structure/property[@name='productNumber']" -v "@value"
>>> ~user/Downloads/hp.USE808N6DS.xml
>>>
>>> against this xml file
>>> https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&sort=name&layout=list&num=50
>>>
>>> Can someone clue me in as to what I am doing wrong?
>>
>> You didn't explain exactly what your intention is, but I suppose you
>> meant @value to refer to the property element that you matched in the
>> previous argument. Unless you use -m (or --match) arguments are
>> relative to the root, I would guess you want this:
>>
>> /usr/bin/xmlstarlet sel -t -m \
>> "category/structure/property[@name='productNumber']" \
>> -c . -v "@value" ~user/Downloads/hp.USE808N6DS.xml
>>
>
> Hi msacks,
>
> Well the two things to check since I also haven't been able to
> download the xml file:
> - I guess xmlstarlet sel -t -m "/category/..." or xmlstarlet sel -t -m
> "//category/..." (note the staring slash(es)) would match something
> - Is there a namespace, in which case you'd have to use the -N option
> and update the XPath accordingly?
>
> Regards,
> André
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> _______________________________________________
> xmlstar-devel mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlstar-devel
>

Re: [Xmlstar-devel] parsing problem

[msacks <nt...@gm...>]

Try this link https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&hl=en&authkey=CNfli4oJ



On Fri, Nov 19, 2010 at 4:17 PM, André Kaplan <ak...@la...> wrote:
>> On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
>>> Hello,
>>> I am having trouble doing some really basic things using xmlstar.
>>> I am executing this command  /usr/bin/xmlstarlet sel -t -c
>>> "category/structure/property[@name='productNumber']" -v "@value"
>>> ~user/Downloads/hp.USE808N6DS.xml
>>>
>>> against this xml file
>>> https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&sort=name&layout=list&num=50
>>>
>>> Can someone clue me in as to what I am doing wrong?
>>
>> You didn't explain exactly what your intention is, but I suppose you
>> meant @value to refer to the property element that you matched in the
>> previous argument. Unless you use -m (or --match) arguments are
>> relative to the root, I would guess you want this:
>>
>> /usr/bin/xmlstarlet sel -t -m \
>> "category/structure/property[@name='productNumber']" \
>> -c . -v "@value" ~user/Downloads/hp.USE808N6DS.xml
>>
>
> Hi msacks,
>
> Well the two things to check since I also haven't been able to
> download the xml file:
> - I guess xmlstarlet sel -t -m "/category/..." or xmlstarlet sel -t -m
> "//category/..." (note the staring slash(es)) would match something
> - Is there a namespace, in which case you'd have to use the -N option
> and update the XPath accordingly?
>
> Regards,
> André
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> _______________________________________________
> xmlstar-devel mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlstar-devel
>

Re: [Xmlstar-devel] XMLStarlet 1.0.3 released

[André K. <ak...@la...>]

> I just released version 1.0.3
>
> - Bug fixes:
>    escape --value in update mode (Bug 3052978)
>    c14n now includes default attributes (Bug 1505579)
>    Allow special characters in sel --output literal (Bug 1912978)
>    remove warning from xml_trans.c (Bug 1521756)
>    Use xmlReader interface so line numbers are 32-bit (Bug 1219072)
>    test for error messages on lines past 2^16 (Bug 1219072)
>    don't look for embedded dtd if not asked (Bug 1167215)
>

Congratulation!
I created a branch to put my "enhanced" version of xml_select.c.
I'm currently unable to regenerate a working configure file from the  
updated autotools scripts.
I'm on MacOSX.

Could you provide me some hints on how to regenerate them?
I assumed
$ NOCONFIGURE=1 ./autogen.sh
would be sufficient.

I'm currently having
./configure: line 2754: syntax error near unexpected token `LIBXML,'
./configure: line 2754: `XSTAR_LIB_ARGS_WITH(LIBXML, with-src)'

Regards,
André

Re: [Xmlstar-devel] parsing problem

[André K. <ak...@la...>]

> On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
>> Hello,
>> I am having trouble doing some really basic things using xmlstar.
>> I am executing this command  /usr/bin/xmlstarlet sel -t -c
>> "category/structure/property[@name='productNumber']" -v "@value"
>> ~user/Downloads/hp.USE808N6DS.xml
>>
>> against this xml file
>> https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&sort=name&layout=list&num=50
>>
>> Can someone clue me in as to what I am doing wrong?
>
> You didn't explain exactly what your intention is, but I suppose you
> meant @value to refer to the property element that you matched in the
> previous argument. Unless you use -m (or --match) arguments are
> relative to the root, I would guess you want this:
>
> /usr/bin/xmlstarlet sel -t -m \
> "category/structure/property[@name='productNumber']" \
> -c . -v "@value" ~user/Downloads/hp.USE808N6DS.xml
>

Hi msacks,

Well the two things to check since I also haven't been able to  
download the xml file:
- I guess xmlstarlet sel -t -m "/category/..." or xmlstarlet sel -t -m  
"//category/..." (note the staring slash(es)) would match something
- Is there a namespace, in which case you'd have to use the -N option  
and update the XPath accordingly?

Regards,
André

Re: [Xmlstar-devel] parsing problem

[Noam P. <npo...@us...>]

On Fri, Nov 19, 2010 at 3:59 PM, msacks <nt...@gm...> wrote:
> Hello,
> I am having trouble doing some really basic things using xmlstar.
> I am executing this command  /usr/bin/xmlstarlet sel -t -c
> "category/structure/property[@name='productNumber']" -v "@value"
> ~user/Downloads/hp.USE808N6DS.xml
>
> against this xml file
> https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&sort=name&layout=list&num=50
>
> Can someone clue me in as to what I am doing wrong?

You didn't explain exactly what your intention is, but I suppose you
meant @value to refer to the property element that you matched in the
previous argument. Unless you use -m (or --match) arguments are
relative to the root, I would guess you want this:

/usr/bin/xmlstarlet sel -t -m \
  "category/structure/property[@name='productNumber']" \
  -c . -v "@value" ~user/Downloads/hp.USE808N6DS.xml

Noam

PS I was unable do download your xml file, I got:

Sorry, the page (or document) you have requested is not available.

[Xmlstar-devel] parsing problem

[msacks <nt...@gm...>]

Hello,
I am having trouble doing some really basic things using xmlstar.
I am executing this command  /usr/bin/xmlstarlet sel -t -c
"category/structure/property[@name='productNumber']"  -v "@value"
~user/Downloads/hp.USE808N6DS.xml

against this xml file
https://docs.google.com/leaf?id=0B6C4Iz1C9X9HMzVjNjRiMTYtZWM3YS00ODljLTgyM2EtMDNjYzIzZjVhYTE2&sort=name&layout=list&num=50

Can someone clue me in as to what I am doing wrong?

Re: [Xmlstar-devel] XmlStarlet User's Guide

[Noam P. <npo...@us...>]

On Tue, Nov 16, 2010 at 10:28 AM, André Kaplan <ak...@la...> wrote:
> Hi,
>
> Is there anything in the codebase to generate the documentation from
> the DocBook user's guide?
>
> I've been able to generate a good enough version, but some minor
> tweaks (like chapter numbering) are needed hence my question.

The following call produced identical (as far as I could tell) output:

xsltproc -o xmlstarlet-ug.html \
    --param section.autolabel 1 \
    --stringparam generate.toc 'book toc,title' \
    --stringparam html.stylesheet html.css \
    /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl \
    xmlstarlet-ug.xml

I installed the docbook-xsl package for the stylesheet.

Noam

[Xmlstar-devel] XMLStarlet 1.0.3 released

[Noam P. <npo...@us...>]

Hi list,

I just released version 1.0.3

   - Bug fixes:
      escape --value in update mode (Bug 3052978)
      c14n now includes default attributes (Bug 1505579)
      Allow special characters in sel --output literal (Bug 1912978)
      remove warning from xml_trans.c (Bug 1521756)
      Use xmlReader interface so line numbers are 32-bit (Bug 1219072)
      test for error messages on lines past 2^16 (Bug 1219072)
      don't look for embedded dtd if not asked (Bug 1167215)

Noam

[Xmlstar-devel] XmlStarlet User's Guide

[André K. <ak...@la...>]

Hi,

Is there anything in the codebase to generate the documentation from  
the DocBook user's guide?

I've been able to generate a good enough version, but some minor  
tweaks (like chapter numbering) are needed hence my question.

Required packages: docbook-xsl, fop > 0.9

$ xsltproc \
     --output xmlstarlet-ug-new.fo \
     --stringparam  paper.type  A4 \
     --stringparam  fop1.extensions 1 \
/path/to/fo/docbook.xsl \
xmlstarlet-ug.xml

$ fop -fo xmlstarlet-ug-new.fo -pdf xmlstarlet-ug-new.pdf

If you generate from the master version, you'll see it's a bit  
different from the currently bundled version.

Regards,
André

Re: [Xmlstar-devel] xmlstarlet status - not dead :)

[Noam P. <npo...@us...>]

On Sun, Nov 14, 2010 at 8:44 PM, André Kaplan <ak...@la...> wrote:
> Hi Noam,
>
> I'm also registered as a xmlstarlet developer.
> I'm monitoring what you've been working on these days.
>
> Could you briefly explain what you're doing?
> It looks like you're trying to close all open tickets and fixing some
> bugs, correct me if I'm wrong.

Exactly right, the ticket system isn't useful if it's filled with open,
spurious tickets. I fixed what I consider to be straightforward and
simple-to-fix bugs.

> Are you targeting for a bug fix release like 1.0.3 soon?

Yes, I'm working on cleaning up the build script and as soon as
that's done I'll release 1.0.3.

> I have a small bug fix for xml fo, I added an option to support input
> encoding.
>
> Once this is done do you have other plans?

Nothing definite, some of the suggestions in the Feature Requests tracker
look good.

> As for me, I made many changes to the xmlstarlet code base (mainly xml
> sel and ed).
> My first goal is to put everything I've done in a git branch, so that
> we can have some concrete matter to discuss with you, Dago, Mikhail
> (if he's still around) and possibly others and then integrate new
> features.
>
> Eventually, xml sel and ed will be completely rewritten.

Awesome, xml_select.c is a total mess.

Noam

[Xmlstar-devel] xmlstarlet status - not dead :)

[André K. <ak...@la...>]

Hi Noam,

> I thought I'd send this out because there hasn't been an answered
> question in the archives for several years, which is kind of
> discouraging to someone with a question.
>
> So rest assured potential question-asker, I am fixing bugs and
> will endeavour to answer your question(s). :)

I'm also registered as a xmlstarlet developer.
I'm monitoring what you've been working on these days.

Could you briefly explain what you're doing?
It looks like you're trying to close all open tickets and fixing some  
bugs, correct me if I'm wrong.
Are you targeting for a bug fix release like 1.0.3 soon?

I have a small bug fix for xml fo, I added an option to support input  
encoding.

Once this is done do you have other plans?

As for me, I made many changes to the xmlstarlet code base (mainly xml  
sel and ed).
My first goal is to put everything I've done in a git branch, so that  
we can have some concrete matter to discuss with you, Dago, Mikhail  
(if he's still around) and possibly others and then integrate new  
features.

Eventually, xml sel and ed will be completely rewritten.

Regards,
André

[Xmlstar-devel] xmlstarlet status - not dead :)

[Noam P. <npo...@us...>]

Hello list,

I thought I'd send this out because there hasn't been an answered
question in the archives for several years, which is kind of
discouraging to someone with a question.

So rest assured potential question-asker, I am fixing bugs and
will endeavour to answer your question(s). :)

Noam

[Xmlstar-devel] xsl:text in entity

[Ronny O. <ob...@vh...>]

Dear xmlstar-devel list,

sorry for bothering you, but I didn't find any useful hints via google, 
nor did I find anything in the xmlstarlet archieve.

I'de like to use the entity-technique for whitspace like it is described 
in http://www.xml.com/pub/a/2001/12/05/whitespace.html . But when using 
the <xsl:text> element inside of the entities (3rd last xsl-stylesheet), 
I'll receive the following output:

$ xml tr stylesheet.xsl employee.xml
namespace error : Namespace prefix xsl on text is not defined
<xsl:text>
         ^
namespace error : Namespace prefix xsl on text is not defined
<xsl:text> </xsl:text>
         ^
09/01/1998JohnnyHerbert


I found a hint on 
http://techtonik.rainforce.org/2006/07/xslt-whitespaces-beautifying.html 
to ship around these errors, with the result of not seeing the 
"namespace error" output anymore, but still with a wrong format (there 
are no whitespaces between the three elements).

The xslt processor xsltproc did quite the same as xmlstarlet (1.0.1). 
Probably, because both are using the same library(?).

Xalan-C 1.10.0 (with Xerces version 2.7.0), another xslt processor, 
works fine with these files, it creates the expected output. But I can't 
use this processor, because it doesn't handle <exsl:document>, which I 
need in other stylesheets.

On http://www.xml.com/pub/a/2001/12/05/whitespace.html?page=2 an 
interessting comment is posted, which could point out a lack of 
xmlstarlet(?):

Sample problem <http://www.xml.com/cs/user/view/cs_msg/414>
2002-02-11 07:12:07 Antonio del Pozzo [Reply] 
<http://www.xml.com/cs/user/create/cs_msg?x-lr=cs_msg/414&x-lr2=a/882>

The article is very interesting. Nevertheless, when try to execute the 
samples I get error that tell me "Reference to undeclared namespace 
prefix: 'xsl' ". I use MSXML 3.0 on W2K, what's wrong?
Thanks in advance
Antonio

Sample problem <http://www.xml.com/cs/user/view/cs_msg/420>
2002-02-13 14:00:33 Bob DuCharme [Reply] 
<http://www.xml.com/cs/user/create/cs_msg?x-lr=cs_msg/420&x-lr2=a/882>

As I told Meili in a private e-mail, the example work properly with XSLT 
processors that completely conform to the XSLT Recommendation such as 
Xalan and Xerces, but Microsoft's processors don't always conform,and 
this is the kind of problem that can come up.


http://www.vbxml.com/xsl/XSLTRef.asp has a good chart showing where each 
release of the Microsoft processors are and aren't compliant. I don't 
know if there's anything about the elements used to control whitespace 
there.


Bob


So, does anyone got another hint or any explanation what's going wrong?
Probably Xalan-Java, the java version, works fine with these entities 
and also the <exsl:document> element. But I don't want to use it, 
because of...well...it's java ;)

Regards
Ronny

BTW: I ran all the transformations under Win XP in cygwin.

[Xmlstar-devel] ArrayIndexOutOfBoundsException Exception in SAX

[<sik...@cc...>]

How to fix this Exception "ArrayIndexOutOfBoundsException" probably from

myPaser.parser(new File(argv[]), myHandler)

Do I need more space in my computer to parse the XML file?
Who cares please?

Smart Ikhu-Omoregbe

[Xmlstar-devel] Mac OS X (10.4.7) build, patch included

[Rick v. d. Z. <ri...@th...>]

Hi,

mac is using .dylib instead of the normal .a, so the config/makefile 
needs to look for it too.
Patch attached, will fix the problem.

Cheerz,
Rick

[Xmlstar-devel] option: "--input-file=<xml-input-file>"

[Tylman U. <t....@gm...>]

(apologies for multiple copies - it seems the first got stuck)


Dear all!

XMLStarlet is an excellent tool - I ran across it recently and started 
to use it quite heavily soon afterwards.  It provides the kind of 
glue that I was missing between line-based Unix Piping and XML.


I wonder, though, how you can utilise "xml sel" in the following 
scenario:
- one big XML file ("data.xml")
- a list of words, one per line, in a plain text file ("words")

task: select something from the XML file for each word, e.g.

for WORD in `cat words`; do
  xml sel -t -m "//word[@form='$WORD']" -v 'text()' -n data.xml;
done

This is o.k., but very inefficient: you'll have to load data.xml once 
for each word.  If data.xml is very large and the list of words is 
long, this can become tedious rather quickly.  This line of argument 
also holds for inserting data with "xml ed" etc.


Alternatively, you could use "xargs".  I often use it to speed up 
similar scenarios: feed one program with many ops to carry out at 
once, instead of restarting it over and over again.  However, you run 
into a problem with "xml sel", because the input file has to be 
either on STDIN or the *last* argument on the command line.  

With an option like "--input-file=<xml-input-file>" you could write:
(the rather cryptic perl one-liner constructs one select expression 
per line in "words")

cat words \
| perl -pe 'chomp; s!^!-t -m "//word[@form=&quot;!; s!$!&quot;]" -v 
"text()" -n\x00!' \
| xargs -0 xml sel --input-file=data.xml

This would construct a command line consisting of as many operations 
as fit in one call, and only repeat the command when there are too 
many operations.  It seems that XMLStarlet scales well with that many 
options internally according to some tests I did.  

For the moment, I resort to a wrapper that just filters out 
"--input-file=<file>" and leaves the rest unchanged, which is not 
very elegant.  What is more, it is problematic exactly for very long 
lines, where it is not clear if the filename will still fit on the 
line.  BTW I got the idea from the option "--target-directory=<dir>" 
of "mv" to specify the target dir, which I found useful for similar 
reasons.

I might be able to dig into the sources and provide a patch, but I was 
interested to hear your opinion first - and whether I did not notice 
any obvious solutions.  I'd be happy to hear any thoughts on this.


Thanks,
Tylman

[Xmlstar-devel] Re: option: "--input-file=<xml-input-file>"

[Tylman U. <t....@gm...>]

On 12/7/05, you wrote:
>  xargs -i (or xargs --replace) allow the substituted argument to be
>  inside the call string.

Unfortunately, "-i" implies "-l1", i.e. only one line can be used as 
an argument per call.  Which was my original problem.

It also implies -x, i.e. to exit when the args do not fit on a line.  
Maybe this is all theoretic (20k chars allowed), and you could 
construct the full sequence of ops to carry out in advance, and pass 
them as a single argument to XMLStarlet.  Let's see...

Did some tests along these lines, and it seems that XMLStarlet does 
not recognise the individual operations when they are passed as a 
string containing many options.  It returns "error in arguments: no 
-t or --template options found".  

Like in:

me@host:~> xml sel '-t -m "//sth" -v "text()" -n' data.xml
error in arguments: no -t or --template options found

I know this is more of an xargs problem than an XMLStarlet problem, 
but it is just sooo appealing to use xargs with it.


Thanks,
Tylman

Re: [Xmlstar-devel] option: "--input-file=<xml-input-file>"

[Alexandre R. <ara...@gm...>]

No help doing this all within xargs, but....

On 12/7/05, Tylman Ule <t....@gm...> wrote:
> Alternatively, you could use "xargs".  I often use it to speed up
> similar scenarios: feed one program with many ops to carry out at
> once, instead of restarting it over and over again.  However, you run
> into a problem with "xml sel", because the input file has to be
> either on STDIN or the *last* argument on the command line.

xargs -i (or xargs --replace) allow the substituted argument to be
inside the call string.

Regards,
   Alex.