On Wed, May 29, 2013 at 06:46:59PM +0200, Christian Moe wrote:
>
> Tristan Nakagawa writes:
>
> > 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
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 th
Tristan Nakagawa writes:
> 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 symbol, not literally "" in the code.
Hi, glad to hear it worked out.
Di
Hi,
For some reason, I don't get the follow-ups per mail, neither can I
respond via the gmane interface =(.
Right now I don't have time to figure it out, so I will let you know
here for all solutions:
Thanks, all, very nice! In fact, pure awesomeness!
And it's brand new. I didn't know about it b
On Wed, May 29, 2013 at 09:20:52AM +0200, Christian Moe wrote:
>
> Suvayu Ali writes:
>
> > Maybe we could allow backend specific macro expansion definitions.
> > Something like:
> >
> > #+HTML_MACRO: ruby $1 ($2) <\ruby>
> > #+LATEX_MACRO: ruby \ruby{$1}{$2}
> >
> > Then {{{ruby(東,ひがし)}}}
Suvayu Ali writes:
> Maybe we could allow backend specific macro expansion definitions.
> Something like:
>
> #+HTML_MACRO: ruby $1 ($2) <\ruby>
> #+LATEX_MACRO: ruby \ruby{$1}{$2}
>
> Then {{{ruby(東,ひがし)}}} will be expanded appropriately for
> different backends.
>
> What do you think?
Hi Tristan,
don't get me wrong. Being married to a Chinese and lived in Japan for many
years I know exactly what you are talking about ;)
I just feel it needs some clean and well defined way how to implement all
those different export features without cluttering the basic exporters.
Somehow the s
Hi Torsten,
Thanks for the input,
To have definable export rules would indeed be great, to increase
flexibility while keeping the base exporter simple and lightweight.
I agree that this is somewhat specific, however, I believe that
globally, this is not unfrequent, and will become quite frequent
Suvayu Ali writes:
> On Tue, May 28, 2013 at 03:00:40PM +0200, Torsten Wagner wrote:
>>
>> However, I believe that for many users, the special cases are not very
>> frequent and complex. Might it be possible to create a very simple syntax
>> for exporting rules which could be either in those abo
On Tue, May 28, 2013 at 05:01:56PM +0200, Suvayu Ali wrote:
>
> PS: Actually on second thought it is probably possible to handle this
> with filters although I failed to find the appropriate filter.
>
> So you could try:
>
> #+MACRO: ruby <$1><$2>
>
> And the filter can transl
On Tue, May 28, 2013 at 03:00:40PM +0200, Torsten Wagner wrote:
>
> However, I believe that for many users, the special cases are not very
> frequent and complex. Might it be possible to create a very simple syntax
> for exporting rules which could be either in those above modules or
> directly wi
Hi Tristan,
this feature request seems simple to implement on one side. However, it
opens a question how to deal with those in general.
\ruby{東} is a very specific command of the CJK package.
If this get's implemented in the standard html exporter, other very special
commands might need to follow.
Hi,
So this is my first try to post to the mailing list. I Love Orgmode, you
guys are the best!
I would like to use orgmode to capture japanese text to later export to
latex, html and epub.
For japanese symbols, sometimes the pronounciation is put in smaller
letters above the symbol to help
13 matches
Mail list logo
