On Wed, Dec 19, 2012 at 2:44 AM, thomasg wrote:
> On Wed, Dec 19, 2012 at 5:18 AM, Gustavo Sverzut Barbieri <
> barbi...@profusion.mobi> wrote:
>
> > On Wednesday, December 19, 2012, thomasg wrote:
> >
> > > On Wed, Dec 19, 2012 at 4:38 AM, Gustavo Sverzut Barbieri <
> > > barbi...@profusion.mobi
On Wed, Dec 19, 2012 at 5:18 AM, Gustavo Sverzut Barbieri <
barbi...@profusion.mobi> wrote:
> On Wednesday, December 19, 2012, thomasg wrote:
>
> > On Wed, Dec 19, 2012 at 4:38 AM, Gustavo Sverzut Barbieri <
> > barbi...@profusion.mobi > wrote:
> >
> > > Hi Thomas,
> > >
> > > The standard way is
On Wednesday, December 19, 2012, thomasg wrote:
> On Wed, Dec 19, 2012 at 4:38 AM, Gustavo Sverzut Barbieri <
> barbi...@profusion.mobi > wrote:
>
> > Hi Thomas,
> >
> > The standard way is pretty fast and lean, but it is a SAX-like parser.
> That
> > mean you only get tokens, for the tags you nee
On Wed, Dec 19, 2012 at 4:38 AM, Gustavo Sverzut Barbieri <
barbi...@profusion.mobi> wrote:
> Hi Thomas,
>
> The standard way is pretty fast and lean, but it is a SAX-like parser. That
> mean you only get tokens, for the tags you need to call yet another
> function to split the tag and arguments.
Hi Thomas,
The standard way is pretty fast and lean, but it is a SAX-like parser. That
mean you only get tokens, for the tags you need to call yet another
function to split the tag and arguments.
It is good enough to parse svg, as done by Esvg. Should be also enough to
parse config files and your
