Re: Broken i18n and the new UI handler.
- From: Daniel Veillard <Daniel Veillard w3 org>
- To: Havoc Pennington <hp redhat com>
- Cc: Daniel Veillard w3 org, Michael Meeks <mmeeks gnu org>, Miguel de Icaza <miguel helixcode com>, Michael Meeks <michael helixcode com>, gnome-hackers nuclecu unam mx, gtk-devel-list gnome org
- Subject: Re: Broken i18n and the new UI handler.
- Date: Mon, 11 Sep 2000 23:03:10 +0200
On Mon, Sep 11, 2000 at 04:29:23PM -0400, Havoc Pennington wrote:
>
> Daniel Veillard <Daniel Veillard w3 org> writes:
> > So it's mostly a (shared) library size issue...
> >
>
> Also "GLib integration", that is you would want to have stuff
> allocated with g_malloc(),
You can do through xmlMemSetup()
http://xmlsoft.org/html/gnome-xml-xmlmemory.html#XMLMEMSETUP
> use GError,
you mean using you own message callback, sure change the
error, warning and fatalError either in your SAX block or directly
in the xmlDefaultSAXHandler block.
> use GList, that type of thing.
Okay libxml doesn't use glist
> > > I actually think a full XML parser could be small enough (remove some
> > > of the addons such as nanohttp and xpath, etc.) - but I'm not sure
> > > it's worth doing that given that we already have libxml. I don't
> >
> > It may be worth splitting libxml into more than one shared library,
> > I'm not opposed to this at all ... Problem is that the entity resolution
> > may need the HTTP or FTP access and I don't know how to load them only
> > when needed at runtime (feasible, iconv works this way, but portable ?)
> > Actually libxml configure allow to remove all non-core options
> >
>
> Right. One thing that might be possible would be to use libxml
> internally in GLib (via the SAX interface) but then export a
> GLib-style interface. Sort of a G-wrapper for libxml. I'm pretty sure
> such a patch wouldn't be accepted for GLib though; I don't know. Maybe
> it could ship with GLib as GObject does, in a separate lib. Just
> speculation. I'm sure there would be significant feeling that it was
> bloat to depend on libxml.
That I understand.
> > > personally care to maintain such an alternative XML parser at least.
> > > So since that won't happen GMarkup will have to do.
> >
> > But make sure it's 100% XML ...
> >
>
> It's supposed to save/output valid XML. It certainly can't read/parse
> full-blown XML.
Okay should not be too hard to doublecheck.
> > > > - How do you intent to handle I18N and L14N issues in GMarkup ?
> > > >
> > >
> > > GMarkup just loads and saves UTF8, and that's it.
> >
> > Well humm... XML requires UTF16 support, but it's not widely used on
> > linux ...
> >
>
> Yep. GMarkup can only read UTF8, but the UTF8 it outputs should be
> valid XML since XML processors are required to handle UTF8 I think.
right
> > > If you have time to look at GMarkup and help ensure it is a genuine
> > > XML subset, that would be a very good thing. As long as it only saves
> > > valid XML, people can easily upgrade to libxml in the future.
> >
> > I don't really have much time, I should spent some anyway. Did you
> > made a list of the specific productions of the XML specification you
> > do not support ?
> >
>
> GMarkup basically accepts:
>
> - elements and attributes <foo bar="baz"></foo>
> - the empty-element shortcut <foo bar="baz"/>
> - the standard 5 entities < > ' " &
> - character references ൠ
> - UTF8 encoding
> - parses processing instructions and comments, but doesn't do
> anything with them (just passes them through in an opaque node,
> and resaves them, but with no interpretation)
>
> It will not handle cdata, custom entities, DTDs or validation,
> etc.
Correspond more or less to SML an XML simplified version developped
by some people using XML for purely data centric use:
http://www.xml.com/pub/1999/11/sml/
but SML is even smaller than your subset (or was supposed to, I didn't
heard much about it lately),
I have no problem with GMarkup, I understand where you come from
and the reasons. As long as people are not pointed to GMarkup as being
a generic XML parser, it makes sense.
Daniel
--
Daniel Veillard w3 org | W3C, INRIA Rhone-Alpes | Today's Bookmarks :
Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW
Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind
http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]