bug#12227: 24.1.50; xml.el: xml-entity-alist is pre-ecaped!

bug#12227: 24.1.50; xml.el: xml-entity-alist is pre-ecaped!

[Matt Price]

"xml-entity-alist" in xml.el is used by other programs, notably
xml-rpc.el, to parse xml content and escape xml entities.
Unfortunately the current version of xml.el has two of the entities
pre-escaped:

(defvar xml-entity-alist
'(("lt" . "<")
("gt" . ">")
("apos" . "'")
("quot" . "\"")
("amp" . "&"))
"Alist mapping XML entities to their replacement text.")

this creates invalid xml output. replacing this with:
(defvar xml-entity-alist
'(("lt" . "<")
("gt" . ">")
("apos" . "'")
("quot" . "\"")
("amp" . "&"))
"Alist mapping XML entities to their replacement text.")

seems to fix the problem.

Thank you!


In GNU Emacs 24.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2)
of 2012-07-29 on charichuelo, modified by Debian
(emacs-snapshot package, version 2:20120728-1~ppa1~precise1)
Windowing system distributor `The X.Org Foundation', version 11.0.11103000
Configured using:
`configure '--build' 'x86_64-linux-gnu' '--host' 'x86_64-linux-gnu'
'--prefix=3D/usr' '--sharedstatedir=3D/var/lib' '--libexecdir=3D/usr/lib'
'--localstatedir=3D/var' '--infodir=3D/usr/share/info'
'--mandir=3D/usr/share/man' '--with-pop=3Dyes'
'--enable-locallisppath=3D/etc/emacs-snapshot:/etc/emacs:/usr/local/share/=
emacs/24.1.50/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/2=

4.1.50/site-lisp:/usr/share/emacs/site-lisp'
'--without-compress-info' '--with-crt-dir=3D/usr/lib/x86_64-linux-gnu/'
'--with-x=3Dyes' '--with-x-toolkit=3Dgtk3' '--with-imagemagick=3Dyes'
'build_alias=3Dx86_64-linux-gnu' 'host_alias=3Dx86_64-linux-gnu'
'CFLAGS=3D-DDEBIAN -DSITELOAD_PURESIZE_EXTRA=3D5000 -g -O2' 'LDFLAGS=3D-g
-Wl,--as-needed -znocombreloc' 'CPPFLAGS=3D-D_FORTIFY_SOURCE=3D2''

Important settings:
value of $LANG: en_CA.UTF-8
locale-coding-system: utf-8-unix
default enable-multibyte-characters: t

Major mode: Org

Minor modes in effect:
org2blog/wp-mode: t
flyspell-mode: t
desktop-save-mode: t
delete-selection-mode: t
yas/global-mode: t
global-auto-complete-mode: t
multi-web-global-mode: t
shell-dirtrack-mode: t
iswitchb-mode: t
sml-modeline-mode: t
show-paren-mode: t
recentf-mode: t
global-linum-mode: t
linum-mode: t
tooltip-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
visual-line-mode: t
transient-mark-mode: t
abbrev-mode: t

Recent input:
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up>=20
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up>=20
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up>=20
<up> <up> <up> <up> <up> <up> <up> <up> M-x <up> <up>=20
<return> C-x b <return> M-x <up> <up> <return> y C-x=20
b <return> <down> <down> <down> <down> <down> <down>=20
<down> <down> <down> <down> <down> <down> <down> <down>=20
<down> <down> <down> <down> <down> <down> <down> C-s=20
e s c a p e C-a C-/ <down> <down> <down> <down> <down>=20
<down> <down> <down> <down> <up> <backspace> <backspace>=20
<backspace> M-x <up> <return> C-g M-x e l i s <tab>=20
<backspace> <backspace> <backspace> <backspace> <backspace>=20
<backspace> <backspace> <backspace> <backspace> <backspace>=20
<backspace> <backspace> <backspace> <backspace> <backspace>=20
<backspace> <backspace> <backspace> l i s p - m <tab>=20
<return> <escape> M-x C-g M-x e v a l - b u f f <tab>=20
<return> C-/ C-/ <left> <left> <left> <left> <left>=20
<left> <left> <left> <left> <left> <left> <left> <right>=20
<right> <right> <right> <right> <right> <right> <right>=20
<right> <right> <right> <right> <backspace> M-x e v=20
a l - b u f f <tab> <return> C-x b <return> M-x <up>=20
<up> <up> <return> <help-echo> <help-echo> <help-echo>=20
<help-echo> <down-mouse-1> <mouse-1> C-x <help-echo>=20
<down-mouse-1> <mouse-1> n <help-echo> <down-mouse-1>=20
<mouse-movement> <mouse-1> C-x b m e s s <return> <escape>=20
> <down-mouse-1> <mouse-1> C-x b <return> C-x k <return>=20
C-x b <return> ; ; SPC <down-mouse-1> <mouse-1> <up>=20
<up> C-a C-SPC <down> <down> <down> <down> <down> <down>=20
<down> <down> <down> <down> <down> <down> <up> <up>=20
<up> <up> <up> <down> <down> <down> <down> <down> C-w=20
M-x <up> <up> <return> C-x b <return> C-x b h i s <return>=20
M-x <up> <up> <return> y M-x r e p o r t - e m a c=20
s - b u g <return>

Recent messages:
parsed!! <div id=3D"table-of-contents"> <h2>Table of Contents</h2> <div id=
=3D"text-table-of-contents"> <ul> <li><a href=3D"#sec-1"><span
style=3D"tex=
t-decoration:underline;">Logistics</span></a></li> <li><a
href=3D"#sec-2"><=
span style=3D"text-decoration:underline;">Introduction</span></a></li>
<li>=
<a href=3D"#sec-3"><span style=3D"text-decoration:underline;">Course
Struct=
ure</span></a></li> <li><a href=3D"#sec-4"><span
style=3D"text-decoration:u=
nderline;">Course Requirements</span></a></li> <li><a
href=3D"#sec-5"><span=
style=3D"text-decoration:underline;">Texts</span></a></li> <li><a href=3D"=
#sec-6">Tools</a></li> <li><a href=3D"#sec-7">Outline for Semester
1</a></l=
i> <li><a href=3D"#sec-8">'Outline' for Semester 2</a></li> </ul> </div> <=
/div> <div id=3D"outline-container-1" class=3D"outline-2"> <h2 id=3D"sec-1=
"><span style=3D"text-decoration:underline;">Logistics</span></h2> <div
cla=
ss=3D"outline-text-2" id=3D"text-1"> <table border=3D"2" cellspacing=3D"0"=
cellpadding=3D"6" rules=3D"groups" frame=3D"hsides"> <caption></caption> <=
colgroup><col class=3D"left" /><col class=3D"left" /> </colgroup>
<tbody> <=
tr><td class=3D"left"><b>Instructor:</b></td><td class=3D"left">Matt
Price<=
/td></tr> <tr><td class=3D"left"><b>Email:</b></td><td
class=3D"left">matt.=
price@utoronto.ca</td></tr> <tr><td class=3D"left"><b>Tel:</b></td><td
clas=
s=3D"left">978-8472</td></tr> <tr><td class=3D"left"><b>Office
Hrs:</b></td=
><td class=3D"left">SS 3077 M 12-2</td></tr> </tbody> </table> </div> </d=
iv> <div id=3D"outline-container-2" class=3D"outline-2"> <h2 id=3D"sec-2">=
<span style=3D"text-decoration:underline;">Introduction</span></h2> <div
cl=
ass=3D"outline-text-2" id=3D"text-2"> <p> In the year of your birth, the =
<a href=3D"http://en.wikipedia.org/wiki/History_of_the_World_Wide_Web#1979.=
E2.80.931991:_Development_of_the_World_Wide_Web">World Wide Web</a> was
an =
obscure technical work-in-progress buried in the depths of a vast
research =
institute. Today, it permeates almost every aspect of our lives, including=
every stage in the production of knowledge. You have been living through =
a fundamental transformation of knowledge; and yet the modes of
communicati=
on you've learned and explored at University (the essay, the article,
the s=
cholarly monograph) belong to the world that came before. There are good r=
easons for this. The standards of our discipline were formed carefully ove=
r hundreds of years, in a determined quest to uncover and communicate
truth=
s about the past to our colleagues and the wider world. Even so, historian=
s need to explore the digital media of our present and future. The books a=
nd other writings of old will not disappear, but they will be
supplemented =
by the new media of the web. In this class, we will explore those new medi=
a as tools for the transmission of historical knowledge, culminating in
an =
intensive group project in which you will build a historical website in
clo=
se collaboration with a community partner. The community partnership is a =
key element of "Hacking History", and a source of many of its pleasures
and=
challenges. </p> <p> Along the way, we will learn about the history of d=
igital media, and their place in the development of the public sphere;
and =
we will also study the history and politics of "engaged" and "public"
schol=
arship. We will also spend a substantial amount of time acquiring the tech=
nical skills needed for a project like this, e.g., the fundamentals of
<a h=
ref=3D"http://en.wikipedia.org/wiki/HTML">HTML</a> and <a
href=3D"http://ww=
w.codecademy.com/tracks/javascript">Javascript</a>, as well as just
enough =
<a href=3D"http://ca.php.net/tut.php">PHP</a> to work with the <a
href=3D"h=
ttp://www.wordpress.org">Wordpress</a> Content Management System. No prior=
technical knowledge is required for this, but you will need to be willing =
to challenge yourself to learn a few tricks and principles of web
programmi=
ng. The payoff for that effort is huge: a chance to contribute in a meanin=
gful way to historical discourse beyond the walls of the University, and
to=
explore the frontiers of historical communication in the process. </p> <=
/div> </div> <div id=3D"outline-container-3" class=3D"outline-2"> <h2 id=
=3D"sec-3"><span style=3D"text-decoration:underline;">Course
Structure</spa=
n></h2> <div class=3D"outline-text-2" id=3D"text-3"> </div> <div id=3D"o=
utline-container-3-1" class=3D"outline-3"> <h3 id=3D"sec-3-1">First
Semeste=
r</h3> <div class=3D"outline-text-3" id=3D"text-3-1"> <p>In the first seme=
ster we will meet on a weekly basis to discuss the week's readings
("Readin=
gs" in the <a href=3D"#Outline-Semester-1">outline</a>) and work
together o=
n a technical or interpretative task that will be defined in advance
("Lab"=
in the <a href=3D"#Outline-Semester-1">outline</a>). In advance of the cl=
ass meeting students will (where not otherwise noted) be expected to
produc=
e written responses to the readings in the form of blog postings, and to
re=
spond to the postings of at least two other students. If at all possible, =
you should bring your laptop or (not as good!) tablet to class for the
lab =
portion. </p> <p> In certain weeks there are also other types of assignme=
nts; these are noted in the outline and referred to in the course
requireme=
nts. In general the aim is to foster an atmosphere of collaborative and se=
lf-directed learning in which all work is focused on building the
analytic =
resources, technical skills, and confidence to create really great
projects=
in the second semester. Though the assignment structure is fixed, reading=
s may change based on student interests. The semester culminates with
group=
presentations of your proposed projects. </p></div> </div> <div id=3D"=
outline-container-3-2" class=3D"outline-3"> <h3 id=3D"sec-3-2">Second
Semes=
ter</h3> <div class=3D"outline-text-3" id=3D"text-3-2"> <p>In the second s=
emester it is expected that students will spend most of their time
working =
directly on their project with the partnering organization. We will meet m=
ost weeks to discuss specific technical questions raised by the projects
th=
emselves, and will discuss additional readings as needed. Importantly, stu=
dents will continue to make regular postings about their progress, and
comm=
ent on each other's writing. Projects will be submitted to community partn=
ers for review in the second to last week of classes, presented to the
clas=
s in the final course meeting, and handed in to the professor
immediately b=
efore the beginning of finals period. </p></div> </div> </div> <div id=
=3D"outline-container-4" class=3D"outline-2"> <h2 id=3D"sec-4"><a
name=3D"C=
ourse-Requirements" id=3D"Course-Requirements"></a><span
style=3D"text-deco=
ration:underline;">Course Requirements</span></h2> <div
class=3D"outline-te=
xt-2" id=3D"text-4"> <p>In this project-based class, we have relatively fe=
w readings and instead focus on active learning through a variety of
assign=
ments, all of which are intended to help you build towards your final,
coll=
aborative group project. </p> <p> The class has 5 kinds of assignments: <=
/p><ul> <li>19 Weekly Blog Postings (both semesters, <b>20%</b>) </li> <=
li>4 "Short Technical Assignments" (STA's, first semester, <b>10%</b>) </=
li> <li>1 Website Review (First Semester, <b>5%</b>) </li> <li>One
Written =
Paper (7-9 pp, Jan 10, <b>10%</b>) </li> <li>The Final Project (website, =
ongoing but due April 4, <b>45%</b>) </li> </ul> <p>with the balance of 10=
% for on- and off-line participation, which includes comments on other
stud=
ents' blog posts, contributions to online resources, and discussion.
</p> <=
p> <b>Blog Postings</b> are thoughtful pieces, 300 words or so in
length, p=
osted to the course blog by noon the day before class meets (so, noon
each =
Wednesday). You will be expected to read your colleagues' postings and res=
pond to them, both online (using the blog's comment function) and in
class.=
In the first semester, these postings will primarily be <i>responses to t=
he weekly readings.</i> In the second semester, they will instead
generally=
take the form of <i>progress reports</i> in which you discuss your final p=
rojects and your interactions with partnering organizations, or of
<i>short=
written pieces from your project site</i> (see below). In the event that =
I want you to focus on something else, I will inform you one week in
advanc=
e <i>in class</i>. Some informality in tone is acceptable, but these are t=
o be serious, thoughtful engagements with the course materials. Think of t=
hem as a cross between a <a
href=3D"http://www.quicksprout.com/2009/07/21/h=
ow-to-write-a-blog-post/">regular blog post</a> and a <a
href=3D"http://his=
toryprofessor.org/reading/how-to-write-a-review/">review or response
paper<=
/a>. Citations of online sources should use hyperlinks; other material sho=
uld be cited as in printed assignments (I recommend <a
href=3D"http://www.c=
hicagomanualofstyle.org/home.html">Chicago Manual of Style</a>, but we
will=
discuss this at greater length during the semester). You are expected to =
blog each week of class, with the exception of the first and last week
of e=
ach semester, and the week of your website review. I will comment on indiv=
idual blog posts as much as possible, but will give out marks only twice
a =
year (approx. Nov. 29 &amp; Apr. 3). </p> <p> <b>Short Technical Assignmen=
ts (STA's)</b> are designed to give you the technical skills you will
need =
for your website development work in the second semester. Approximately ev=
ery 3 weeks in the first semester, you will complete a short on or
off-line=
assignment for a pass-fail grade. The lab assignments will cover basic we=
b skills and other technical topics, which will always have been covered
in=
the third 'lab' hour of class. </p> <p> The <b>Website Review</b> has two=
parts: a written review of a historical website posted to the course websi=
te at least 24 hours before class, and a very short in-class
presentation. =
We will have one or two website reviews each week in the first semester, e=
xcept for Nov. 29. The written portion is posted to the course website in =
lieu of that week's blog post (see the review assignment for more
details).=
</p> <p> <b>The Paper</b> is due shortly after the beginning of the seco=
nd semester. Approximately 7-9 pages long, its format is that of a standar=
d course paper: a well-researched thesis, supported by evidence garnered f=
rom primary and secondary sources. Students are expected to write on topic=
s related to their <b>Final Projects</b> (see below). </p> <p> <b>The Fin=
al Project</b> is a major collaborative effort to build a historical
websit=
e in service to an organization outside the University. Students will work=
in groups of 2-4, collaboratively building a substantive site which balanc=
es scholarly merit with the interests of the sponsoring organization and
ac=
cessibility to the general public. We have assembled a list of <a href=3D"=
http://2012.hackinghistory.ca/wp-content/uploads/2012/08/wpid-ProjectGuidel=

ines1.html">Project Guidelines</a> for more detailed discussion &amp;
marki=
ng breakdown. </p> </div> <div id=3D"outline-container-4-1" class=3D"ou=
tline-3"> <h3 id=3D"sec-4-1">Late Policy</h3> <div
class=3D"outline-text-3"=
id=3D"text-4-1"> <p><b>Blogs:</b> blog postings are due by noon <i>the da=
y before class</i>. Late blog postings will not be marked. </p> <p>
<b>STA'=
s:</b> 5%/day late penalty for the first 4 days, after which they will
not =
be marked. </p> <p> <b>Paper:</b> 3%/day. </p> <p> <b>Final Project:</b>
It=
is <i>essential</i> that you complete your final project on time in order =
to get feedback from the sponsoring organization and organize the
handoff o=
f the project. The various deadlines for the project (see <a
href=3D"http:/=
/2012.hackinghistory.ca/wp-content/uploads/2012/08/wpid-ProjectGuidelines.h=

tml">Project Guidelines</a>) are firm. <b>DO NOT MISS THEM.</b> </p></div=
> </div> <div id=3D"outline-container-4-2" class=3D"outline-3"> <h3 id=3D=
"sec-4-2"><a name=3D"texts" id=3D"texts"></a>Project Timetable</h3> <div
cl=
ass=3D"outline-text-3" id=3D"text-4-2"> <ul> <li><span class=3D"timestamp-=
wrapper"> <span class=3D"timestamp">2012-09-27 Thu</span></span>:
Detailed =
assignment handed out with preliminary partner suggestions </li>
<li><span =
class=3D"timestamp-wrapper"> <span class=3D"timestamp">2012-11-01
Thu</span=
></span>: Hand in preliminary (individual) project proposal. </li> <li><s=
pan class=3D"timestamp-wrapper"> <span class=3D"timestamp">2012-11-29
Thu</=
span></span> Presentation of Final (group) Proposal </li> <li><span class=
=3D"timestamp-wrapper"> <span class=3D"timestamp">2013-01-07
Mon</span></sp=
an>: Placement begins (approximate) </li> <li><span
class=3D"timestamp-wrap=
per"> <span class=3D"timestamp">2013-02-21 Thu</span></span>:
Intermediate =
Status Report </li> <li><span class=3D"timestamp-wrapper"> <span
class=3D"t=
imestamp">2013-03-21 Thu</span></span>: Submission to Community Partner
</l=
i> <li><span class=3D"timestamp-wrapper"> <span
class=3D"timestamp">2013-04=
-04 Thu</span></span>: Project Open House/FINAL DUE DATE </li> </ul> </di=
v> </div> </div> <div id=3D"outline-container-5" class=3D"outline-2"> <h2=
id=3D"sec-5"><span style=3D"text-decoration:underline;">Texts</span></h2> =
<div class=3D"outline-text-2" id=3D"text-5"> <p>All texts for this course =
are online, either in the public web or as pdfs. Most of them are publicly=
available. You may want physical copies of some books; these are availabl=
e at <a href=3D"http://www.amazon.ca">Amazon</a> or by special order
from a=
ny sizable bookstore. </p><ul> <li>Cohen &amp; Rosenzweig, <i>Digital Hist=
ory</i> (<a
href=3D"http://chnm.gmu.edu/digitalhistory/">http://chnm.gmu.ed=
u/digitalhistory/</a>) </li> <li>C. Kelty, <i>Two Bits</i> (<a
href=3D"http=
://twobits.net/read/">http://twobits.net/read/</a>) </li> <li>D. Brown,
<i>=
Communicating Design: Developing Web Site Documentation for Design and
Plan=
ning</i> (<a
href=3D"http://communicatingdesign.com/">http://communicatingd=
esign.com/</a>) </li> </ul> <p>A sizable collection of links is also store=
d in a <a href=3D"http://www.zotero.org">Zotero</a> database, having
been m=
erged with the <a href=3D"https://www.zotero.org/groups/25659/">course
bibl=
iogrpahy</a>. </p></div> </div> <div id=3D"outline-container-6" class=3D"=
outline-2"> <h2 id=3D"sec-6"><a name=3D"outline1"
id=3D"outline1"></a>Tools=
</h2> <div class=3D"outline-text-2" id=3D"text-6"> <p>We'll be using a num=
ber of important software tools, some of them very easy to use, some of
the=
m harder. All of them are free (as in beer, and usually as in speech) and =
most run on all three major platforms (Windows, Mac, Linux) or on the
web. =
See the <a href=3D"http://2012.hackinghistory.ca/wp-content/uploads/2012/0=
8/wpid-Tools.html">Tools</a> page for more details. </p></div> </div> <di=
v id=3D"outline-container-7" class=3D"outline-2"> <h2
id=3D"sec-7">Outline =
for Semester 1</h2> <div class=3D"outline-text-2" id=3D"text-7"> </div> =
<div id=3D"outline-container-7-1" class=3D"outline-3"> <h3
id=3D"sec-7-1"><=
span class=3D"timestamp-wrapper"> <span class=3D"timestamp">2012-09-13
Thu<=
/span></span> Hacking History//what is digital history?</h3> <div
class=3D"=
outline-text-3" id=3D"text-7-1"> <p>Why we should write history, why every=
one should do it, and why that means we need the Web. Hacker cultures, col=
laborative learning, knowledge sharing, non-expert culture. </p> </div> =
<div id=3D"outline-container-7-1-1" class=3D"outline-4"> <h4
id=3D"sec-7-1-=
1">Background:</h4> <div class=3D"outline-text-4" id=3D"text-7-1-1"> <ul> =
<li><a
href=3D"http://www.journalofamericanhistory.org/issues/952/interchan=
ge/index.html">JAH - The Promise of Digital History</a>, <a
href=3D"http://=
writinghistory.trincoll.edu/revisioning/tanaka-2012-spring/">Pasts in a
Dig=
ital Age</a> </li> <li>Mark Poster, "<a
href=3D"http://www.hnet.uci.edu/mpo=
ster/writings/democ.html">Cyberdemocracy</a>" </li> </ul> </div> </div> =
<div id=3D"outline-container-7-1-2" class=3D"outline-4"> <h4 id=3D"sec-7-1=
-2">Lab: Technical Introduction</h4> <div class=3D"outline-text-4" id=3D"t=
ext-7-1-2"> <ul> <li>Wordpress &amp; the course site. </li> <li>Blogging=
&amp; social media review. </li> <li>Preliminary listing of potential NGO=
partners. %2

bug#12227: 24.1.50; xml.el: xml-entity-alist is pre-ecaped!

[Chong Yidong]

Matt Price <matt.price@utoronto.ca> writes:

> Unfortunately the current version of xml.el has two of the entities
> pre-escaped:
>
> (defvar xml-entity-alist
> '(("lt" . "&#60;")
> ("gt" . ">")
> ("apos" . "'")
> ("quot" . "\"")
> ("amp" . "&#38;"))
> "Alist mapping XML entities to their replacement text.")
>
> this creates invalid xml output.

Please provide an example of why you think this is a bug.

> ("amp" . "&"))

This would be wrong.  XML entity substitution is recursive, so the above
would cause `AT&amp;T;' to expand to `AT&T;', and then further
substitution would fail since there is no entity `&T;' defined.

The way it is set up now, `AT&amp;T;' expands to `AT&#38;T;', which
finally gives the literal text `AT&T;'.