From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Introduce ox-i18n.el
Date: Tue, 02 Jul 2013 18:21:53 +0200 [thread overview]
Message-ID: <87ip0thqzi.fsf@pank.eu> (raw)
In-Reply-To: 871u7hq8cj.fsf@gmail.com
Hello,
>>> +(defconst org-export-dictionary
>> ^^^^^^^^
>> ^^^^^^^^
>>
>> Why?
>
> Because it is not meant to be changed by the user nor let-bound. IOW,
> it's a constant.
But perhaps it should not be. Consider org-export-smart-quotes-alist.
In Danish, according to the 'official' guidance, all of the following
are appropriate
(*) ,,.'', ``.'', `.', >>.<<, >.<.
Basically, only the french <<.>> is not appropriate. A similar
situation exists in Norwegian, to the best of my knowledge. Why
should I (submitting a patch) be able to actively force which of forms
in (*) should be used?
One remedy /in LaTeX/ would be to let quote-characters be selected by
csquote, but I don't really know if I'd want to go that way. . .
Alternatively, we can populate the various language variables and
provide easy means to alter them, a la:
(org-alter-language "da" :left-latex "``" :right-latex "''" :table "tabel").
–Rasmus
--
⠠⠵
next prev parent reply other threads:[~2013-07-02 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 14:06 [RFC] Introduce ox-i18n.el Nicolas Goaziou
2013-06-29 15:01 ` Bastien
2013-06-29 15:22 ` Rasmus
2013-07-01 10:13 ` Sebastien Vauban
2013-07-01 10:19 ` Bastien
2013-07-02 6:37 ` Jambunathan K
2013-07-02 15:39 ` Nicolas Goaziou
2013-07-02 16:21 ` Rasmus [this message]
2013-07-02 16:29 ` Nicolas Goaziou
2013-07-02 17:10 ` Jambunathan K
2013-07-02 17:26 ` Nicolas Goaziou
2013-07-02 17:40 ` Jambunathan K
2013-07-02 17:43 ` Rasmus
2013-07-02 18:12 ` Jambunathan K
2013-07-02 16:40 ` Jambunathan K
2013-07-02 13:04 ` Rasmus
2013-07-02 16:30 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip0thqzi.fsf@pank.eu \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).