From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Introduce ox-i18n.el
Date: Tue, 02 Jul 2013 15:04:56 +0200 [thread overview]
Message-ID: <87txkdi03r.fsf@pank.eu> (raw)
In-Reply-To: 87fvw1ovtm.fsf@gmail.com
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.
So I did some translation work today, and I now support this notion
further. It's super tedious /finding/ all the correct variables, as
they are not spread all over the place.
Should the ox-latex language-code to babel list also be included in an
ox-int'l file? The reason is that I found some "bugs" in this list
and perhaps further language related bugs would be easier to detect if
they were in the same file.
--
Don't panic!!!
next prev parent reply other threads:[~2013-07-02 13:05 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txkdi03r.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.