public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Galevsky <galevsky@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: An XML Question
Date: Tue, 29 May 2007 11:25:06 +0200	[thread overview]
Message-ID: <d5cfc3af0705290225h7496410br1878e2e57405acce@mail.gmail.com> (raw)
In-Reply-To: <AA0639A1EB70AE409130258CE7BDC3183237F7@messenger.cv63.navy.mil>

Well, a "man libxml2" gives you all that you need:

 Documentation   for   libxml   is   available   on-line   at
     http://www.xmlsoft.org/

;o)

Gal'

2007/5/29, burlingk@cv63.navy.mil <burlingk@cv63.navy.mil>:
>
>
> > -----Original Message-----
> > From: Galevsky [mailto:galevsky@gmail.com]
> > Sent: Tuesday, May 29, 2007 4:21 PM
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] OT: An XML Question
> >
> >
> > Hi,
> >
> > you can learn the xml concepts at http://www.w3schools.com/.
> > Then, depending on the language you choose, there is lots of
> > libs to deal with xml in many languages. Though you always
> > have two different ways of parsing your xml file: a SAX
> > parser approach, that runs on an element-by-element process,
> > retrieving each element with no view on the next ones. The
> > second way is a DOM object builder, parsing the xml file as a
> > whole, then giving you back the whole tree as an object that
> > can browse later with a set of methods. The later is faster
> > to get all the information of the xml, but takes more memory
> > since the whole xml tree must be built first. You have to
> > look for the libs of your language now for further details,
> > but the choice between the two is crucial. I remind a
> > Xmlchecker java tool I wrote to run no-diff tests.... I
> > implemented first with jdom, and it was good..... until I had
> > to deal with 300 Mb files ... and rewrite the whole browsing
> > engine with SAX.
> >
> > Gal'
> >
> >
> > 2007/5/29, burlingk@cv63.navy.mil <burlingk@cv63.navy.mil>:
> > >
> > >
> > > Are there any really  good XML tutorials on the web, or
> > perhaps a book
> > > that is actually  useful?
> <snip>
>
> Thanks for the info!
> I think I may look into the DOM approach. ^_^
> Does(do?) libxml or libxml2 have a DOM interface?  I know that
> libxml2 is already on the system (part of the base install), so
> it may be a good place to look. :)  Does anyone know of a good
> tutorial site with a .org or .edu web address?  The firewall I
> am stuck behind at the moment has some funky restrictions. :P
>
> ^_^
>
> --
> gentoo-user@gentoo.org mailing list
>
>
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-29  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  9:15 [gentoo-user] OT: An XML Question burlingk
2007-05-29  9:25 ` Galevsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-29  1:00 burlingk
2007-05-29  7:21 ` Galevsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d5cfc3af0705290225h7496410br1878e2e57405acce@mail.gmail.com \
    --to=galevsky@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox