We just upgraded to AIX 4.3.3. We'ed been using xlC 3.6.6, on AIX 4.2,
which is what we used to build the 1.0 and 1.1 distributions. The compiler
configuration file that we supply for Xalan should take care of configuring
STLport, so there shouldn't be any iostream issues, as STLport will wrap
Yes, that's fine. I can deal with surrogate pairs myself, as long as I know
that all lengths and offsets are in terms of 16-bit physical storage units,
not logical characters. Frankly, I prefer to deal with these myself, and
have the simplicity of assuming that I'm dealing with arrays of 16-bit
See [2] under 2.2 Characters:
"... Legal characters are tab, carriage return, line feed, and the
legal characters of Unicode and ISO/IEC 10646. ...
Character Range
[2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] |
[#xE000-#xFFFD] | [#x1-#x10] "
On Tuesday, April 3, 2001, at
DOMString is defined in the DOM spec as UTF-16. If you want to insert
characters, you have to understand multi-unit characters and Do The Right
Thing, I'm afraid. It would be Really Nice to have a general Unicode
support library which hid the internal representation entirely, but the DOM
really i
There are no smarts about surrogate pairs in DOMString AFAIK. Its not an
issue internally because all of the chars that are special to XML are
non-surrogate values. But if you mess with any output from the parser or the
DOM, its up to you to do the right thing wrt surrogates.
--
Dean
Dean Roddey wrote:
>
> It is UTF-16, in the native endianess, and no it cannot be changed. It used
> to be changeable between UTF-16 and UCS-4, but now its fixed at UTF-16.
That's great! I thought Xerces-C was UCS-2 only. So this means that
Unicode characters beyond the Base Plane are encoded
It is UTF-16, in the native endianess, and no it cannot be changed. It used
to be changeable between UTF-16 and UCS-4, but now its fixed at UTF-16.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Sze, Tak F [mailto:[EMAIL P
Does anybody know the internal encoding used by Xerces-C?
Can this be changed?
- Tak Sze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, there is very good reason. And that reason is that the spec says so :-)
So this one is a 'working as designed' in this case. If you look at the end
of the spec, it shows the lists of characters that are valid. Only a few of
the traditional control chars (< 32 in ASCII) are permitted. You cann
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1203
*** shadow/1203 Tue Apr 3 15:16:33 2001
--- shadow/1203.tmp.22490 Tue Apr 3 15:16:33 2001
***
*** 0
--- 1,59
+ ++
+ | Control chars as e
There is a method on the validator interface to do that. So you'd get the
validator from the scanner and use that to translate the id to the text.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Sze, Tak F [mailto:[EMAIL PR
Hello everybody,
I am submitting a fix I made to the sources so that it can be included in
the next release (I am a newbie to this mailing list, so I am not sure if
and how I can make the change myself - please forgive me).
I have an XML document that points to a DTD including several other DTD
How does one convert the URIId returned from startElement
to the actual URI?
- Tak Sze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> You've got no prefix, but its in a
> namespace, which is inconsistent and requires special casing.
> Why couldn't they have just said that if you see an unprefixed attribute
named
> xmlns, that's all the signal that you need.
That would save special-casing during DOM construction, but add spec
>So when adding namespace declarations through the DOM, you should manually
>set the namespaceURI to "http://www.w3.org/2000/xmlns/". Correct?
Yep. See the description of when createAttributeNS throws a NAMESPACE_ERR
DOMException.
---
Try catching SAXException also. There was a thread in the xalan group a
little while back that mentioned all the different types of exceptions that
may be thrown.
xerces:
SAXException
XMLException
DOM_DOMException
xalan:
XSLException
XalanDOMException
Dave
I saw this link on the Xalan dev mailing list ...
If you need to browse the mailing lists for xerces-c-dev for this year go to
...
http://marc.theaimsgroup.com/
and follow the link to xerces-c-dev ... might be useful.
-
To un
thanks
-Original Message-
From: A l e x a n d e r Z e y l i g e r [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 1:15 AM
To: [EMAIL PROTECTED]
Subject: Re: error
> m='msn.afslx2.auto 6D 3D 27 6D 73 6E 2E 61 66 73 6C 78 32 2E 61 75 74 6F
> matedfinancial.com 6D 61 74 65 64 66
Did you pattern "split" after DOMPrint or is it
included in DOMPrint.cpp ... just where is this code you wrote? If it is a
new file, do you initialize the system with
XMLPlatformUtils::Initialize()?
Todd
- Original Message -
From:
Emma
Towey
To: [EMAIL PROTECTED]
Then you should use a debugger and debug where its
failing.
--Dean RoddeyThe CIDLib C++
FrameworksCharmed Quark Software[EMAIL PROTECTED]http://www.charmedquark.com
"I'm not sure how I feel about ambivalence"
- Original Message -
From:
Emma
T
That should not be a problem. Whitespace, comments, and PIs are legal after
the end of the root element. If anyone is actually having that problem its a
bug.
--
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"I'm
"has an Attr with
nodeName = "xmlns"
prefix = null (unspecified)
localName = "xmlns"
namespaceURI = "http://www.w3.org/2000/xmlns/"
nodeValue="xxx""
Is the part that I think is bad. You've got no prefix, but its in a
namespace, which is inconsistent and requires special c
The error that I receive is not due to my xml file as I can parse it using DOMPrint.
The message that I get from my program (which is using Microsoft Visual C++ 6) is:
unhandled exception in split.exe (XERCES-C_1_4D.DLL): 0XC0005: Access Violation.
(split is the name of my C++ class)
Those should never get out of the parse() call. If they are reaching you,
then the problem is really that they aren't getting caught internally as
they should (perhaps for the reason you indicate), which will cause many bad
problems. I'd suggest using a compiler that works personally.
---
I have had several problems ... I will bring them up again ... what version
of STL are you using? xlC version? I looked again and I stated my AIX
version incorrectly ... I have 4.3.2.
Also, what did you do about SGI_IOSTREAMS?
Todd
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[
> Also note that if you insist on using DOM Level 1 factory methods to build
> the nodes, you wind up with DOM Level 1 nodes -- the nodename gets set,
> none of prefix, namespaceURI, or localName will. Intermixing level 1 and
> level 2 nodes is _NOT_ recommended.
So when adding namespace declarat
Make sure that you don't have any whitespace characters at the end of your
xml stream. I used to get the same error if I have a new line at the end
of my xml file, but the DOM will still be constructed since the error
occurs at the end of the file.
-JJ
On Mon, 2 Apr 2001, Alex Fridman wrote:
>
>Do you want to boil that down to the raw facts,
>just so that there is no confusion?
Sorry; overcompensated writer's block ... If you're using the DOM
Level 2 namespace-aware calls to build and probe the DOM, and assuming I'm
awake, this should work out as follows.
>
>
>
Element
n
Did you rebuild build xerces-c with ICU? The pre-built
binaries
do not use ICU, even if it is avialable on your
system.
ICU does support euc-kr, and xerces built with ICU should
recognize
euc-kr encoded documents with no problem.
IBM XML4C is xerces-c + ICU. Binaries are available
from
It looks like xerces throws exceptions of type XMLErrs::Codes (which
is an enum). My platform is Solaris 8 with Forte 6.1, and the
compiler (or is it debugger?) seems to get confused: I think
they treat enums as ints, and don't really know what to catch
when an int is thrown.
In my application,
It's just for compatibility. The XHTML 1.0 abstract reads: "This
specification defines XHTML 1.0, a reformulation of HTML 4 as an XML 1.0
application, and three DTDs corresponding to the ones defined by HTML 4. The
semantics of the elements and their attributes are defined in the W3C
Recommendatio
Emma
What does your XML file look like?
Todd
- Original Message -
From:
Emma
Towey
To: [EMAIL PROTECTED]
Sent: Tuesday, April 03, 2001 12:51
PM
Subject: error thrown by parser
Hi,
I’m having a bit of a problem with the parser.
When my program p
Try
parsing the file with one of the standalone sample programs, like DOMPrint. If
that works, then its nothing to do with the XML text you are parsing, and its
just an error in your program probably causing an access violation or something.
That's not something anyone but you can figure out
If the XHTML folks are really saying that, they are making a huge mistake
unless its just a 'for compatibility' thing. No XML parser will ever check
that, so what's the point? They can't start making up well formedness rules
above and beyond XML and expect any XML parsers to care.
--
No, that's not required.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: A l e x a n d e r Z e y l i g e r [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 10:15 PM
To: [EMAIL PROTECTED]
Subject: Re: error
I've see
XHTML 1.0 says, "Include a space before the trailing / and > of empty
elements," but I'm not aware of any reason to do so for an XML document that
is not also HTML.
-Original Message-
From: A l e x a n d e r Z e y l i g e r [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 1:15 AM
Is there a way to do
with Xerces/Xalan?
It does not to work here (testxslt.exe) - is it not supported?
Thank you,
Martin Teucher
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
hello.
I installed Xerces1.4 on Solaris 2.6 andy cc & CC compiler.
and I installed icu1.8.
but.. still, I got a problem with my job which process XML
Document encoding "euc-kr"..
In DOM Parsing time, error message is occured,
like, "euc-kr" is unknown
so.. I want to know how I process do
> m='msn.afslx2.auto 6D 3D 27 6D 73 6E 2E 61 66 73 6C 78 32 2E 61 75 74 6F
> matedfinancial.com 6D 61 74 65 64 66 69 6E 61 6E 63 69 61 6C 2E 63 6F 6D
> /registered'/> 2F 72 65 67 69 73 74 65 72 65 64 27 2F 3E
I've seen somewhere that there should be a space between the last
quote and /> .
-
Hi,
Im having a bit of a problem with the parser.
When my program parses a file it returns an error. The error returned is not of type XMLException or of type DOM_DOMException.
try
{
parser->parse(gXmlFile);
}
catch (const XMLException& e)
{
cerr << "A
Hi,
Im having a bit of a problem with the parser.
When my program parses a file it returns an error. The error returned is not of type XMLException or of type DOM_DOMException.
try
{
parser->parse(gXmlFile);
}
catch (const XMLException& e)
{
cerr << "An
XML parsers are not like HTML parsers where they will just try to continue
making sense out of any random text you throw at them. One you've hit an
error from which the parser cannot know for sure how to recover correctly,
its not going to go any further. You have to feed the parser well formed
XM
"In the DOM, any node which is not assigned a namespace (which I think is
what Dean referred to as the global namespace) should use null rather than
the empty string or any other string as its namespaceURI."
That's pretty sad, because there is no good way to represent this coming out
of the parse
Do you want to boil that down to the raw facts, just so that there is no
confusion?
So:
becomes what?
and
becomes what, in the DOM world?
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED
Since I have got about 5 requests over the last few months for my
experiences porting Xerces to VxWorks, I thought I should post them for all
to use. Thanks to everyone on the mailing list for helping me get Xerces up
and running.
Here are roughly the steps I used to port the Xerces C++ XML pa
You must use an output encoding that can handle those characters. Internally
the parser uses UTF-16, which can handle pretty much everything. But when
you dump it back out, you must use an encoding which understands all of the
characters you are going to output, or tell the formatter to generate
c
HI Todd,
What problems are you having with STLport for AIX 4.3.3. We just upgraded
our AIX machine and started having trouble building Xalan, although we
could just have a configuration issue.
Dave
(BTW, apologies if I seem to be convolving a SAX question with a DOM
question -- my citations of the DOM's solution were just intended to give
the perspective of someone who's already had to wrestle this particular
alligator. )
---
> >"The prefix xmlns is used only for namespace bindings and is not itself
> >bound to any namespace name."
>
> The Namespace authors have since conceded that this was not
> optimal design.
> It isn't currently listed as an erratum, but I believe it's likely to
> change to agree with the DOM's s
>"The prefix xmlns is used only for namespace bindings and is not itself
>bound to any namespace name."
The Namespace authors have since conceded that this was not optimal design.
It isn't currently listed as an erratum, but I believe it's likely to
change to agree with the DOM's solution if/whe
Wild guess: XML requres that there be one and only one root element, and
after it goes by only comments and PIs are permitted. Is there any chance
that you're trying to parse a document/file/input-stream containing two or
more root elements?
Curent XML Recommendation (1.1): "The Namespaces in XML Recommendation [XML
Names] assigns a meaning to names containing colon characters. Therefore,
authors should not use the colon in XML names except for namespace
purposes, but XML processors must accept the colon as a name character."
And in
This is from Deja ...
*
Message 6 in thread
From: Irina Kosinovsky ([EMAIL PROTECTED])
Subject: Re: STLPort.org Gone?
Newsgroups: comp.lang.c++
Date: 2001-04-02 04:02:04 PST
Yes STLport.org is being maintained. Recent online problems were caused by
NortPoint DSL provider suddenly go
Hello,
I am trying to parse XML document sent from remote site. Because
I don't have the content length field for the XML document, I have
to parse it progressively. The problem is after encountered an
error due to incomplete content, I cannot continue the parse using
SAXParser::parseNext() though
>But is there anything in the namespace spec that says that the URL for a
>namespace cannot be empty?
In the definition of "namespace prefix", it says "In such declarations, the
namespace name may not be empty."
The default namespace may be returned to the no-namespace case by using
xmlns="" ..
>The tricky part which I didn't see in
>the DOM spec was how would prefix and localname work. I would assume that
>the default namespace decl would have a null or zero length local name.
The DOM's intent was that the xmlns= default declaration would have
localname "xmlns", no prefix, and the nam
I need to verify ... I believe I was tried to remake the Xerces library and
was having trouble. I no longer want to do that and I am able to compile
code that uses teh Xerces library with xlC.
I do still have a problem with Xalan but that is on a back burner for a few
days. I tried to get ST
I was able to get to STLport.org this morning. They do have software setup
for various systems. I have been having trouble with a port for AIX 4.3.3
... so now I am going to look at the code off of the SGI site ... but that
is another story.
Todd
>From: Richard Morgan <[EMAIL PROTECTED]>
>
Todd,
Are you talking Xalan only, or Xerces and Xalan? I have Xerces going, but
have not tried Xalan.
Thanks,
Mike
Belezebubba wrote:
> Bovone
>
> I have been working through that as well ... I have AIX and xlC and been
> having fits ... I am slowly narrowing it down ... a good makefile would
Hi,
I am trying to compile xerces source in solaris 2.6 with
g++ 2.95.2
It compiles all the .c files and creates the .o files in the ${XERCESROOT}/obj/SOLARIS
But while "Building ${XERCESROOT}/lib/libxerces-c1_4.so",
the following error occurs.
The command is:
g++ -DSOLARIS -shared -o /opt/
Okay, but that doesn't mention support for solaris. The
http://www.stlport.org/beta.html
url has some beta versions to download, but I've not tried
these yet.
-Original Message-
From: Todd Firsich [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 1:47 PM
To: [EMAIL PROTECTED]
Subj
Try the SGI site ...
http://www.sgi.com/tech/stl/download.html
>From: "Paul Linden" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: STLPort defunct?
>Date: Mon, 2 Apr 2001 17:38:41 -0700
>
>I'm sorry if this has been asked thousands of times recently, but the
Thanks Andy, that was what I was missing...
-ryan
- Original Message -
From: "Andy Heninger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 02, 2001 4:57 PM
Subject: Re: Casting DOM_Node to DOM_Element... still a problem.
> > DOM_Element elem = static_cast(nodeList.it
The latest XML Namespaces W3C Rec. says:
--
Namespace Constraint: Prefix Declared
The namespace prefix, unless it is xml or xmlns, must have been declared in a
namespace declaration attribute in either the start-tag of the element where
the prefix is used or in an an ancestor elem
I've an XML file with a lot oh CDATA section. In these sections, there
are a lot of accentuated characters because of the language I use is
French.
When I build the tree with the DOMParser, there is no problems but when
i get the text contained in CDATA section, and when i display it whith
the XM
I've an XML file with a lot oh CDATA section. In these sections, there
are a lot of accentuated characters because of the language I use is
French.
When I build the tree with the DOMParser, there is no problems but when
i get the text contained in CDATA section, and when i display it whith
the XM
Maybe there is a problem with my build. Does anyone out there have a
working (non-leaking) project for BCB5, or any hints or things I should know
or look out for?
Simon
-Original Message-
From: Dean Roddey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 4:35 PM
To: [EMAIL PROTE
that
is because an id is considered as an xml-name and according to the specs (www.w3.org):
[Definition: A Name
is a token beginning with a
letter or one of a few punctuation characters, and continuing with letters,
digits, hyphens, underscores, colons, or full stops, together known as nam
68 matches
Mail list logo
