From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Advice on handling translations in export Date: Sun, 22 Feb 2015 21:05:15 +0800 Message-ID: <14bb1644af8.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com> References: <14bb1576a18.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40325) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YPWEO-0007yo-NJ for emacs-orgmode@gnu.org; Sun, 22 Feb 2015 08:05:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YPWEK-0000mE-Jk for emacs-orgmode@gnu.org; Sun, 22 Feb 2015 08:05:56 -0500 Received: from smtpbguseast2.qq.com ([54.204.34.130]:49957) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YPWEJ-0000gf-Tw for emacs-orgmode@gnu.org; Sun, 22 Feb 2015 08:05:52 -0500 Received: from [192.168.1.156] (unknown [113.111.115.92]) by esmtp4.qq.com (ESMTP) with SMTP id 0 for ; Sun, 22 Feb 2015 21:05:15 +0800 (CST) In-Reply-To: <14bb1576a18.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com> 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: emacs-orgmode@gnu.org Just wondering if anyone has any experience with texts written in org, which then need to be translated. The simplest thing, of course, would be an org file for the original language, and then separate files for other languages. Markup and export are simpler this way, but future edits would be harder to sync. For the edit/sync problem (and also because hey, we're org users, meaning born tinkerers), I'm wondering if it's worth interleaving the languages in the same file, with some kind of tagging to select one or more languages for export. I'm struggling to imagine how that would look. Regular org tags wouldn't work because they're hierarchical, and there's no point in considering any sort of scheme for this if you can't keep original text and translation close together. Maybe language prefixes, which an export filter could process? Perhaps: * en: Hello fr: Bonjour To be honest, I'm a bit skeptical of doing this at all because it would be a chunk of work and it would clutter the org files visually. But if someone has figured out a clever way, I'd be curious to hear about it. Thanks in advance -- hjh Sent with AquaMail for Android http://www.aqua-mail.com