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 >