Thanks!
I prepared a patch as you've suggested (attached).
On Thu, Nov 14, 2013 at 3:15 AM, Rasmus ras...@gmx.us wrote:
Hi Daniil,
Daniil Frumin difru...@gmail.com writes:
Hi! I am using the latest org from git and I can't get org to export (I
need LaTeX export particularly) files
Caio Daniil,
Daniil Frumin difru...@gmail.com writes:
I prepared a patch as you've suggested (attached).
Are the unicode entities correct? In my UTF8-Emacs they look like,
e.g, \302\253. It could be OK, though and I could just be missing a
font that has these glyphs.
Also, please change the
Hi! I am using the latest org from git and I can't get org to export (I
need LaTeX export particularly) files with smart quotes.
The following example silently fails to produce smart quotes:
#+OPTIONS: ':t
#+LANGUAGE: ru
This is a 'test' file.
* Headline with 'quotes'
** Subheading with quotes.
Hi Daniil,
Daniil Frumin difru...@gmail.com writes:
Hi! I am using the latest org from git and I can't get org to export (I
need LaTeX export particularly) files with smart quotes.
You need to add it to the variable org-export-smart-quotes-alist
defined in ox.el. Put your cursor on the
Hi Mark and Nicolas,
in the patchwork¹, I've marked patches² related to this discussion as
Not Applicable.
If there are progress made on this front, please send updated patches.
If there is a patch below that I should apply, please let me know.
Thanks!
¹
Hello,
Mark Shoulson m...@kli.org writes:
Well, wait; regexps can make some pretty darn good guesses at the beginnings
or ends of strings.
I know that. They make a good job, I just want a better one.
This isn't quite it; beginning-of-string followed by quote, then punctuation
and then
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Mark Shoulson mark at kli.org writes:
ASCII exporter also handle UTF-8. So it's good to have there too.
Really? I would have thought ASCII meant ASCII, as in 7-bit clean
text.
org-e-ascii.el (as old org-ascii.el) handles
Hello,
Mark Shoulson m...@kli.org writes:
ASCII exporter also handle UTF-8. So it's good to have there too.
Really? I would have thought ASCII meant ASCII, as in 7-bit clean
text.
org-e-ascii.el (as old org-ascii.el) handles ASCII, Latin1 and UTF-8
encodings.
It looked to me like your
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Mark E. Shoulson mark at kli.org writes:
Update on the smart-quotes patch. Supports the odt exporter now too,
which I think covers all the current major new exporters for which
it is relevant (adding smart quotes to ASCII export
Hello,
Mark E. Shoulson m...@kli.org writes:
Update on the smart-quotes patch. Supports the odt exporter now too,
which I think covers all the current major new exporters for which
it is relevant (adding smart quotes to ASCII export is a contradiction
in terms;
ASCII exporter also handle
Update on the smart-quotes patch. Supports the odt exporter now too,
which I think covers all the current major new exporters for which it
is relevant (adding smart quotes to ASCII export is a contradiction in
terms; should it be in the publish exporter? It didn't look like it
to me).
All right, preliminary patch is attached, *maybe* good enough for more
serious consideration now, but might need some fixes. Still only uses
ordinary regexps and plain-text strings, but can now handle the example
with formatting-breaks next to quotes. Things have been moved into more
Hello,
Mark E. Shoulson m...@kli.org writes:
Oh, certainly; they're all a disaster. I think I said that in the
writeup at the top. This is just proof of concept, nothing is in the
right place, nothing is properly documented. They have to be
defcustoms, there needs to be a good :type in
On 06/01/2012 01:11 PM, Nicolas Goaziou wrote:
Hello,
Mark E. Shoulsonm...@kli.org writes:
Oh, certainly; they're all a disaster. I think I said that in the
writeup at the top. This is just proof of concept, nothing is in the
right place, nothing is properly documented. They have to be
Sorry for messing up the thread subject header; I think I misused
gmane's posting.
On 05/31/2012 09:38 AM, Nicolas Goaziou wrote:
Hello,
Mark Shoulsonm...@kli.org writes:
+(defvar org-e-html-quote-replacements
+ '((fr « » ‘ ’ ’)
+(en “ ” ‘ ’ ’)
+(de „ “ ‚ ‘ ’))
A docstring will
Hello,
Mark E. Shoulson m...@kli.org writes:
Maybe, if it's all on one line. But if the quote is several lines
long, can you sensibly count the levels?
Well, yes.
I guess it doesn't actually matter, but it starts to get weird if you
find yourself looking arbitrarily far back, and then you
On 05/29/2012 01:57 PM, Nicolas Goaziou wrote:
Hello,
Mark E. Shoulsonm...@kli.org writes:
I guess it doesn't actually matter, but it starts to get weird if you
find yourself looking arbitrarily far back, and then you start
building in exceptions for crossing paragraph boundaries...
True.
On 05/26/2012 02:48 AM, Nicolas Goaziou wrote:
Hello,
Mark E. Shoulsonm...@kli.org writes:
The regexp may be able to tell level 1 from level 2 quotes.
Do you mean that the author would use the same characters for both
first and second level quotes, and the regexp would be smart enough to
Hello,
Mark E. Shoulson m...@kli.org writes:
The regexp may be able to tell level 1 from level 2 quotes.
Do you mean that the author would use the same characters for both
first and second level quotes, and the regexp would be smart enough to
distinguish which level each was at? I don't
Hello,
Mark E. Shoulson m...@kli.org writes:
Hm. I like the idea, but it raises some questions for me. It would
be particularly good if this could share code/custom variables with
the pieces of the (new) exporter that make smart quotes on export.
That way we could be sure that what it
I could be interesting, but keep in mind that no matter how smart your
quotes are, they will fail in some situations. So, it will have to be
optional for export, independently on their in-buffer status.
The OPTIONS keyword may be used, with q:t and q:nil items.
I don't see an entry for this
On 05/25/2012 01:14 PM, Nicolas Goaziou wrote:
Hello,
Mark E. Shoulsonm...@kli.org writes:
Hm. I like the idea, but it raises some questions for me. It would
be particularly good if this could share code/custom variables with
the pieces of the (new) exporter that make smart quotes on
Hello,
Mark E. Shoulson m...@kli.org writes:
Smart quotes can be annoying when they aren't smart enough. But when
they work you can miss them. I'm attaching a patch that defines a
custom variable org-smart-quotes (nil by default), which when non-nil
causes the and ' characters to display
On 05/23/2012 06:17 PM, Nicolas Goaziou wrote:
Hello,
Mark E. Shoulsonm...@kli.org writes:
Smart quotes can be annoying when they aren't smart enough. But when
they work you can miss them. I'm attaching a patch that defines a
custom variable org-smart-quotes (nil by default), which when
(I seem to be winding up fixating on non-asciisms for org-mode;
strange)
"Smart" quotes can be annoying when they aren't smart enough.
But when they work you can miss them. I'm attaching a patch that
defines a custom variable org-smart-quotes (nil by default),
25 matches
Mail list logo
