aboutsummaryrefslogtreecommitdiff
path: root/test/lhs-test.html+lhs
AgeCommit message (Collapse)AuthorFilesLines
2019-07-14Update test for new skylighting.John MacFarlane1-7/+6
2019-05-27Use skylighting 0.8.John MacFarlane1-14/+16
2019-02-10Use latest skylighting.John MacFarlane1-1/+1
2019-01-08Removed superfluous sourceCode class on code blocks.John MacFarlane1-1/+1
* These were added by the RST reader and, for literate Haskell, by the Markdown and LaTeX readers. There is no point to this class, and it is not applied consistently by all readers. See #5047. * Reverse order of `literate` and `haskell` classes on code blocks when parsing literate Haskell. Better if `haskell` comes first.
2018-12-14Remove unnecessary type="text/css" on style and link for HTML5.John MacFarlane1-2/+2
Closes #5146.
2018-10-08Fixed tests for new skylighting.John MacFarlane1-4/+4
2018-06-09Use skylighting 0.7.2. Adjust tests.John MacFarlane1-6/+4
This should fix commercialhaskell/stackage#3719, once a new release is made.
2017-12-26HTML writer: Use br elements in line blocks...John MacFarlane1-1/+0
instead of relying on CSS. Closes #4162. HTML-based templates have had the custom CSS for div.line-block removed. Those maintaining custom templates will want to remove this too. We still enclose line blocks in a div with class line-block.
2017-12-10Changes for skylighting-0.5.John MacFarlane1-27/+37
This fixes a bug in 2.0.4, whereby pandoc could not read the theme files generated with `--print-highlight-style`. It also fixes some CSS issues involving line numbers. Highlighted code blocks are now enclosed in a div with class sourceCode. Highlighting CSS no longer sets a generic color for pre and code; we only set these for class `sourceCode`. This will close #4133 and #4128.
2017-12-03Include default CSS for 'underline' class in HTML-based templates.John MacFarlane1-0/+1
2017-11-28Update tests for new skylighting.John MacFarlane1-2/+4
2017-11-21Update tests for skylighting changes.John MacFarlane1-7/+7
2017-11-04Fix test output for latest skylighting.John MacFarlane1-3/+3
2017-11-03Updated tests.John MacFarlane1-1/+1
2017-11-02Improved support for columns in HTML.John MacFarlane1-3/+3
* Move as much as possible to the CSS in the template. * Ensure that all the HTML-based templates (including epub) contain the CSS for columns. * Columns default to 50% width unless they are given a width attribute. Closes #4028.
2017-11-02Use latest skylighting; ensure no duplicate ids on code lines.John MacFarlane1-3/+3
The line identifiers are built using the code block's identifier as a prefix. If the code block has null identifier, we use "cb1", "cb2", etc. Closes #4031.
2017-10-26Use skylighting 0.4.2.John MacFarlane1-6/+5
This prevents the problem with extra space around highlighted code blocks (closes #3996). Note that we no longer put an enclosing div around highlighted code blocks. The pre is the outer element, just as for unhighlighted blocks.
2017-09-09Updated lhs-test for new skylighting.John MacFarlane1-37/+54
2017-08-14Implement multicolumn support for slide formats.John MacFarlane1-0/+1
The structure expected is: <div class="columns"> <div class="column" width="40%"> contents... </div> <div class="column" width="60%"> contents... </div> </div> Support has been added for beamer and all HTML slide formats. Closes #1710. Note: later we could add a more elegant way to create this structure in Markdown than to use raw HTML div elements. This would come for free with a "native div syntax" (#168). Or we could devise something specific to slides
2017-04-25HTML line block: Use class instead of style attribute.John MacFarlane1-0/+1
We now issue `<div class="line-block">` and include a default definition for `line-block` in the default templates, instead of hard-coding a `style` on the div. Closes #1623.
2017-03-09HTML writer: fallback to basename rather than Untitled.John MacFarlane1-1/+1
2017-03-04Regularized CSS in html/epub/html slide templates.John MacFarlane1-1/+4
All templates now include `code{white-space: pre-wrap}` and CSS for `q` if `--html-q-tags` is used. Previously some templates had `pre` and others `pre-wrap`; the `q` styles were only sometimes included. See #3485.
2017-03-04templates: CSS for .smallcaps, closes #1592 (#3485)Mauro Bieg1-1/+1
2017-03-04HTML writer: issue warning if no title specified and template used.John MacFarlane1-1/+1
See #3473.
2017-03-04Make default.html5 polyglot markup conformant. (#3473)John Luke Bentley1-4/+4
Polyglot markup is HTML5 that is also valid XHTML. See <https://www.w3.org/TR/html-polyglot>. With this change, pandoc's html5 writer creates HTML that is both valid HTML5 and valid XHTML. See jgm/pandoc-templates#237 for prior discussion. * Add xml namespace to `<html>` element. * Make all `<meta>` elements self closing. See <https://www.w3.org/TR/html-polyglot/#empty-elements>. * Add `xml:lang` attribute on `<html>` element, defaulting to blank, and always include `lang` attribute, even when blank. See <https://www.w3.org/TR/html-polyglot/#language-attributes>. * Update test files for template changes. The key justification for having language values default to blank: it turns out the HTML5 spec requires it (as I read it). Under [the HTML5 spec, section "3.2.5.3. The lang and xml:lang attributes"](https://www.w3.org/TR/html/dom.html#the-lang-and-xmllang-attributes), providing attributes with blank contents both: * Has meaning, "unknown", and * Is a MUST (written as "must") if a language value is not provided ... > The lang attribute (in no namespace) specifies the primary language > for the element's contents and for any of the element's attributes that > contain text. Its value must be a valid BCP 47 language tag, or the > empty string. Setting the attribute to the empty string indicates that > the primary language is unknown. In short, it seems that where a language value is not provided then a blank value MUST be provided for Polyglot Markup conformance, because the HTML5 spec stipulates a "must". So although the Polyglot Markup spec is unclear on this issue it would seem that if it was correctly written, it would therefore require blank attributes. Further justifications are found at https://github.com/jgm/pandoc-templates/issues/237#issuecomment-275584181 (but the HTML5 spec justification given above would seem to be the clincher). In addition to having lang-values-default-to-blank I recommend that, when an author does not provide a lang value, then upon on pandoc command execution a warning message like the following be provided: > Polyglot markup stipulates that 'The root element SHOULD always specify > the language'. It is therefore recommended you specify a language value in > your source document. See > <https://www.w3.org/International/articles/language-tags/> for valid > language values.
2017-02-04Moved tests/ -> test/.John MacFarlane1-0/+66
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-14 17:33:43 +0000