Closed GoogleCodeExporter closed 9 years ago
I believe the problems have been fixed in the latest development version on
github.
703c421c9e8684bb20aa091223ca5e532b6bb867
(Note: in order to install this, you must first install pandoc-types from the
github repo,
and then reinstall citeproc-hs after tweaking its build-depends to allow
pandoc-types 1.8.
So you may just want to wait to test this further.)
I'll mark this fixed, but if you still encounter problems, reply here.
Original comment by fiddloso...@gmail.com
on 27 Jan 2011 at 1:53
I'm sorry for the late reply. Largely it is now working, but not completely -
this may be because of a misunderstanding of mine.
In the case where we have
:field1: variable
if field1 has a space in it, like so:
:field 1: variable
there still seems to be an issue. I've not looked deeply into the problem, but
I noticed that the fields that were not rendering correctly all had spaces,
while all others (including those that previously were not rendering correctly)
were rendering correctly.
Presuming that this is a regex issue, I considered that this initial diagnosis
was enough. Shout out if you need any more.
Original comment by data...@gmail.com
on 3 Feb 2011 at 12:47
Can you supply an actual test case that fails? Field names with spaces seem to
work for me (see below). Are you sure you're using pandoc 1.8 now?
% pandoc -f rst -t native
:field1: variable
:field 1: variable
[DefinitionList
[([Str "field1"],
[[Para [Str "variable"]]])
,([Str "field 1"],
[[Para [Str "variable"]]])]]
Original comment by fiddloso...@gmail.com
on 3 Feb 2011 at 3:46
You are right, my bad. Somehow I ended up with /usr/lib/pandoc (1.6) as well as
~/.cabal/bin/pandoc (1.8.0.1).
I removed the old stuff, all good now - thanks
Original comment by data...@gmail.com
on 3 Feb 2011 at 11:57
Original issue reported on code.google.com by
data...@gmail.com
on 27 Jan 2011 at 1:45