summaryrefslogtreecommitdiff
path: root/tests/Tests
Commit message (Collapse)AuthorAge
* Export Text.Pandoc.Error in Text.Pandoc.John MacFarlane2016-10-24
| | | | [API change]
* Tighten up parsing of raw email addresses.John MacFarlane2016-10-23
| | | | | | | | | | Technically `**@user` is a valid email address, but if we allow things like this, we get bad results in markdown flavors that autolink raw email addresses. (See #2940.) So we exclude a few valid email addresses in order to avoid these more common bad cases. Closes #2940.
* Add option for top-level division typeAlbert Krewinkel2016-10-19
| | | | | | | | | | The `--chapters` option is replaced with `--top-level-division` which allows users to specify the type as which top-level headers should be output. Possible values are `section` (the default), `chapter`, or `part`. The formats LaTeX, ConTeXt, and Docbook allow `part` as top-level division, TEI only allows to set the `type` attribute on `div` containers. The writers are altered to respect this option in a sensible way.
* Merge pull request #3165 from hubertp-lshift/feature/odt-imageJohn MacFarlane2016-10-18
|\ | | | | [odt] images parser
| * Infer caption from the text following the imgHubert Plociniczak2016-10-17
| | | | | | | | | | | | | | Frame can contain other frames with the text boxes. This is something that has not been considered before and meant that the whole construction of images was broken in those cases. Also the captions were fixed/ignored.
* | RST reader: Add test for space-before-note.Jesse Rosenthal2016-10-17
| |
* | Org reader: allow figure with empty captionAlbert Krewinkel2016-10-14
| | | | | | | | | | | | | | | | | | A `#+CAPTION` attribute before an image is enough to turn an image into a figure. This wasn't the case because the `parseFromString` function, which processes the caption value, would fail on empty values. Adding a newline character to the caption value fixes this. Fixes: #3161
* | Remove Tests.ArbitraryJesse Rosenthal2016-10-14
| | | | | | | | Use exported Arbitrary instances from pandoc-types instead.
* | Parse line-oriented markup as LineBlockAlbert Krewinkel2016-10-13
|/ | | | | | | | Markup-features focusing on lines as distinctive part of the markup are read into `LineBlock` elements. This currently means line blocks in reStructuredText and Markdown (the latter only if the `line_block` extension is enabled), the `linegroup`/`line` combination from the Docbook 5.1 working draft, and Org-mode `VERSE` blocks.
* Markdown writer: add test for note placement.Jesse Rosenthal2016-10-11
|
* LaTeX writer: change braced backtick to \textasciigrave{}Jesse Rosenthal2016-09-20
| | | | | | | Backticks in verbatim environments are converted to open-single-quotes. This change makes them appear as backticks. This corresponds to how we treat `'' in verbatim environments (with \textquotesingle{}).
* Add test for backtick in verbatim.Jesse Rosenthal2016-09-19
|
* Org reader: respect unnumbered header propertyAlbert Krewinkel2016-08-30
| | | | | | | | | | | Sections the `unnumbered` property should, as the name implies, be excluded from the automatic numbering of section provided by some output formats. The Pandoc convention for this is to add an "unnumbered" class to the header. The reader treats properties as key-value pairs per default, so a special case is added to translate the above property to a class instead. Closes #3095.
* Merge branch 'org-meta-handling'Albert Krewinkel2016-08-29
|\
| * Org reader: respect `creator` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | | | | | The `creator` option controls whether the creator meta-field should be included in the final markup. Setting `#+OPTIONS: creator:nil` will drop the creator field from the final meta-data output. Org-mode recognizes the special value `comment` for this field, causing the creator to be included in a comment. This is difficult to translate to Pandoc internals and is hence interpreted the same as other truish values (i.e. the meta field is kept if it's present).
| * Org reader: respect `email` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | The `email` option controls whether the email meta-field should be included in the final markup. Setting `#+OPTIONS: email:nil` will drop the email field from the final meta-data output.
| * Org reader: respect `author` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | The `author` option controls whether the author should be included in the final markup. Setting `#+OPTIONS: author:nil` will drop the author from the final meta-data output.
| * Put Org reader export option tests into test groupAlbert Krewinkel2016-08-29
| | | | | | | | | | Using a separate test group instead of prefixing the test subject should be clearer than the current approach.
| * Org reader: read HTML_head as header-includesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | HTML-specific head content can be defined in `#+HTML_head` lines. They are parsed as format-specific inlines to ensure that they will only show up in HTML output.
| * Org reader: set classoption meta from LaTeX_class_optionsAlbert Krewinkel2016-08-29
| |
| * Org reader: set documentclass meta from LaTeX_classAlbert Krewinkel2016-08-29
| |
| * Org reader: read LaTeX_header as header-includesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | LaTeX-specific header commands can be defined in `#+LaTeX_header` lines. They are parsed as format-specific inlines to ensure that they will only show up in LaTeX output.
| * Org reader: give precedence to later meta linesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | The last meta-line of any given type is the significant line. Previously the value of the first line was kept, even if more lines of the same type were encounterd.
| * Org reader: allow multiple, comma-separated authorsAlbert Krewinkel2016-08-29
| | | | | | | | | | Multiple authors can be specified in the `#+AUTHOR` meta line if they are given as a comma-separated list.
| * Org reader: read markup only for special meta keysAlbert Krewinkel2016-08-29
| | | | | | | | | | Most meta-keys should be read as normal string values, only a few are interpreted as marked-up text.
* | Docx reader: test for nested anchor spans in headerJesse Rosenthal2016-08-29
|/ | | | | This ensures that anchor spans in header with content (or with other anchor spans inside) will resolve to links to a header id properly.
* Docx writer test: comment out function to make compiler happy.Jesse Rosenthal2016-08-15
|
* Docx writer: test for custom styles.Jesse Rosenthal2016-08-15
| | | | | | | | This just tests whether a custom style with a recognizable style (italic etc, defined in a reference.docx) will roundtrip back to that format (i.e., whether `<span custom-style="Emphasized">` will roundtrip to `Emph`). The custom styles are defined in the `custom-style-reference.docx` included in the docx dir.
* Docx writer tests: allow for altered round tripJesse Rosenthal2016-08-15
| | | | | | Sometimes we will want to get back something different than we started with in a round-trip test. This allows for that, and makes the perfect roundtrip a special case.
* Merge pull request #3065 from tarleb/org-verse-indentJohn MacFarlane2016-08-09
|\ | | | | Org reader: preserve indentation of verse lines
| * Org reader: preserve indentation of verse linesAlbert Krewinkel2016-08-08
| | | | | | | | | | | | | | Leading spaces in verse lines are converted to non-breaking spaces, so indentation is preserved. This fixes #3064.
* | Org reader: ensure image sources are proper linksAlbert Krewinkel2016-08-09
|/ | | | | | | | | | | | | Image sources as those in plain images, image links, or figures, must be proper URIs or relative file paths to be recognized as images. This restriction is now enforced for all image sources. This also fixes the reader's usage of uncleaned image sources, leading to `file:` prefixes not being deleted from figure images (e.g. `[[file:image.jpg]]` leading to a broken image `<img src="file:image.jpg"/>) Thanks to @bsag for noticing this bug.
* Removed some redundant class constraints.John MacFarlane2016-07-14
|
* Org reader: fix parsing of verbatim inlinesAlbert Krewinkel2016-07-14
| | | | | | | | | | Org rules for allowed characters before or after markup chars were not checked for verbatim text. This resultet in wrong parsing outcomes of if the verbatim text contained e.g. space enclosed markup characters as part of the text (`=is_substr = True=`). Forcing the parser to update the positions of allowed/forbidden markup border characters fixes this. This fixes #3016.
* Org reader: support headline levels export settingAlbert Krewinkel2016-07-03
| | | | | The depths of headlines can be modified using the `H` option. Deeper headlines will be converted to lists.
* Org reader: support archived trees export optionsAlbert Krewinkel2016-07-01
| | | | | | | Handling of archived trees can be modified using the `arch` option. Archived trees are either dropped, exported completely, or collapsed to include just the header when the `arch` option is nil, non-nil, or `headline`, respectively.
* Added Zim Wiki writer, template and tests.Alex Ivkin2016-06-30
|
* LaTeX reader: fixed `\cite` so it is a NormalCitation not AuthorInText.John MacFarlane2016-06-29
|
* Org reader: support figure labelsAlbert Krewinkel2016-06-26
| | | | | | | | Figure labels given as `#+LABEL: thelabel` are used as the ID of the respective image. This allows e.g. the LaTeX to add proper `\label` markup. This fixes half of #2496 and #2999.
* Docx reader: add tests for commentsJesse Rosenthal2016-06-23
| | | | | | We test for comments, using all track-changes options. Note that we should only output comments if `--track-changes=all`. We also test for emitting warnings if there is complicated formatting.
* Docx reader tests: Add tests for warnings.Jesse Rosenthal2016-06-23
| | | | We test to see if we emit any warnings.
* Org reader: support arbitrary raw inlinesAlbert Krewinkel2016-06-13
| | | | | | | Org mode allows arbitrary raw inlines ("export snippets" in Emacs parlance) to be included as `@@format:raw foreign format text@@`. Support for this features is added to the Org reader.
* Org reader: add support for "Berkeley-style" citesAlbert Krewinkel2016-06-05
| | | | | | | | | A specification for an official Org-mode citation syntax was drafted by Richard Lawrence and enhanced with the help of others on the orgmode mailing list. Basic support for this citation style is added to the reader. This closes #1978.
* Merge pull request #2950 from tarleb/org-ref-supportJohn MacFarlane2016-05-31
|\ | | | | Org reader: support org-ref style citations
| * Org reader: support org-ref style citationsAlbert Krewinkel2016-05-27
| | | | | | | | | | | | The *org-ref* package is an org-mode extension commonly used to manage citations in org documents. Basic support for the `cite:citeKey` and `[[cite:citeKey][prefix text::suffix text]]` syntax is added.
* | Org reader: support new syntax for export blocksAlbert Krewinkel2016-05-29
|/ | | | | | | Org-mode version 9 usees a new syntax for export blocks. Instead of `#+BEGIN_<FORMAT>`, where `<FORMAT>` is the format of the block's content, the new format uses `#+BEGIN_export <FORMAT>` instead. Both types are supported.
* Org reader: respect drawer export settingAlbert Krewinkel2016-05-23
| | | | | The `d` export option can be used to control which drawers are exported and which are discarded. Basic support for this option is added here.
* Org reader/writer: use CUSTOM_ID in propertiesAlbert Krewinkel2016-05-22
| | | | | | | | | The `ID` property is reserved for internal use by Org-mode and should not be used. The `CUSTOM_ID` property is to be used instead, it is converted to the `ID` property for certain export format. The reader and writer erroneously used `ID`. This is corrected by using `CUSTOM_ID` where appropriate.
* Org reader: add :PROPERTIES: drawer supportAlbert Krewinkel2016-05-20
| | | | | | | | | | | | | | Headers can have optional `:PROPERTIES:` drawers associated with them. These drawers contain key/value pairs like the header's `id`. The reader adds all listed pairs to the header's attributes; `id` and `class` attributes are handled specially to match the way `Attr` are defined. This also changes behavior of how drawers of unknown type are handled. Instead of including all unknown drawers, those are not read/exported, thereby matching current Emacs behavior. This closes #1877.
* Org reader: add support for ATTR_HTML attributesAlbert Krewinkel2016-05-19
| | | | | | | | | | | Arbitrary key-value pairs can be added to some block types using a `#+ATTR_HTML` line before the block. Emacs Org-mode only includes these when exporting to HTML, but since we cannot make this distinction here, the attributes are always added. The functionality is now supported for figures. This closes #1906.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 01:42:15 +0000