From: tsd@tsdye.com (Thomas S. Dye)
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: org-entities for texinfo
Date: Mon, 12 Nov 2012 07:41:13 -1000 [thread overview]
Message-ID: <m14nkura6e.fsf@tsdye.com> (raw)
In-Reply-To: <CAEWDx5eViPqs3D_cC-3NXMZ6hY+EkZ08gBx1g78=VJYeESQCDg@mail.gmail.com> (Jonathan Leech-Pepin's message of "Mon, 12 Nov 2012 09:49:22 -0500")
Aloha Nicolas and Jon,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> Hello,
>
> On 11 November 2012 15:13, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>> Hello,
>>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>> > With the new exporter's texinfo back-end, I think org-entities and
>> > org-entities-user might usefully be augmented with the entities listed
>> > in Chapter 14 of the texinfo manual, Special Insertions.
>> >
>> > Or, is there some other Org mechanism that might be preferable?
>>
>> AFAIU, texinfo can handle UTF-8 characters with:
>>
>> @documentencoding UTF-8
>>
>> (see section 18.2 from texinfo manual). So I guess it's safe to rely
>> on :utf-8 entities.
Yes, this seems to work fine. I was thinking about a back-end agnostic
Org document, but I see that texinfo has its own suite of exporters, so
there is no real need to export this document from Org using the other
back-ends.
>>
>> However, special characters like @dots{} are usually handled with
>> "special strings" mechanism, directly at the plain text transcoded (see
>> `org-e-latex-plain-text' for example).
>>
>
>
> I believe I accounted for most of the special strings that are
> directly transcoded in texinfo. There may be some that are missing,
> however they can be added directly in the document using the
> =@@info:<texinfo command>@@= syntax (inline export snippets).
>
This works well, too. Thanks.
> Are there any particular pieces of synxtax that you believe would be
> useful to have added to org-entities that would also be useful in
> other backends?
Not yet. I'm just getting started, but will let you know if I run into
any.
All the best,
Tom
>
>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>>
> Regards,
>
> --
> Jon
> Hello,
>
> On 11 November 2012 15:13, Nicolas Goaziou <n.goaziou@gmail.com>
> wrote:
>
> Hello,
>
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
> > With the new exporter's texinfo back-end, I think org-entities
> and
> > org-entities-user might usefully be augmented with the entities
> listed
> > in Chapter 14 of the texinfo manual, Special Insertions.
> >
> > Or, is there some other Org mechanism that might be preferable?
>
>
> AFAIU, texinfo can handle UTF-8 characters with:
>
> @documentencoding UTF-8
>
> (see section 18.2 from texinfo manual). So I guess it's safe to
> rely
> on :utf-8 entities.
>
> However, special characters like @dots{} are usually handled with
> "special strings" mechanism, directly at the plain text transcoded
> (see
> `org-e-latex-plain-text' for example).
>
>
>
> I believe I accounted for most of the special strings that are
> directly transcoded in texinfo. There may be some that are missing,
> however they can be added directly in the document using the
> =@@info:<texinfo command>@@= syntax (inline export snippets).
>
> Are there any particular pieces of synxtax that you believe would be
> useful to have added to org-entities that would also be useful in
> other backends?
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
>
>
> Regards,
>
> --
> Jon
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2012-11-12 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 19:53 org-entities for texinfo Thomas S. Dye
2012-11-11 20:13 ` Nicolas Goaziou
2012-11-12 14:49 ` Jonathan Leech-Pepin
2012-11-12 17:41 ` Thomas S. Dye [this message]
2012-11-12 18:42 ` Jonathan Leech-Pepin
2012-11-12 19:56 ` Thomas S. Dye
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m14nkura6e.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=n.goaziou@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.