Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
Fix RST reference names with special characters
|
|
Normally these will cause an error in LaTeX, but there
are contexts (e.g. `alltt` environments) where they are
okay. Now that we aren't treating them as super/subscript
outside of math mode, it seems okay to parse them as regular
text.
|
|
|
|
Not AppData\Local\Apps\Pandoc as wix was now doing.
It is going to be easier if we don't change the install
directory so that users end up with two versions.
|
|
|
|
|
|
|
|
Taking some values from a user-supplied reference.docx
tends to lead to corruption.
This fixes a regression from the last release. Closes #2249.
|
|
See #2205
|
|
Now they are constructed on the fly from their components,
but we now allow them to be printed with `--print-default-data-file`
and to override the defaults if placed in the user data directory.
Shared now exports getDefaultReferenceDocx and getDefaultReferenceODT
(API change).
These functions have been removed from the Docx and ODT writers.
Shared.readDataFile has been modified so that requests to read
a reference.odt or reference.docx will use these functions to
generate the files.
|
|
* Instead of defining readmeFile in Text.Pandoc.Data (which we forgot
to export anyway), we simply add a record for "README" to the
`dataFiles` lookup table. This allows simplifying some of the code
for `readDefaultDataFile` in SHared.
* As a bonus, `pandoc --print-default-data-file README` now works.
|
|
This change adds `--man1` and `--man5` options to pandoc, so
pandoc can generate its own man pages.
It removes the old overly complex method of building a separate
executable (but not installing it) just to create the man pages.
The man pages are no longer automatically created in the build
process.
The man/ directory has been removed. The man page templates
have been moved to data/.
New unexported module: Text.Pandoc.ManPages.
Text.Pandoc.Data now exports readmeFile, and `readDataFile`
knows how to find README.
Closes #2190.
|
|
Because of the addition of `Options.plainExtensions`.
|
|
In 1b44acf0c59b70cc63f48a23c6f77e45a982aaf9 we replaced some
hackish CSS parsing with css-text, which I thought was a complete
CSS parser. It turns out that it is very buggy, which results
in lots of things being silently dropped from CSS when
`--self-contained` is used (#2224).
This commit replaces the use of css-text with a small but
more principled css preprocessor, which only removes whitespace
and replaces URLs with base 64 data when possible.
Closes #2224.
|
|
This should allow the user to select a per-user or systemwide install.
It also shows install location in the list of installed programs.
Thanks to @nkalvi.
See #2205.
|
|
|
|
Closes #2225.
|
|
Simplified code by using plainExtensions from Options.
Closes #2237.
|
|
These are the extensions used in `plain` output.
|
|
|
|
Thanks to Xavier Olive.
The addition of the `CJKoptions` variable allows one to set (e.g.)
a bigger font size for Asian fonts than latin ones.
Including dvipsnames allows specifying colors like MidnightBlue
for link colors. This brings in a dependency on the color package,
but it is a standard package and required anyway by graphics.
|
|
DocBook reader mediaobjects and figures, closes #2184
|
|
|
|
|
|
|
|
|
|
|
|
|
|
replace old url with pandoc.org
|
|
|
|
They don't have a certificate.
|
|
Closes #1920.
|
|
Fix InDesign crash with URLs containing more than one colon character
|
|
|
|
Colons are valid characters in URLs, and used e.g. by the Internet Archive's Wayback Machine - a popular resource amongst researchers. When InDesign encounters a HyperlinkURLDestination with more than one colon character in it, it crashes when placing the ICML. (This was tested against CS6.) The IDML specification hints at this requirement in section 6.4.1: "The colon apppears in the Name attribute of the style, but is encoded as %3a when it appears in the Self attribute". Follow this example for all colon characters in URLs.
|
|
|
|
Closes #2213.
|
|
|
|
* Allow setting of installation path.
* Use cleaner wix syntax for setting the path:
https://www.firegiant.com/wix/tutorial/com-expression-syntax-miscellanea/environmentally-friendly/
* Show the user what changes, in a new command window.
See #2205.
|
|
|
|
|
|
|
|
|
|
|
|
|