From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Matt Price Newsgroups: gmane.emacs.bugs Subject: bug#12227: 24.1.50; xml.el: xml-entity-alist is pre-ecaped! Date: Sat, 18 Aug 2012 12:24:00 -0400 Message-ID: <502FC1A0.6040101@utoronto.ca> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1345312692 26158 80.91.229.3 (18 Aug 2012 17:58:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Aug 2012 17:58:12 +0000 (UTC) To: 12227@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Aug 18 19:58:12 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T2nHl-0001ov-T4 for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Aug 2012 19:58:10 +0200 Original-Received: from localhost ([::1]:49992 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2nHk-0005i8-QQ for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Aug 2012 13:58:08 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:60812) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2nHe-0005cV-LQ for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 13:58:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T2nHb-0004wB-KU for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 13:58:02 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56439) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2nHb-0004w7-Eo for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 13:57:59 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1T2nHe-0003ER-AG for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 13:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Matt Price Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 Aug 2012 17:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 12227 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.134531266012383 (code B ref -1); Sat, 18 Aug 2012 17:58:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 18 Aug 2012 17:57:40 +0000 Original-Received: from localhost ([127.0.0.1]:37748 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1T2nHG-0003Dd-7A for submit@debbugs.gnu.org; Sat, 18 Aug 2012 13:57:40 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43111) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1T2low-000193-HC for submit@debbugs.gnu.org; Sat, 18 Aug 2012 12:24:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T2loq-0003V0-PM for submit@debbugs.gnu.org; Sat, 18 Aug 2012 12:24:15 -0400 Original-Received: from lists.gnu.org ([208.118.235.17]:51938) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2loq-0003Uw-LA for submit@debbugs.gnu.org; Sat, 18 Aug 2012 12:24:12 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:51413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2lon-0004Jh-O8 for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 12:24:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T2loj-0003Ta-L8 for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 12:24:09 -0400 Original-Received: from bureau60.ns.utoronto.ca ([128.100.132.147]:40465) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T2loj-0003TT-Cu for bug-gnu-emacs@gnu.org; Sat, 18 Aug 2012 12:24:05 -0400 Original-Received: from [192.168.0.105] (69-165-170-213.dsl.teksavvy.com [69.165.170.213]) (authenticated bits=0) by bureau60.ns.utoronto.ca (8.13.8/8.13.8) with ESMTP id q7IGO1mx020480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 18 Aug 2012 12:24:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=utoronto.ca; s=beta; t=1345307043; bh=a/FK8vcmchA0Ne2PbWI2irVFB4tBu5bnBth6ZP4GaOw=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=wc+zO3CFcucYVW9senu+ak+fYILiDMpEVOMJ6AJGyYdzvLjYoFJPfHLOxGnCTBI0K DtmPku//zp8tzasvk/Rs1N/uOFjO1qU2GB1D0ljG4gemrPjjq7UIIqrpcbEDd4gvp3 qKcf/DLuFH4U83hPJ/bHau+dkvOInyA8og3sDTSY= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120724 Thunderbird/15.0 X-Enigmail-Version: 1.5a1pre X-PMX-Spam: Gauge=XIIIIIIIII, Probability=19%, Report=' RATWARE_SIGNATURE_3 2, HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_10000_PLUS 0, DATE_TZ_NA 0, RDNS_GENERIC_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, URI_ENDS_IN_PHP 0, __ANY_URI 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_MSGID 0, __INT_PROD_COMP 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RATWARE_SIGNATURE_3 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __USER_AGENT 0' X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Mailman-Approved-At: Sat, 18 Aug 2012 13:57:37 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:63272 Archived-At: "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: =20 =20 =20 M-x =20 C-x b M-x y C-x=20 b =20 =20 C-s=20 e s c a p e C-a C-/ =20 =20 M-x C-g M-x e l i s =20 =20 =20 =20 l i s p - m =20 M-x C-g M-x e v a l - b u f f =20 C-/ C-/ =20 =20 =20 M-x e v=20 a l - b u f f C-x b M-x =20 =20 C-x =20 n =20 C-x b m e s s =20 > C-x b C-x k =20 C-x b ; ; SPC =20 C-a C-SPC =20 =20 C-w=20 M-x C-x b C-x b h i s =20 M-x y M-x r e p o r t - e m a c=20 s - b u g Recent messages: parsed!!

Table of Contents

<= /div>

Logistics

<= colgroup> <= tr>
Instructor:Matt Price<= /td>
Email:matt.= price@utoronto.ca
Tel:978-8472
Office Hrs:SS 3077 M 12-2

= Introduction

In the year of your birth, the = World Wide Web 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.

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 HTML and Javascript, as well as just enough = PHP to work with the Wordpress 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.

<= /div>

Course Structure

First Semeste= r

In the first seme= ster we will meet on a weekly basis to discuss the week's readings ("Readin= gs" in the outline) and work together o= n a technical or interpretative task that will be defined in advance ("Lab"= in the outline). 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.

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.

Second Semes= ter

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.

Course Requirements

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.

The class has 5 kinds of assignments: <= /p>

  • 19 Weekly Blog Postings (both semesters, 20%)
    • <= li>4 "Short Technical Assignments" (STA's, first semester, 10%)
  • 1 Website Review (First Semester, 5%)
  • One Written = Paper (7-9 pp, Jan 10, 10%)
  • The Final Project (website, = ongoing but due April 4, 45%)

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> Blog Postings 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 responses to t= he weekly readings. In the second semester, they will instead generally= take the form of progress reports in which you discuss your final p= rojects and your interactions with partnering organizations, or of short= written pieces from your project site (see below). In the event that = I want you to focus on something else, I will inform you one week in advanc= e in class. 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 regular blog post and a review or response paper<= /a>. Citations of online sources should use hyperlinks; other material sho= uld be cited as in printed assignments (I recommend Chicago Manual of Style, 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 & Apr. 3).

Short Technical Assignmen= ts (STA's) 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.

The Website Review 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).=

The Paper 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 Final Projects (see below).

The Fin= al Project 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 Project Guidelines for more detailed discussion & marki= ng breakdown.

Late Policy

Blogs: blog postings are due by noon the da= y before class. Late blog postings will not be marked.

STA'= s: 5%/day late penalty for the first 4 days, after which they will not = be marked.

Paper: 3%/day.

Final Project: It= is essential 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 Project Guidelines) are firm. DO NOT MISS THEM.

Project Timetable

  • 2012-09-27 Thu: Detailed = assignment handed out with preliminary partner suggestions
  • 2012-11-01 Thu: Hand in preliminary (individual) project proposal.
  • 2012-11-29 Thu Presentation of Final (group) Proposal
  • 2013-01-07 Mon: Placement begins (approximate)
  • 2013-02-21 Thu: Intermediate = Status Report
  • 2013-03-21 Thu: Submission to Community Partner
  • 2013-04= -04 Thu: Project Open House/FINAL DUE DATE
Texts =

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 Amazon or by special order from a= ny sizable bookstore.

A sizable collection of links is also store= d in a Zotero database, having been m= erged with the course bibl= iogrpahy.

Tools=

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 Tools page for more details.

Outline = for Semester 1

=

<= span class=3D"timestamp-wrapper"> 2012-09-13 Thu<= /span> Hacking History//what is digital history?

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.

= =

Lab: Technical Introduction

  • Wordpress & the course site.
  • Blogging= & social media review.
  • Preliminary listing of potential NGO= partners. %2