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
better quote handling in markdown reader #99
Comments
The first part resolved by 7864f30 The second part (open quote with no close quote) dropped on closer consideration. It's a bad idea, because the writers will just put the close quote in. Google Code Info: |
I don't know if it's worth considering, but I may have to stop using pandoc on my current work-in-progress because of this bug :( The project is a fiction novel with a lot of dialogue. There are sections where a character must talk for multiple paragraphs. Pandoc's handling of this is currently broken. Here's an example:
Thanks. |
It's not a closed smart quote -- it's a straight quote (not curly at all). If you want to write in this style, you can always directly insert curly quotes. Generally it's pretty easy to program an editor to do this in a way that is easy to type. |
They do not generate a Quoted element; instead, the double quote is just turned into a Str with a curly left quote. This should satisfy the fiction writers. Closes #99 (again).
Support for Asian languages, CJKmainfont label
Currently the markdown reader's quoted parser ignores curly double and single quotes. This is okay for some kinds of output, but not for others. It would be best to produce a Quoted inline consistently, whether or not curly quotes are used.
Also, the parser should be able to handle the American standard of putting an open quote
at the beginning of a paragraph with no close quote, if the same speaker is speaking in the
next paragraph.
Google Code Info:
Issue #: 270
Author: fiddloso...@gmail.com
Created On: 2010-11-21T21:39:35.000Z
Closed On: 2010-12-07T04:38:38.000Z
The text was updated successfully, but these errors were encountered: