From: Chong Yidong <cyd@gnu.org>
To: MON KEY <monkey@sandpframing.com>
Cc: 4950@debbugs.gnu.org
Subject: bug#4950: `xml-parse-file' returns incorrect results strings after `>' before `<' when CR\LF TAB+
Date: Sun, 01 Jul 2012 19:22:33 +0800 [thread overview]
Message-ID: <874npr6806.fsf@gnu.org> (raw)
In-Reply-To: <d2afcfda0911171412m394edccdw129ff7993c245384@mail.gmail.com> (MON KEY's message of "Tue, 17 Nov 2009 17:12:37 -0500")
MON KEY <monkey@sandpframing.com> writes:
> <ELEMENT attr1="a1" attr2="a2" attr3="a3" attr4="a4" attr5="a5">CR\LF
> TAB TAB TAB <NEXT-NODE>
>
> Returns (:NOTE with my pp-ing to help clarify the problem):
>
> (ELEMENT nil
> ((attr1 . "a1")
> (attr2 . "a2")
> (attr3 . "a3")
> (attr4 . "a4")
> (attr5 . "a5") "
> " ;; <-i.e. (mapconcat #'char-to-string '(32 10 9 9 9) "")
> (NEXT-NODE nil (...
>
> Is it if fair/safe to assume that where these types of sequences occur
> they are not part of the XML and can be removed with a regexp?
No.
XML 1.0 Recommendation, Section 2.10 White Space Handling:
"An XML processor MUST always pass all characters in a document that are
not markup through to the application."
prev parent reply other threads:[~2012-07-01 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 22:12 bug#4950: `xml-parse-file' returns incorrect results strings after `>' before `<' when CR\LF TAB+ MON KEY
2012-07-01 11:22 ` Chong Yidong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874npr6806.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=4950@debbugs.gnu.org \
--cc=monkey@sandpframing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).