From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Smart Quotes Exporting Date: Thu, 07 Jun 2012 21:21:15 +0200 Message-ID: <87haunexn8.fsf@gmail.com> References: <4FBB08CA.5060705@kli.org> <87d35u8rvk.fsf@gmail.com> <4FBDA56E.5030901@kli.org> <87zk8w6v4q.fsf@gmail.com> <4FC00CE0.6060308@kli.org> <87r4u75tg9.fsf@gmail.com> <4FC426AC.2030109@kli.org> <87ehq227ky.fsf@gmail.com> <4FC56F1B.5040201@kli.org> <87r4u031ye.fsf@gmail.com> <4FC7FE2C.6040702@kli.org> <878vg72bzy.fsf@gmail.com> <4FCEBCF5.1070209@kli.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41154) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SciJm-0007Ff-5i for emacs-orgmode@gnu.org; Thu, 07 Jun 2012 15:24:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SciJk-0003IK-0B for emacs-orgmode@gnu.org; Thu, 07 Jun 2012 15:24:25 -0400 Received: from mail-ee0-f41.google.com ([74.125.83.41]:43186) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SciJj-0003Hx-OF for emacs-orgmode@gnu.org; Thu, 07 Jun 2012 15:24:23 -0400 Received: by eekb47 with SMTP id b47so476041eek.0 for ; Thu, 07 Jun 2012 12:24:20 -0700 (PDT) In-Reply-To: <4FCEBCF5.1070209@kli.org> (Mark E. Shoulson's message of "Tue, 05 Jun 2012 22:14:13 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Mark E. Shoulson" Cc: emacs-orgmode@gnu.org Hello, "Mark E. Shoulson" 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 UTF-8. So it's good to have there too. > should it be in the "publish" exporter? It didn't look like it to > me). No. > Added an options keyword, '"' (that is, the double-quote mark) to > select smart quotes on/off, and a defcustom for customizing your > default. Set the default default [sic] to nil, though actually it > might be reasonable to set it to t. Slight touch-up to the regexps > since last time, but they will definitely be subject to a lot of > fine-tuning as more special cases are found that break them and ways > to fix it are found (the close-quote still breaks on one of "/a/." or > "/a./") Again, using regexps on plain text objects is a wrong approach, as you need a better understanding of the whole paragraph structure to properly. I already suggested a possible solution, is there anything wrong with it? Regards, -- Nicolas Goaziou