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 13:42:32 -0500 Message-ID: References: <87ip9b99uf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf300e4bef149b0104ce50aa58 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34041) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXyxx-00028Q-1v for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 13:42:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TXyxu-0007Lb-0O for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 13:42:36 -0500 Received: from mail-qa0-f41.google.com ([209.85.216.41]:48744) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXyxt-0007LN-JX for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 13:42:33 -0500 Received: by mail-qa0-f41.google.com with SMTP id c26so2071223qad.0 for ; Mon, 12 Nov 2012 10:42:33 -0800 (PST) In-Reply-To: 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: "Thomas S. Dye" Cc: Org-mode , Nicolas Goaziou --20cf300e4bef149b0104ce50aa58 Content-Type: text/plain; charset=UTF-8 On 12 November 2012 12:41, Thomas S. Dye wrote: > Aloha Nicolas and Jon, > > Jonathan Leech-Pepin writes: > > > 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. > > 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:@@= 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 > > 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 > > -- > Thomas S. Dye > http://www.tsdye.com > --20cf300e4bef149b0104ce50aa58 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 12 November 2012 12:41, Thomas S. Dye= <t= sd@tsdye.com> wrote:
Aloha Nicolas and Jon,

Jonathan Leech-Pepin <j= onathan.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-ent= ities and
>> > org-entities-user might usefully be augmented with the entiti= es listed
>> > in Chapter 14 of the texinfo manual, Special Insertions.
>> >
>> > Or, is there some other Org mechanism that might be preferabl= e?
>>
>> 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 t= o rely
>> on :utf-8 entities.

Yes, this seems to work fine. I was thinking about a back-end agnosti= c
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 b= e capable of exporting the
entities as well.

I also must stress t= hat there's no guarantee that the texinfo exporter
will be able to g= enerate documents that for anything other than info
use.=C2=A0 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<= br> >> "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. =C2=A0There may be some that are missi= ng,
> however they can be added directly in the document using the
> =3D@@info:<texinfo command>@@=3D syntax (inline export snippets)= .
>

This works well, too. =C2=A0Thanks.

> 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:
>
> =C2=A0 =C2=A0 Hello,
>
>
> =C2=A0 =C2=A0 tsd@tsdye.com (Thom= as S. Dye) writes:
>
> =C2=A0 =C2=A0 > With the new exporter's texinfo back-end, I thi= nk org-entities
> =C2=A0 =C2=A0 and
> =C2=A0 =C2=A0 > org-entities-user might usefully be augmented with = the entities
> =C2=A0 =C2=A0 listed
> =C2=A0 =C2=A0 > in Chapter 14 of the texinfo manual, Special Insert= ions.
> =C2=A0 =C2=A0 >
> =C2=A0 =C2=A0 > Or, is there some other Org mechanism that might be= preferable?
>
>
> =C2=A0 =C2=A0 AFAIU, texinfo can handle UTF-8 characters with:
>
> =C2=A0 =C2=A0 =C2=A0 @documentencoding UTF-8
>
> =C2=A0 =C2=A0 (see section 18.2 from texinfo manual). So I guess it= 9;s safe to
> =C2=A0 =C2=A0 rely
> =C2=A0 =C2=A0 on :utf-8 entities.
>
> =C2=A0 =C2=A0 However, special characters like @dots{} are usually han= dled with
> =C2=A0 =C2=A0 "special strings" mechanism, directly at the p= lain text transcoded
> =C2=A0 =C2=A0 (see
> =C2=A0 =C2=A0 `org-e-latex-plain-text' for example).
> =C2=A0 =C2=A0 =C2=A0
>
>
> I believe I accounted for most of the special strings that are
> directly transcoded in texinfo.=C2=A0 There may be some that are missi= ng,
> however they can be added directly in the document using the
> =3D@@info:<texinfo command>@@=3D 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?
>
>
> =C2=A0 =C2=A0 Regards,
>
> =C2=A0 =C2=A0 --
> =C2=A0 =C2=A0 Nicolas Goaziou
>
>
>
> Regards,
>
> --
> Jon

--
Thomas S. Dye
http://www.tsdye.com=

--20cf300e4bef149b0104ce50aa58--