The intention is to end up with one set of serializers/printers sooner
rather than later.
I might note that the arguments made for pulling the DOM out of the xerces
package also apply to the serializers/printers.
-scott
Assaf Arkin
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
e.com> cc: (bcc: Scott Boag/CAM/Lotus)
Sent by: Subject: Re: C++ printers [was
Re: [Proposal] Printer package]
[EMAIL PROTECTED]
office.com
11/17/99 07:57
PM
Please respond
to xerces-dev
Mike Pogue wrote:
>
> Very cool. Thanks!
>
> So, let me make sure I understand. Are there TWO printers of this type
> (one from Arkin, one already in Xalan somewhere)? Does Arkin's replace
> the Xalan one, or does it do something different than the Xalan one, or
> am I just totally confused here?
Yes, two printers of the same type. The one in Xalan pretty much does
the same job, the one I'm contributing just has more features already
integrated (SAX2, line wrapping, good HTML support).
The discussion on where to put them is relevant if Xalan would benefit
from using the same set of printer as Xerces, so we'll end up having
only one set of printers.
arkin
>
> Thanks,
> Mike
>
> Keith Visco wrote:
> >
> > I will create the SAX based C++ printers, which will be pretty much a
straight
> > port from Assaf's code. Given time I might write the DOM printer that
sits on
> > top of the SAX one, but that will come later.
> >
> > --Keith
> >
> > Assaf Arkin wrote:
> >
> > > Mike Pogue wrote:
> > > >
> > > > Hey, Arkin...can we get a C++ version, too, so that the two
> > > > Xerces parsers stay together? I'd expect that the Java and
> > > > C++ Xerces parsers would want to serialize and canonicalize
> > > > identically.
> > >
> > > The Java code can be migrated into C++, but I'll have to decline this
> > > one, I haven't written a line of C++ in nearly three years, and it's
> > > hard to get back.
> > >
> > > arkin
> > >
> > > >
> > > > Mike
> > > >
> > > > Assaf Arkin wrote:
> > > > >
> > > > > OK. Package name changes to org.apache.xerces.serialize
> > > > >
> > > > > arkin
> > > > >
> > > > > Tom Palmer wrote:
> > > > > >
> > > > > > > people confuse because Java semantics are a bit different and
more
> > > > > > > common.
> > > > > > >
> > > > > > The trick is having to cope with two groups using the same
> > > > > > word in slightly different ways, and any name picked that is
> > > > > > nice for Java may end up being bad for another language.
> > > > > >
> > > > > > It would be good to use the terms that the W3C uses.
> > > > > >
> > > > > > Adding a qualifier may help at times: DOM serialization vs.
> > > > > > Java serialization. Of course, this would only be useful for
> > > > > > normal conversation and so on. Package naming is a
> > > > > > different issue.
> > > > > >
> > > > > > - Tom Palmer
> > > > >
> > > > > --
> > > > > ____________________________________________________________
> > > > > Assaf Arkin [EMAIL PROTECTED]
> > > > > CTO http://www.exoffice.com
> > > > > Exoffice, The ExoLab Company tel: (650) 259-9796
> > >
> > > --
> > > ____________________________________________________________
> > > Assaf Arkin [EMAIL PROTECTED]
> > > CTO http://www.exoffice.com
> > > Exoffice, The ExoLab Company tel: (650) 259-9796
--
____________________________________________________________
Assaf Arkin [EMAIL PROTECTED]
CTO http://www.exoffice.com
Exoffice, The ExoLab Company tel: (650) 259-9796
