From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.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 13:42:32 -0500 [thread overview]
Message-ID: <CAEWDx5d21Y0TtGcJyyTTAydC3pz3-=YYSm=Xyxj6NHZnK8mA6g@mail.gmail.com> (raw)
In-Reply-To: <m14nkura6e.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 3824 bytes --]
On 12 November 2012 12:41, Thomas S. Dye <tsd@tsdye.com> wrote:
> 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.
>
I believe most of the entities should be capable of exporting the
entities as well.
I also must stress that there's no guarantee that the texinfo exporter
will be able to generate documents that for anything other than info
use. I haven't tested any documents with the other exporters, but I
focused on trying to provide successful export to info.
>>
> >> 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
>
[-- Attachment #2: Type: text/html, Size: 5603 bytes --]
next prev parent reply other threads:[~2012-11-12 18:42 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
2012-11-12 18:42 ` Jonathan Leech-Pepin [this message]
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
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='CAEWDx5d21Y0TtGcJyyTTAydC3pz3-=YYSm=Xyxj6NHZnK8mA6g@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=tsd@tsdye.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 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).