git.iko.soy/typeable/pandoc
on master help sign in
Updated changelog.
65e118efiddlosopher
debian/changelog+185
@@ -1,3 +1,188 @@
1+pandoc (0.46) unstable; urgency=low
2+
3+ [ John MacFarlane ]
4+
5+ * Made -H, -A, and -B options cumulative: if they are specified
6+ multiple times, multiple files will be included.
7+
8+ * Added optional HTML sanitization using a whitelist.
9+ When this option is specified (--sanitize-html on the command line),
10+ unsafe HTML tags will be replaced by HTML comments, and unsafe HTML
11+ attributes will be removed. This option should be especially useful
12+ for those who want to use pandoc libraries in web applications, where
13+ users will provide the input.
14+
15+ + Main.hs: Added --sanitize-html option.
16+
17+ + Text.Pandoc.Shared: Added stateSanitizeHTML to ParserState.
18+
19+ + Text.Pandoc.Readers.HTML:
20+ - Added whitelists of sanitaryTags and sanitaryAttributes.
21+ - Added parsers to check these lists (and state) to see if a given
22+ tag or attribute should be counted unsafe.
23+ - Modified anyHtmlTag and anyHtmlEndTag to replace unsafe tags
24+ with comments.
25+ - Modified htmlAttribute to remove unsafe attributes.
26+ - Modified htmlScript and htmlStyle to remove these elements if
27+ unsafe.
28+
29+ + Modified README and man pages to document new option.
30+
31+ * Improved handling of email addresses in markdown and reStructuredText.
32+ Consolidated uri and email address parsers. (Resolves Issue #37.)
33+
34+ + New emailAddress and uri parsers in Text.Pandoc.Shared.
35+ - uri parser uses parseURI from Network.URI.
36+ - emailAddress parser properly handles email addresses with periods
37+ in them.
38+
39+ + Removed uri and emailAddress parsers from Text.Pandoc.Readers.RST
40+ and Text.Pandoc.Readers.Markdown.
41+
42+ * Markdown reader:
43+
44+ + Fixed emph parser so that "*hi **there***" is parsed as a Strong
45+ nested in an Emph. (A '*' is only recognized as the end of the
46+ emphasis if it's not the beginning of a strong emphasis.)
47+
48+ + Moved blockQuote parser before list parsers for performance.
49+
50+ + Modified 'source' parser to allow backslash-escapes in URLs.
51+ So, for example, [my](/url\(1\)) yields a link to /url(1).
52+ Resolves Issue #34.
53+
54+ + Disallowed links within links. (Resolves Issue #35.)
55+ - Replaced inlinesInBalanced with inlinesInBalancedBrackets, which
56+ instead of hard-coding the inline parser takes an inline parser
57+ as a parameter.
58+ - Modified reference and inlineNote to use inlinesInBalancedBrackets.
59+ - Removed unneeded inlineString function.
60+ - Added inlineNonLink parser, which is now used in the definition of
61+ reference.
62+ - Added inlineParsers list and redefined inline and inlineNonLink parsers
63+ in terms of it.
64+ - Added failIfLink parser.
65+
66+ + Better handling of parentheses in URLs and quotation marks in titles.
67+ - 'source' parser first tries to parse URL with balanced parentheses;
68+ if that doesn't work, it tries to parse everything beginning with
69+ '(' and ending with ')'.
70+ - source parser now uses an auxiliary function source'.
71+ - linkTitle parser simplified and improved, under assumption that it
72+ will be called in context of source'.
73+
74+ + Make 'block' conditional on strictness state, instead of using
75+ failIfStrict in block parsers. Use a different ordering of parsers
76+ in strict mode (raw HTML block before paragraph) for performance.
77+ In non-strict mode use rawHtmlBlocks instead of htmlBlock.
78+ Simplified htmlBlock, since we know it's only called in strict
79+ mode.
80+
81+ + Improved handling of raw HTML. (Resolves Issue #36.)
82+ - Tags that can be either block or inline (e.g. <ins>) should
83+ be treated as block when appropriate and as inline when
84+ appropriate. Thus, for example,
85+ <ins>hi</ins>
86+ should be treated as a paragraph with inline <ins> tags, while
87+ <ins>
88+ hi
89+ </ins>
90+ should be treated as a paragraph within <ins> tags.
91+ - Moved htmlBlock after para in list of block parsers. This ensures
92+ that tags that can be either block or inline get parsed as inline
93+ when appropriate.
94+ - Modified rawHtmlInline' so that block elements aren't treated as
95+ inline.
96+ - Modified para parser so that paragraphs containing only HTML tags and
97+ blank space are not allowed. Treat these as raw HTML blocks instead.
98+
99+ + Fixed bug wherein HTML preceding a code block could cause it to
100+ be parsed as a paragraph. The problem is that the HTML parser
101+ used to eat all blank space after an HTML block, including the
102+ indentation of the code block. (Resolves Issue #39.)
103+ - In Text.Pandoc.Readers.HTML, removed parsing of following space
104+ from rawHtmlBlock.
105+ - In Text.Pandoc.Readers.Markdown, modified rawHtmlBlocks so that
106+ indentation is eaten *only* on the first line after the HTML
107+ block. This means that in
108+ <div>
109+ foo
110+ <div>
111+ the foo won't be treated as a code block, but in
112+ <div>
113+
114+ foo
115+
116+ </div>
117+ it will. This seems the right approach for least surprise.
118+
119+ * RST reader:
120+
121+ + Fixed bug in parsing explicit links (resolves Issue #44).
122+ The problem was that we were looking for inlines until a '<' character
123+ signaled the start of the URL; so, if you hit a reference-style link,
124+ it would keep looking til the end of the document. Fix: change
125+ inline => (notFollowedBy (char '`') >> inline). Note that this won't
126+ allow code inlines in links, but these aren't allowed in resT anyway.
127+
128+ + Cleaned up parsing of reference names in key blocks and links.
129+ Allow nonquoted reference links to contain isolated '.', '-', '_', so
130+ so that strings like 'a_b_' count as links.
131+
132+ + Removed unnecessary check for following link in str.
133+ This is unnecessary now that link is above str in the definition of
134+ 'inline'.
135+
136+ * HTML reader:
137+
138+ + Modified rawHtmlBlock so it parses </html> and </body> tags.
139+ This allows these tags to be handled correctly in Markdown.
140+ HTML reader now uses rawHtmlBlock', which excludes </html> and </body>,
141+ since these are handled in parseHtml. (Resolves Issue #38.)
142+
143+ + Fixed bug (emph parser was looking for <IT> tag, not <I>).
144+
145+ + Don't interpret contents of style tags as markdown.
146+ (Resolves Issue #40.)
147+ - Added htmlStyle, analagous to htmlScript.
148+ - Use htmlStyle in htmlBlockElement and rawHtmlInline.
149+ - Moved "script" from the list of tags that can be either block or
150+ inline to the list of block tags.
151+
152+ + Modified rawHtmlBlock to use anyHtmlBlockTag instead of anyHtmlTag
153+ and anyHtmlEndTag. This fixes a bug in markdown parsing, where
154+ inline tags would be included in raw HTML blocks.
155+
156+ + Modified anyHtmlBlockTag to test for (not inline) rather than
157+ directly for block. This allows us to handle e.g. docbook in
158+ the markdown reader.
159+
160+ * LaTeX reader: Properly recognize --parse-raw in rawLaTeXInline.
161+ Updated LaTeX reader test to use --parse-raw.
162+
163+ * HTML writer:
164+
165+ + Modified rules for automatic HTML header identifiers to
166+ ensure that identifiers begin with an alphabetic character.
167+ The new rules are described in README. (Resolves Issue #33.)
168+
169+ + Changed handling of titles in HTML writer so you don't get
170+ "titleprefix - " followed by nothing.
171+
172+ * ConTeXt writer: Use wrappers around Doc elements to ensure proper
173+ spacing. Each block element is wrapped with either Pad or Reg.
174+ Pad'ed elements are guaranteed to have a blank line in between.
175+
176+ * RST writer:
177+
178+ + Refactored RST writer to use a record instead of a tuple for state,
179+ and to include options in state so it doesn't need to be passed as
180+ a parameter.
181+
182+ + Use an interpreted text role to render math in restructuredText.
183+ See http://www.american.edu/econ/itex2mml/mathhack.rst for the
184+ strategy.
185+
1pandoc (0.45) unstable; urgency=low
186pandoc (0.45) unstable; urgency=low
2
187
3 [ John MacFarlane ]
188 [ John MacFarlane ]