From: Daniel Clemente <n142857@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-odt-export-to-odt: hide text
Date: Sun, 07 Jul 2013 15:48:39 +0700 [thread overview]
Message-ID: <87ip0m21so.wl%n142857@gmail.com> (raw)
In-Reply-To: <87fvvr11um.fsf@ericabrahamsen.net>
>
> You put your translation table in an org table, and there's a command to
> slurp that into a hashtable. The translation commands just whizz through
> the text and swap strings, basically. You can do subtree/region/file,
> tag subtrees to translate or not to translate, and there are interactive
> (a la query-replace) and noninteractive (for use as an export hook)
> versions.
>
This is the usual gettext approach, which centralizes translations in a file (or table). When you change the original, your strings won't be found and you must update the translation table.
I prefer the approach of having a phrase's translations together, so that you when you make a change you can update the translations from the same place.
An overlay system in Emacs could show only „the current language“ and hide the others, then with some keys you could cycle through languages.
I think this is something that can be done at an Emacs level (since it's for any text file), and org can simply use it.
next prev parent reply other threads:[~2013-07-07 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 12:17 org-odt-export-to-odt: hide text Uwe Brauer
2013-07-05 17:07 ` Eric S Fraga
2013-07-05 17:22 ` Uwe Brauer
2013-07-05 17:40 ` Eric S Fraga
2013-07-05 19:26 ` Uwe Brauer
2013-07-06 7:13 ` Suvayu Ali
2013-07-06 8:37 ` Uwe Brauer
2013-07-06 11:03 ` Suvayu Ali
2013-07-06 16:48 ` Daniel Clemente
2013-07-07 3:32 ` Eric Abrahamsen
2013-07-07 8:04 ` Suvayu Ali
2013-07-07 8:48 ` Daniel Clemente [this message]
2013-07-06 9:52 ` Christian Moe
2013-07-07 7:23 ` Rustom Mody
2013-07-07 8:05 ` Suvayu Ali
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=87ip0m21so.wl%n142857@gmail.com \
--to=n142857@gmail.com \
--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).