From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: org-entities for texinfo Date: Mon, 12 Nov 2012 09:49:22 -0500 Message-ID: References: <87ip9b99uf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=00235429d2bc2e7a4a04ce4d684e Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40799) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXvKI-0007kg-Eh for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 09:49:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TXvKF-00037z-CI for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 09:49:26 -0500 Received: from mail-qa0-f48.google.com ([209.85.216.48]:48175) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXvKF-00037t-71 for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 09:49:23 -0500 Received: by mail-qa0-f48.google.com with SMTP id s11so1936335qaa.0 for ; Mon, 12 Nov 2012 06:49:22 -0800 (PST) In-Reply-To: <87ip9b99uf.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Org-mode , "Thomas S. Dye" --00235429d2bc2e7a4a04ce4d684e Content-Type: text/plain; charset=UTF-8 Hello, On 11 November 2012 15:13, Nicolas Goaziou 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:@@= 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 --00235429d2bc2e7a4a04ce4d684e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello,

On 11 November 2012 15:13, Nicolas= Goaziou <n.goaziou@gmail.com> wrote:
Hello,

tsd@tsdye.com (Thomas S. Dye) writes:<= br>
> 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:

=C2=A0 @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 transcode= d (see
`org-e-latex-plain-text' for example).
=C2=A0

I believe I accounted for most of the special s= trings that are
directly transcoded in texinfo.=C2=A0 There may be some = that are missing,
however they can be added directly in the document usi= ng the
=3D@@info:<texinfo command>@@=3D syntax (inline export snippets).
=
Are there any particular pieces of synxtax that you believe would beuseful to have added to org-entities that would also be useful in
other= backends?


Regards,

--
Nicolas Goaziou


Regards,

--
Jon
--00235429d2bc2e7a4a04ce4d684e--