Hi,
I've run across a problem trying to use XUL in
the MS XML parser. XUL has the XML describing
the user interface in a file with the .xul extension.
It's pretty standard XML and XML schema code.
I think so anyway. They are localizing using
!ENTITIES in a dtd file. In reality, XUL is not
using the DTD to describe the grammer for
the user interface code in the .xul file.
The problem is Visual Basic won't parse the
.xul file since it is expecting the DTD. If
I don't include the DTD in the xul file then
of course the parser complains because it
can't find the ENTITY defines.
The XPFE - cross platform front
engine must be a home-grown parser and
can handle the DTD inconsistencies.
Unless everyone wants to use the XPFE,
we can't use XUL directly. I don't want to
be forced to use the XPFE, I think
the advantage of having a XML based
format is to use parsers already out
there.
If we can't directly use XUL - it looks
like we have to leverage.
Concerns???
Suggestions???
Sandra Matts
Sandra Matts
Engineer Scientist
Hewlett-Packard
sandram at boi.hp.com
208-396-4755 phone
Boise, ID 83714
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2140 bytes
Desc: not available
Url : http://www.pwg.org/archives/upd/attachments/19991117/067c83d8/winmail-0001.bin