| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
| |
This speeds up the textile reader by about a factor of 4.
But the reader is still very slow, compared to others readers.
|
| | |
|
| |
|
|
|
|
|
| |
This affected notes occuring before punctuation, e.g.
`foo[1].`.
Closes #518.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Better to keep reader and writer options separate.
|
| |
|
|
|
|
|
|
|
| |
This is the beginning of a larger transition that will make
Options, not ParserState, the parameter of the read functions.
(Options will also be used in writers, in place of WriterOptions.)
Next step is to remove strict, replacing it with granular
tests for different extensions.
|
| | |
|
| |
|
|
|
| |
No other module directly imports Parsec. This will make it easier
to change the parsing backend in the future, if we want to.
|
| | |
|
| |
|
|
|
|
|
| |
Square brackets need to be used when the link isn't surrounded by
spaces or punctuation, or when the URL ending may be ambiguous.
Closes #564.
|
| |
|
|
| |
Closes #517.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #473.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
$ cabal configure --haddock-option=-v3
$ cabal haddock -v3
Creating interface...
100% ( 2 / 2) in 'Text.Pandoc.Readers.Native'
Checking module Text.Pandoc.Readers.HTML...
Creating interface...
50% ( 4 / 8) in 'Text.Pandoc.Readers.HTML'
Checking module Text.Pandoc.Readers.Textile...
Creating interface...
haddock: internal error: lexical error
/usr/bin/haddock returned ExitFailure 1
Patch changes UTF-8 spaces to ASCII spaces.
It's a known haddock issue:
http://www.haskell.org/pipermail/haskell-cafe/2012-March/099870.html
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* `---` is always em-dash, `--` is always en-dash.
* pandoc no longer tries to guess when `-` should be en-dash.
* A new option, `--old-dashes`, is provided for legacy documents.
Rationale: The rules for en-dash are too complex and
language-dependent for a guesser to work reliably. This
change gives users greater control. The alternative of
using unicode isn't very good, since unicode em- and en-
dashes are barely distinguishable in a monospace font.
|
| |
|
|
|
|
|
|
|
|
|
| |
* Added stateLastStrPos to ParserState. This lets us keep track
of whether we're parsing the position immediately after a 'str'.
If we encounter a ' in such a location, it must be an apostrophe,
and can't be a single quote start.
* Set this in the markdown, textile, html, and rst str parsers.
* Closes #360.
|
| | |
|
| |
|
|
|
|
|
|
| |
Additional related changes:
* URLs in Code in autolinks now use class "url".
* Require highlighting-kate 0.2.8.2, which omits the final <br/> tag,
essential for inline code.
|
| |
|
|
|
|
|
| |
The old TeX, HtmlInline and RawHtml elements have been removed
and replaced by generic RawInline and RawBlock elements.
All modules updated to use the new raw elements.
|
| | |
|
| |
|
|
|
| |
The problem was a missing 'try' in the maybeExplicitBlock parser.
Test case, a paragraph beginning with 'p', has been added.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* The new reader is faster and more accurate.
* API changes for Text.Pandoc.Readers.HTML:
- removed rawHtmlBlock, anyHtmlBlockTag, anyHtmlInlineTag,
anyHtmlTag, anyHtmlEndTag, htmlEndTag, extractTagType,
htmlBlockElement, htmlComment
- added htmlTag, htmlInBalanced, isInlineTag, isBlockTag, isTextTag
* tagsoup is a new dependency.
* Text.Pandoc.Parsing: Generalized type on readWith.
* Benchmark.hs: Added length calculation to force full evaluation.
* Updated HTML reader tests.
* Updated markdown and textile readers to use the functions from
the HTML reader.
* Note: The markdown reader now correctly handles some cases it did not
before. For example:
<hr/>
is reproduced without adding a space.
<script>
a = '<b>';
</script>
is parsed correctly.
|
| | |
|
| |
|
|
|
| |
We now parse PBS(Public Broadcasting System) as if it were
"PBS (Public Broadcasting System)".
|
| | |
|
| |
|
|
|
| |
+ Parameterized smartPunctuation on an inline parser.
+ Handle smartPunctuation in Textile reader.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The smartPuncutation parser from the markdown parser
was being used, but this creates two problems:
* smart punctuation rules are slightly different in textile,
for example, a single dash wish space around becomes an
En dash.
* the following gets parsed as a double quoted string followed
by a colon, rather than as a link:
"emphasized text":http://my.url.com
This needs rethinking.
|
| | |
|
| | |
|
| |
|
|
| |
This is consistent with how the other readers work.
|
| |
|
|
|
|
| |
* A single hyphen between two word characters is no longer a
potential strikeout-starter.
* Acronym explanations are dropped.
|
| |
|
|
|
|
| |
It's part of the textile spec to allow raw HTML,
just as with markdown.
-R is no longer needed in test suite.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
entries
|
| | |
|
