From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [RFC] Introduce ox-i18n.el Date: Sat, 29 Jun 2013 17:01:41 +0200 Message-ID: <871u7lezai.fsf@bzg.ath.cx> References: <87fvw1ovtm.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45538) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uswel-0006Pa-Cu for emacs-orgmode@gnu.org; Sat, 29 Jun 2013 11:01:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uswej-0001PP-CS for emacs-orgmode@gnu.org; Sat, 29 Jun 2013 11:01:43 -0400 Received: from mail-wi0-x235.google.com ([2a00:1450:400c:c05::235]:58481) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uswej-0001P6-6v for emacs-orgmode@gnu.org; Sat, 29 Jun 2013 11:01:41 -0400 Received: by mail-wi0-f181.google.com with SMTP id hq4so1743519wib.8 for ; Sat, 29 Jun 2013 08:01:40 -0700 (PDT) In-Reply-To: <87fvw1ovtm.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 29 Jun 2013 16:06:29 +0200") 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: Nicolas Goaziou Cc: Org Mode List Hi Nicolas, Nicolas Goaziou 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