From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Feature Request] - Furigana - Yomigana - Ruby
Date: Wed, 29 May 2013 20:13:23 +0200 [thread overview]
Message-ID: <20130529181323.GE16384@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <51A61CB5.2070405@googlemail.com>
Hello Tristan,
Since you broought up Org versions, I thought it would be pertinent to
classify the version dependence of the possible solutions.
On Wed, May 29, 2013 at 05:20:21PM +0200, Tristan Nakagawa wrote:
>
> I didn't get Suvayus solution in the old version, i suspect it might
> work in the new version, but since the snippet version (see below)
> doesnt involve changing the backend for every macro, i didn't follow up
> on it
My solution with filters is only possible with Org 8.x or above. Also a
minor nit-pick, my solution goes into your emacs setup; the backends
stay as it is. But I would say Christian's solution is much more
elegant and portable in the sense that the Org file is self contained
and independent of the setup.
> Thomas' ruby link solution works nicely (except the closing tag should
> be </ruby>, not <\ruby>, and works for both for latex and html.
>
> The only downside is that you won't see the symbol in the original
> orgfile or in section headers in the export, just the reading, but that
> is a very minor annoyance and this is a very nice elegant solution with
> a very readable source org file.
> (I don't guess the link could be redefined to switch reading and symbol
> around?)
Tom's solution is probably the most portable across different Org
versions.
> Christians suggestion with snippets works great, both for html and pdf
> via latex; even in section headers.
> (it took me reading the 8.0 upgrade info to understand we were talking
> about the <at> symbol, not literally "<at>" in the code.
This one again is a Org 8.x or above solution.
Hope you can adapt either of these to your needs.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2013-05-29 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 22:41 [Feature Request] - Furigana - Yomigana - Ruby T.T.N.
2013-05-28 13:00 ` Torsten Wagner
2013-05-28 15:01 ` Suvayu Ali
2013-05-28 15:27 ` Suvayu Ali
2013-05-28 15:34 ` Thomas S. Dye
2013-05-29 7:20 ` Christian Moe
2013-05-29 7:30 ` Suvayu Ali
2013-05-28 15:43 ` Tristan Nakagawa
2013-05-28 17:36 ` Torsten Wagner
2013-05-29 15:20 ` Tristan Nakagawa
2013-05-29 16:46 ` Christian Moe
2013-05-29 18:15 ` Suvayu Ali
2013-05-29 18:13 ` Suvayu Ali [this message]
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=20130529181323.GE16384@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).