From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Introduce ox-i18n.el
Date: Sat, 29 Jun 2013 17:01:41 +0200 [thread overview]
Message-ID: <871u7lezai.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87fvw1ovtm.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 29 Jun 2013 16:06:29 +0200")
Hi Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> I would like to move every variable and function related to
> internationalization (i.e smart quotes and translations) in a dedicated
> file ("ox-i18n.el") instead of "ox.el".
>
> Considering "ox.el" is 6k lines long, I think it can be a bit tedious to
> locate and modify internationalization entries. And since we are missing
> quite a few translations, every little bit can help.
Maybe we can generalize even more, call it org-i18n.el and have
`org-clock-clocktable-language-setup' (and maybe others) included?
If ox-i18n.el exists, it will be confusing to have other i18n
pieces in other part of Org.
If the *only* purpose is to boost translations, I don't think
moving the code the right thing to do: we simply need to give
more pointers on the website on how to help with it.
2 cts,
--
Bastien
next prev parent reply other threads:[~2013-06-29 15:01 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 [this message]
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
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=871u7lezai.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).