khajavi / pandoc Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/pandoc
License: GNU General Public License v2.0
Automatically exported from code.google.com/p/pandoc
License: GNU General Public License v2.0
What steps will reproduce the problem?
What is the expected output? What do you see instead?
Create an HTML document with an A tag like <a href="http://foo">bar</a>.
pandoc chooses to encode this as
[bar][1]
[1]: http://foo
which is legitimate referenced-link markdown, but to my tasted is far
inferior to the inline markdown
[bar](http://foo)
What version of the product are you using? On what operating system?
pandoc 0.3 Debian
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 25 Jan 2007 at 7:39
According to the RST documentation
(http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#hyperlink-ta
rgets),
the following external hyperlink targets are equivalent:
.. _one-liner: http://docutils.sourceforge.net/rst.html
.. _starts-on-this-line: http://
docutils.sourceforge.net/rst.html
.. _entirely-below:
http://docutils.
sourceforge.net/rst.html
Pandoc does not currently handle this correctly. It assumes that the
entire URI is on one line.
Original issue reported on code.google.com by [email protected]
on 12 Feb 2007 at 2:45
I've added support for strikeout text. The included patch applies against
your current trunk (r714 at time of submission). The only input/output
format that didn't support strikeout was reStructured text, so I added a
dummy output for it. For the rest, I added the standard methods for the
given format.
Original issue reported on code.google.com by [email protected]
on 15 Jul 2007 at 4:28
Attachments:
Allow tables to have no column heading.
E.g.
------------ ---
California 42
New Mexico 5
------------ ---
How do we determine the alignment in these cases?
Possibly from the first line. Or possibly we could
introduce a special notation:
. .
------------ ---
California 42
New Mexico 5
------------ ---
Original issue reported on code.google.com by [email protected]
on 22 Jan 2008 at 3:40
Backslash escapes don't work in link URLs.
Run pandoc on:
[test](/url\(test\))
Output:
<p
><a href="/url\(test\"
>test</a
>)</p
>
Expected output: the final ) should be part of the URL, and the
backslashes should not be part of it.
Original issue reported on code.google.com by [email protected]
on 16 Dec 2007 at 7:20
Hi,
RST code blocks are indented blocks of text following a paragraph ending
with two colons::
like this
Alternatively, you can even do this!
::
This is code.
I hope Google preserves the spacing.
When pandoc converts this to Markdown, it creates indented text:
> like
> this
and it does not preserve line breaks or spaces.
Instead, it should really convert indented blocks following a :: to blocks
indented by four spaces or a tab, which is what Markdown uses.
Thanks for your attention.
Original issue reported on code.google.com by [email protected]
on 10 Oct 2007 at 9:39
What steps will reproduce the problem?
Convert the following snippet as Pandoc-enhanced Markdown:
Lorem <lj user="ipsum" /> dolor sic
What is the expected output? What do you see instead?
Markdown.pl produces:
<p>Lorem <lj user="ipsum" /> dolor sic</p>
Strict Markdown produces:
<p>Lorem <lj user="ipsum" /> dolor sic</p>
Pandoc enhanced produces:
Lorem <lj user="ipsum" />
<p>dolor sic</p>
What version of the product are you using? On what operating system?
PanDoc 0.3 w/ GHC 6.6 and Ubuntu 7.04 (Feisty).
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 16 Aug 2007 at 3:01
Currently, we're required to use 4 spaces for indenting bulleted lists.
Ideally pandoc should allow an arbitrary amount of indentation.
- this
- should
- work
- but
- right now
- it doesn't
Original issue reported on code.google.com by [email protected]
on 23 Mar 2007 at 6:36
Pandoc does not properly handle autolink email addresses with periods
in them:
<[email protected]>
does not get converted into an email link.
Original issue reported on code.google.com by [email protected]
on 16 Dec 2007 at 7:27
[http://www.mit.edu/~y_z/](http://www.mit.edu/~y_z/)
I think that generally, brackets/parens should get precedence over tilde,
especially since tildes are commonly used in URLs.
BTW, is there any way to create the above type of link without the
repetition? Thanks!
Original issue reported on code.google.com by [email protected]
on 20 Jan 2008 at 8:26
This is a feature request.
Would you consider adding some syntax for comments? Perhaps something
along the lines of:
[Comment: To render this text file document into HTML, use pandoc 0.3 or
greater, available at http://....]
Thanks!
Original issue reported on code.google.com by [email protected]
on 26 Jul 2007 at 5:42
This is an enhancement request.
I have recently been using ditaa for generating diagrams. It would be
incredibly awesome if pandoc supported in-line generation of these
diagrams!
I'm surprised something like this hasn't been done before with (e.g.)
Markdown. I'm not sure what other ASCII art renderers exist - I tried
looking for a while but didn't find anything - but if you know of
others, then perhaps consider those too!
Original issue reported on code.google.com by [email protected]
on 2 Jun 2007 at 9:54
The link to the Pandoc 0.3 Debian package in Pandoc's home page is broken.
Instead, there is a Pandoc 0.4 package on Recai Oktaş repository:
http://people.debian.org/~roktas/packages/pandoc_0.4_i386.deb
This pandoc_0.4_i386.deb produces html with greater-than signs (>) at the
beginning of each line. See attached file.
To reproduce the issue:
1. environment is Debian testing
2. sudo dpkg -i pandoc_0.4_i386.deb
3. pandoc README -o example1.html
The output html file has an > for every new line. Same for standalone output.
Removing 0.4 and installing 0.3 fixes the issue. There is an 0.3 package here:
http://people.debian.org/~roktas/tmp/pandoc-old/pandoc_0.3_i386.deb
Original issue reported on code.google.com by [email protected]
on 4 May 2007 at 8:52
Attachments:
Jonathan Deber notes on the Markdown list: "If you're posting to a CMS
system where multiple articles may appear on the same HTML page, you need
to assign each article a GUID so that the footnote links make sense (i.e.,
you can't have two articles that both use "fnref" as the anchor name for
the footnotes, since you would end up with two anchors with the same name
if two articles are published on the same page). It's of course possible to
do this with a search and replace of "fnref" to something like
"2007-01-23-1" prior to publishing. But, it would be nice if you could
specify a document GUID and have the Markdown processor do that
substitution for you."
Perhaps a command-line option should be provided to specify a string to be
added to the anchor names?
Original issue reported on code.google.com by [email protected]
on 4 Jan 2008 at 8:14
input:
A long line with enough text to break the following line.<br />
This is the following line.
output:
A long line with enough text to break the following line.
This is
the following line.
Original issue reported on code.google.com by [email protected]
on 25 Sep 2007 at 4:26
What steps will reproduce the problem?
pandoc
A.B.
^D
What is the expected output?
<p
>A.B.</p
>
What do you see instead?
pandoc:
Error:
"source" (line 7, column 3):
unexpected "B"
This is due to the fact that anyOrderedListStart doesn't require a
space after the marker.
Original issue reported on code.google.com by [email protected]
on 18 Aug 2007 at 3:14
Pandoc allows links to occur nested in links, which is not valid HTML:
So, running pandoc on
[[Link](url)](url)
yields
<p
><a href="url"
><a href="url"
>Link</a
></a
></p
>
Original issue reported on code.google.com by [email protected]
on 16 Dec 2007 at 7:22
Thanks for quick fix for last report!
This is a minor issue when input strings end with a single
newline character, adding a further newline character
works as a fix.
I'd half expect no newline character to still catch the final
paragraph as well, I'm not sure.
Thanks again,
Rohan
What steps will reproduce the problem?
test.hs
>>>
import Text.Pandoc.Readers.Markdown ( readMarkdown )
import Text.Pandoc.Writers.HTML ( writeHtmlString )
import Text.Pandoc.Definition
import Text.Pandoc.Shared
prs = defaultParserState { stateParseRaw = False
, stateTabStop = 4
, stateStandalone = False
, stateSmart = False
, stateColumns = 1
, stateStrict = True
, stateInlineLinks = False }
opt = WriterOptions { writerStandalone = False
, writerTitlePrefix = ""
, writerHeader = ""
, writerIncludeBefore = ""
, writerIncludeAfter = ""
, writerS5 = False
, writerIncremental = False
, writerNumberSections = False
, writerStrictMarkdown = True
, writerTabStop = 4
, writerNotes = [] }
main = do let s = "this is a paragraph\n\nand this is another\n"
d = readMarkdown prs s
putStrLn (writeHtmlString opt d)
<<<
What is the expected output? What do you see instead?
expect:
<p
>this is a paragraph</p
><p
>and this is another</p
>
receive:
<p
>this is a paragraph</p
>and this is another
What version of the product are you using? On what operating system?
Current svn (as of 12/3/07)
$ pandoc --version
pandoc 0.4
Copyright (C) 2006 John MacFarlane
Web: http://sophos.berkeley.edu/macfarlane/pandoc
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.
$ uname --all
Linux alice.localdomain 2.6.20-rt8 #1 PREEMPT Thu Mar 8 23:01:25 EST 2007
i686 i686 i386 GNU/Linux
$
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 12 Mar 2007 at 10:36
What steps will reproduce the problem?
1. install ghc in, say "/opt/ghc/bin"
2. extract pandoc tarball
3. cd into pandoc dir
4. type make
5. behold the error
6. change GDC* variables in Makefile to full path of binaries
7. try again
8. see the error
9. sigh.
10. make symlinks of all files in /opt/ghc/bin to /usr/local/bin/
11. try again
12. works.
13. there is no step 13.
What is the expected output? What do you see instead?
Eh... works now. Forgot *what* I saw exactly.
What version of the product are you using? On what operating system?
pandoc 0.44
Original issue reported on code.google.com by [email protected]
on 17 Nov 2007 at 2:11
What steps will reproduce the problem?
1. Install GHC (OSX 10.4.8, intel), Audrey Tang version of GHC binary.
2. run Make on pandoc
3.
What is the expected output? What do you see instead?
error message:
Main.hs:21:7:
Could not find module `Distribution.GetOpt':
it is hidden (in package Cabal-1.1.6.1)
make[1]: *** [../pandoc] Error 1
make: *** [all] Error 2
What version of the product are you using? On what operating system?
OSX 10.4.8. Intel, Pandoc-0.2, GHC 6.6, Cabal 1.1.6.1a
Please provide any additional information below.
Being newbie to Haskel, GHC, etc., I also reinstalled Cabal independently
of GHC after getting the error message. Cabal installation was successfull,
but error message persists. Any obvious issues?
Original issue reported on code.google.com by [email protected]
on 4 Nov 2006 at 3:28
What steps will reproduce the problem?
1. markdown -f rst -t mdwn attached_file.rst
What is the expected output? What do you see instead?
markdown output, but it seems to loop forever.
What version of the product are you using? On what operating system?
pandoc 0.45 / debian sid
Original issue reported on code.google.com by [email protected]
on 6 Jan 2008 at 12:57
Attachments:
Run pandoc on
<ins>hello</ins>
You get:
<ins><p
>hello</ins></p
>
which is improperly nested.
Optimal output:
<p><ins>hello</ins></p>
Perhaps this can be fixed by putting the raw HTML parser after
the paragraph parser in the definition of 'block'.
Original issue reported on code.google.com by [email protected]
on 16 Dec 2007 at 7:26
I think Pandoc should treat definition lists as PHP Markdown Extra does.[^1] In
accordance with the
HTML specification, it supports consecutive terms (several terms may share a
common definition)
and consecutive definitions (terms may have more than one definition). It also
seems useful to
remain compatible with the existing syntax specified by PHP Markdown Extra.
Such changes may be incompatible with Latex and other formats but the
deficiencies of a given
format should not impair the utility of another.
[^1]: http://michelf.com/projects/php-markdown/extra/#def-list
Original issue reported on code.google.com by [email protected]
on 24 Sep 2007 at 10:29
Latex output doesn't usepackage amsmath. It would be nice to have that
included by default, though perhaps you intentionally excluded it because
you felt it wasn't safe to assume people had that package. Perhaps some
simple heuristics for implicitly detecting amsmath commands could be added.
Original issue reported on code.google.com by [email protected]
on 19 Jan 2008 at 6:39
1. Create a markdown document with very long link text (not the uri - the
description) or with a long file path
http://localhost/workingdir/trunk/src/project/trunk/WebContent/
~/Documents/Work/Project/SVN/workingdir/trunk/src/project/trunk/WebContent/
2. Generate PDF using markdown2pdf or pandoc to tex to pdf
Would expect to see a PDF where the hyperlinks are wrapped or at least
forced to their own line. This is not the case.
0.46 on OS X 10.5.1 (Leopard)
When coupled with the extremely large margins of PDF out this exacerbates
the problem.
Original issue reported on code.google.com by [email protected]
on 19 Jan 2008 at 1:28
steps to reproduce the problem
1. debian sid, pandoc 0.44,
2. get a markdown file such as http://johnmacfarlane.net/pandoc/README
3. pandoc -S README.txt -o README.html
4. less README.html
HTML linebreaks happen before the closing > tag, newlines beginning with
the same > tag.
Debian sid
pandoc 0.44
libghc6-pandoc-dev 0.44
Original issue reported on code.google.com by [email protected]
on 17 Oct 2007 at 2:28
Attachments:
In some cases it is preferable to obtain output which is not hard wrapped.
Perhaps this option could
be called: no-wrap.
Original issue reported on code.google.com by [email protected]
on 25 Sep 2007 at 4:33
1. use markdown2pdf to generate a pdf
2. use pandoc to generate a tex (pandoc -w context) and texexec to convert
to pdf
You get a PDF as expected but the margins are very large. Using
markdown2pdf I see no way to effectively manipulate margins. Using padoc
to generate an intermediary tex allows you to modify the tex before using
texexec to convert.
On 0.46 - OS X 10.5.1 (Leopard)
Original issue reported on code.google.com by [email protected]
on 19 Jan 2008 at 1:20
It would be fantastic if it supported at least a subset of AsciiDoc. (I
personally prefer AsciiDoc's section headers over Markdown's, where the
former underlines the title with = or -.)
Original issue reported on code.google.com by [email protected]
on 12 Feb 2007 at 2:39
What steps will reproduce the problem?
1. Make a file containing the following:
<br>
foo
bar
2. Run pandoc --no-wrap --from=markdown on it.
What is the expected output? What do you see instead?
I expected something like:
<br>
<pre><code>foo
bar
</code></pre>
But I got:
<br>
<p>foo bar</p>
I was originally seeing if literate Haskell would work by doing the following:
<pre><code>
> foo
> bar
</code></pre>
Which gives (note the incorrect tag nesting):
<pre><code><blockquote>foo bar </code></pre>
</blockquote>
What version of the product are you using? On what operating system?
SVN revision 1161 on Windows XP, compiled with the help of Cygwin and GHC
6.8.2.
Original issue reported on code.google.com by [email protected]
on 30 Dec 2007 at 12:35
What steps will reproduce the problem?
1. Make a file with the following contents:
<style type="text/css">
body {}
</style>
2. Run pandoc --from=markdown on it.
What is the expected output? What do you see instead?
Expected is something like:
<style type="text/css">body {}</style>
Seen is:
<style type="text/css"><p
>body {}</p
></style>
I.e. a <p> tag is wrapped around the contents, because of the blank line
before the closing </style> tag.
Another, worse case is:
<style type="text/css">
/*
* a CSS comment
*
*/
</style>
Which becomes a mess which isn't even valid HTML, let alone CSS:
<style type="text/css"><p
>/*</p
><ul
><li
>a CSS comment * */</style>
</li
></ul
>
What version of the product are you using? On what operating system?
SVN revision 1161 on Windows XP, compiled with the help of Cygwin and GHC
6.8.2.
Please provide any additional information below.
This isn't as bad as it seems, since it's easy to work around: don't put
any blank lines in <style>. Still, it's annoying.
Original issue reported on code.google.com by [email protected]
on 30 Dec 2007 at 1:12
What steps will reproduce the problem?
1. Create a document that contains this line only: "# 1 Test"
2. Run "pandoc -st html test.txt > test.html".
What is the expected output? What do you see instead?
The output should contain a valid ID for the HTML h1 tag. However, the
identifier is "1-test", which is not a valid identifier because identifiers
may not begin with a number (see
http://htmlhelp.com/reference/html40/attrs.html).
Running this through HTML Tidy will result in the following warning: 'line
10 column 4 - Warning: <h1> attribute "id" has invalid value "1-test"'.
What version of the product are you using? On what operating system?
I'm using revision 1145 checked out from the SVN repository on Windows
under Cygwin.
Original issue reported on code.google.com by [email protected]
on 10 Dec 2007 at 3:21
RST allows "internal" hyperlink targets that refer to the next element.
They can also be "chained." Pandoc's parser doesn't handle either case
correctly. See
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#hyperlink-tar
gets
What steps will reproduce the problem?
1. Run pandoc on the following input:
`hello`_
.. _hello:
paragraph
Expected output: "hello" should link to the paragraph "paragraph", which
should get id="hello".
2. Run pandoc on the following input:
`hello`_ and `goodbye`_
.. _hello:
.. _goodbye: foo.bar.com
Expected output: Both "hello" and "goodbye" should be links to foo.bar.com.
Original issue reported on code.google.com by [email protected]
on 12 Feb 2007 at 2:43
Currently pandoc's markdown tables are difficult to use with
proportionally spaced fonts, because they require lining up columns.
It might be worth adding an additional table syntax similar to that
used by PHP Markdown Extra:
| Item | Value |
| --------- | -----:|
| Computer | $1600 |
| Phone | $12 |
| Pipe | $1 |
Here the columns would not have to line up. A multiline variant could
also be added:
---------------------
| Item | Value |
| --------- | -----:|
| Computer | $1600 |
| | |
| Phone | $12 |
| jack | |
| | |
| Pipe | $1 |
---------------------
Original issue reported on code.google.com by [email protected]
on 4 Jan 2008 at 8:19
What steps will reproduce the problem?
1. make test
2. head -n 5 tests/writer.html
What is the expected output?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Pandoc Test Suite</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
What do you see instead?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
><head
><title
>Pandoc Test Suite</title
What version of the product are you using? On what operating system?
pandoc 0.44, Linux 2.6.20-suspend2-r6 #3 PREEMPT
Please provide any additional information below.
compiled with "The Glorious Glasgow Haskell Compilation System, version 6.6.1"
Original issue reported on code.google.com by [email protected]
on 17 Nov 2007 at 2:22
There is currently no way to specify the size of an image.
For some ideas, see http://code.google.com/p/pandoc/wiki/ImageSizes.
Original issue reported on code.google.com by [email protected]
on 1 Nov 2007 at 5:05
What steps will reproduce the problem?
1. Run pandoc on <a href="">foo bar</a>
What is the expected output? What do you see instead?
Expected that the HTML entity would be preserved; instead, it is
translated as a Unicode non-breaking space. Uggh.
What version of the product are you using? On what operating system?
pandoc 0.3 Debian
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 25 Jan 2007 at 7:31
Validation fails because:
- missing xmlns element (note: this can be fixed by compiling pandoc
with the newest xhtml library in GHC 6.6.1)
- when --toc option is used, headers are wrapped in anchors, and this
is invalid (block-level content inside inline-level tags).
Original issue reported on code.google.com by [email protected]
on 2 Sep 2007 at 4:50
I'd like to see an official release that works on GHC 6.6, since previous
versions of GHC don't work
on OS X i386 (but MacPorts has a build process for 6.6 that works). I could use
the subversion
repository, but I personally don't need pandoc, instead I want to enable others
to use it, and it
would be a lot easier if there was an official release that I could make a
MacPorts Portfile for.
Original issue reported on code.google.com by [email protected]
on 5 Dec 2006 at 2:57
What steps will reproduce the problem?
Run pandoc -r rst on the following input:
``#``
Indented code block
Indented code block
Expected output: an inline literal # followed by two h1 headings.
The problem: Pandoc will get this right, but it takes forever. This
happens even with r526, which fixed a few bugs in RST parsing. Note
that the inline literal by itself, or the headings by themselves,
are parsed quickly.
This bug is responsible for pandoc's hanging while trying to parse the RST
markup specification:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.txt
Original issue reported on code.google.com by [email protected]
on 12 Feb 2007 at 3:59
Hello John,
Pandoc is excellent, thanks very kindly!
A minor issue: the mail address mangling is nice however
under --strict it the encoding for the visible text is
not correct.
What steps will reproduce the problem?
test.md
>>>
contact [us][1] for details
[1]: mailto:[email protected]
<<<
$ pandoc --strict test.md > test.html
What is the expected output? What do you see instead?
expected: contact us for details
received: contact us for details
What version of the product are you using? On what operating system?
~$ pandoc --version
pandoc 0.4
Copyright (C) 2006 John MacFarlane
Web: http://sophos.berkeley.edu/macfarlane/pandoc
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.
~$ uname --all
Linux alice.localdomain 2.6.20-rt8 #1 PREEMPT Thu Mar 8 23:01:25 EST 2007
i686 i686 i386 GNU/Linux
~$
Original issue reported on code.google.com by [email protected]
on 10 Mar 2007 at 10:26
What steps will reproduce the problem?
Run pandoc on the following input:
test^[my [note] contains brackets].
What is the expected output? What do you see instead?
Expected a footnote with the content: "my [note] contains brackets".
Instead, the note is cut off at the first closing bracket: "my [note",
and the rest appears in the main text.
Original issue reported on code.google.com by [email protected]
on 26 Mar 2007 at 8:41
These tables could include arbitrary lists of blocks in each cell.
+------------------------+------------+----------+----------+
| Header row, column 1 | Header 2 | Header 3 | Header 4 |
+------------------------+------------+----------+----------+
| body row 1, column 1 | column 2 | column 3 | column 4 |
| and more col 1 | | | and more |
| and more | and more | and more | col4 |
+------------------------+------------+----------+----------+
| body row 2 | Cells may span column | |
+------------------------+------------+----------+----------+
Look at reStructuredText's table syntax as a paradigm.
Original issue reported on code.google.com by [email protected]
on 4 Jan 2008 at 8:21
What steps will reproduce the problem?
1. echo "<html><body>Foo bar.</body></html>" | pandoc --no-wrap
What is the expected output? What do you see instead?
Pandoc escapes the closing html and body tags, resulting in:
<html><body><p>Foo bar.</body></html></p>
What I hoped to see was:
<html><body><p>Foo bar.</p></body></html>
What version of the product are you using? On what operating system?
Pandoc 0.45, the Windows binary package on Windows XP.
Original issue reported on code.google.com by [email protected]
on 22 Dec 2007 at 6:59
This is a feature request and not a bug report :) Would it be possible to
support internal cross references, perhaps in the manner of
http://fletcherpenney.net/MultiMarkdown_Syntax_Guide#automaticcross-references
Original issue reported on code.google.com by [email protected]
on 16 Aug 2007 at 1:28
It would be great to have some way to output 'display' (multiline, aligned,
etc., not in-line) math equations for HTML (any of the math-in-HTML options).
Thanks!
Original issue reported on code.google.com by [email protected]
on 19 Jan 2008 at 5:58
Hi, I love this program! Please consider adding support (perhaps for a
subset of input formats) for generating man pages. (This is featured in
AsciiDoc.)
Original issue reported on code.google.com by [email protected]
on 22 Mar 2007 at 6:32
To see the bug:
1. Create a link with text containing a character entity, `[Foo
&c.](mailto:[email protected])`; and
2. Translate the document to HTML.
With JavaScript enabled one sees the expected link "Foo &c.".
With JS disabled the one sees the incorrect text "Foo &c. (foo at bar dot
baz)".
Encountered using the OS X package of pandoc 0.3. Tested with Camino 1.0.3 and
eLinks 0.10.6.
The attached pandoc-0.3-obfuscateString.patch resolves the issue, and doesn't
introduce any
regressions w.r.t. the test suite.
Original issue reported on code.google.com by [email protected]
on 8 Apr 2007 at 10:07
Attachments:
We've had a number of good suggestions for improving ConTeXt output.
See http://code.google.com/p/pandoc/wiki/ConTeXtImprovements
Original issue reported on code.google.com by [email protected]
on 1 Nov 2007 at 5:07
There are a number of differences from the original Markdown syntax which
pandoc offers. These should be documented!
Original issue reported on code.google.com by [email protected]
on 22 Mar 2007 at 8:46
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.