* org-entities for texinfo
@ 2012-11-11 19:53 Thomas S. Dye
2012-11-11 20:13 ` Nicolas Goaziou
0 siblings, 1 reply; 6+ messages in thread
From: Thomas S. Dye @ 2012-11-11 19:53 UTC (permalink / raw)
To: Org-mode
Aloha all,
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?
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: org-entities for texinfo
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
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Goaziou @ 2012-11-11 20:13 UTC (permalink / raw)
To: Thomas S. Dye; +Cc: Org-mode
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).
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: org-entities for texinfo
2012-11-11 20:13 ` Nicolas Goaziou
@ 2012-11-12 14:49 ` Jonathan Leech-Pepin
2012-11-12 17:41 ` Thomas S. Dye
0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Leech-Pepin @ 2012-11-12 14:49 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: Org-mode, Thomas S. Dye
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1912 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: org-entities for texinfo
2012-11-12 14:49 ` Jonathan Leech-Pepin
@ 2012-11-12 17:41 ` Thomas S. Dye
2012-11-12 18:42 ` Jonathan Leech-Pepin
0 siblings, 1 reply; 6+ messages in thread
From: Thomas S. Dye @ 2012-11-12 17:41 UTC (permalink / raw)
To: Jonathan Leech-Pepin; +Cc: Org-mode, Nicolas Goaziou
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: org-entities for texinfo
2012-11-12 17:41 ` Thomas S. Dye
@ 2012-11-12 18:42 ` Jonathan Leech-Pepin
2012-11-12 19:56 ` Thomas S. Dye
0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Leech-Pepin @ 2012-11-12 18:42 UTC (permalink / raw)
To: Thomas S. Dye; +Cc: Org-mode, Nicolas Goaziou
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: org-entities for texinfo
2012-11-12 18:42 ` Jonathan Leech-Pepin
@ 2012-11-12 19:56 ` Thomas S. Dye
0 siblings, 0 replies; 6+ messages in thread
From: Thomas S. Dye @ 2012-11-12 19:56 UTC (permalink / raw)
To: Jonathan Leech-Pepin; +Cc: Org-mode, Nicolas Goaziou
Aloha Jon,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> 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.
>
Yes, I agree that the focus should be export to a syntactically correct
.texi file. AFAICT at this early stage of my experiment, you've achieved
that.
It was wrong-headed of me to be thinking about a back-end agnostic Org
document for this project. The texi2* tools have that issue covered.
Sorry for the red herring--I'm a noisy learner.
All the best,
Tom
>>>
>> >> 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
>>
> 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
>
>
--
Thomas S. Dye
http://www.tsdye.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-11-12 19:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2012-11-12 19:56 ` Thomas S. Dye
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).