Age | Commit message (Collapse) | Author | Files | Lines |
|
Org reader: remove partial functions
|
|
Previously we just passed all raw TeX through when MathJax
was used for HTML math. This passed through too much.
With this patch, only raw LaTeX environments that MathJax
can handle get passed through.
This patch also causes raw LaTeX environments to be treated
as math, when possible, with MathML and WebTeX output.
Closes #2758.
|
|
|
|
Partial functions like `head` lead to avoidable errors and should be
avoided. They are replaced with total functions.
This fixes #2991.
|
|
Closes #2985.
|
|
- `writerEmailObfuscation` in `defaultWriterOptions` is now
`NoObfuscation`
- the default for the command-line `--email-obfuscation` option is
now `none`.
Closes #2988.
|
|
Documentation updates
|
|
Org reader: raw inlines in arbitrary formats
|
|
Allow tagsoup 0.14
|
|
Building with the new release went fine here, and it works correctly.
|
|
Raw HTML is kept when the output format is Emacs Org mode.
|
|
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 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 writer.
|
|
Raw TeX is kept verbatim when the output format is Emacs Org mode.
|
|
MultiMarkdown was only mentioned as a supported Markdown dialect but not
as a possible input or output format. A brief mention is added
everywhere the other supported markdown dialects are mentioned.
This closes #2973.
|
|
This is for better compatibility with babelmark2.
|
|
Docbook writer: Declare xlink namespace in Docbook5 output
|
|
Here's a minimal case:
\documentclass[]{article}
\usepackage{hyperref}
\begin{document}
\section{\%á}
\end{document}
Without this change, this fails on the second invocation of xelatex.
See https://tex.stackexchange.com/questions/313266/and-non-ascii-characters-in-headings
This affects inputs this like
# %á
with pdf output via xelatex.
|
|
|
|
Org reader: "Berkeley style" citation support
|
|
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.
|
|
Semicolons are used as special characters in citations syntax. This
ensures the correct parsing of Pandoc-style citations:
[prefix; @key; suffix]
Previously, parsing would have failed unless there was a space or other
special character as the last <prefix> character.
|
|
|
|
It has no effect, and Hackage wouldn't accept the package.
|
|
We just sign the pkg now.
For some reason we were getting "obsolete resource envelope"
in signing executables. This seems to be documented here
http://stackoverflow.com/questions/25152451/are-mac-app-store-code-sign-resource-envelopes-always-version-1
and seems to be an El Capitan regression. Until a solution
is found, we'll just sign the pkg.
|
|
|
|
* Scope selection in the first screen. Since I couldn't detect if the
user is 'real' admin user, default is still per user.
* Scope is limited to per machine on servers. Though not perfect
(couldn't detect `DisableMSI` policy), it should handle #2389 better.
* For per machine, location can be changed by selecting Advanced.
Localization: modified templates from WiX toolkit support localization
very well. A short sample localization file for en-us is used.
* Dialog elements are moved to their own files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Can't set flag on something not in extra-deps.
|
|
Use released pandoc-citeproc, not git.
|
|
|
|
|
|
|
|
- Create pandoc.msi as artifact.
- Don't install wix unless we need to.
|
|
Updated stackage resolver.
|
|
|
|
|
|
|
|
|
|
Org reader: support more export settings
|
|
Parsing of special strings (like '...' as ellipsis or '--' as en dash)
can be toggled using the `-` option.
|
|
Parsing of emphasized text can be toggled using the `*` option. This
influences parsing of text marked as emphasized, strong, strikeout, and
underline. Parsing of inline math, code, and verbatim text is not
affected by this option.
|