New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pandoc 2.4 regression: (@) and odt #5076
Comments
Output changed from what version? Isn't the new output better? Maybe this was this change back in 2017: 34b9bee#diff-75ef96f1820e7e194afee0dd28277dd6 ? |
This probably has to do with the following changelog entry:
See #4385 and commit f82d574. |
where 2221 is pandoc 2.2.2.1, 24 is pandoc 2.4. |
Fixed by #5095, I believe. |
just checked with 2.5: as bad as 2.4 -- should the fix the commit be in pandoc 2.5 ? |
But the indentation is a change -- there was no indentation up to 2.3. And neither the pdf/latex output nor docx output has this indentation. And just for the records: the (@) is a "numbered example lists", not a normal numbered list. Ok i could live with the change if there a way to change this via a reference.odt file. Is there such a way? |
It would be easy to remove the outer 0.25" of
indentation so that lists start at the margin.
@pyssling what would you think of that?
|
@AugustH could you be more clear on which of your examples corresponds to which version? My personal view is that ODT should look like a libreoffice document. Could we clarify what exactly the remaining issues are? Is it only that the first list level is indented? This is, I'm quite sure, not configurable via a template or reference. Ideally we would eventually add support for CSS on the ODT writer. The XML tags are very similar to HTML in their semantics, so this should be doable. |
Nils Carlson <notifications@github.com> writes:
This is, I'm quite sure, not configurable via a template or reference. Ideally we would eventually add support for CSS on the ODT writer. The XML tags are very similar to HTML in their semantics, so this should be doable.
This would be great. If you could offer some
examples, perhaps we could move towards this. I
didn't write the opendocument writer, and I've never
liked the way it hardcodes styles for everything,
but I don't know the format, really.
|
@AugustH I see the conundrum. I think the answer to this is that the ODT writer is naive. The I think the 2.5 behavior is preferable to both the 2.3 and 2.4 behavior, it is the closest to the latex behavior. We could do some micro adjustments, but I think that they would make other use-cases uglier. The ODT writer is simply not dynamic in the same way as the latex layout engine. |
Nils Carlson <notifications@github.com> writes:
I think the 2.5 behavior is preferable to both the 2.3 and 2.4 behavior, it is the closest to the latex behavior. We could do some micro adjustments, but I think that they would make other use-cases uglier. The ODT writer is simply not dynamic in the same way as the latex layout engine.
One adjustment I considered was making the distances
bigger (say, 0.3 or 0.35 in instead of 0.25). This
would give better results for (1) but make the space
a little too wide for bullets. With some fancier
coding, one could have different distances for
different sorts of lists, but that does complicate
things a lot. What I'd really like is the ability
to use styles that can be adjusted in the reference.odt.
|
We can increase the width, as noted above, but this will make bullets look worse. |
I would like to see what libreoffice does. I have tried to replicate that behaviour, but if this is what it does then that's not good enough. I'll try to create a libreoffice document today. |
@AugustH I replicated this behaviour in Libreoffice, it behaves the exact same way. I can file a bug on libreoffice and see what they say, my guess is that (10) overflows some buffer where the next tab stop becomes the correct one. |
Yes, I see what you mean. I'm wondering what the correct behaviour should be. I agree this looks good for numbered paragraphs like this, but for a more traditional list of one line or two in point form this would look odd. This may simply be a different use-case than the traditional list. |
I suppose we could make the indent dependent on whether the list marker is >9 (for ordered lists). Not sure how easy that is to implement... |
The code is currently all under the assumption that
you can figure out indent levels by calculating
the degree of nesting. This assumes constant indent
for each type of list. We'd have to complicate things
to have different indents for different lists.
Mauro Bieg <notifications@github.com> writes:
… I suppose we could make the indent dependent on whether the list marker is >9 (for ordered lists). Not sure how easy that is to implement...
|
I fixed it for me by replacing the Idea: i looked at the code: the offset is set in |
Sample:
compile with:
pandoc -f markdown test.md -o test.odt
output changed with pandoc 2.4 (on linux mint, libreoffice 6.0.6): the numbered paragraph is indented
The text was updated successfully, but these errors were encountered: