From: "T.V Raman" <raman@google.com>
To: yantar92@gmail.com
Cc: briangpowellms@gmail.com, raman@google.com,
maciaschain@posteo.net, theophilusx@gmail.com,
emacs-orgmode@gnu.org
Subject: Re: Org mode export accessibility
Date: Fri, 8 Jul 2022 06:54:40 -0700 [thread overview]
Message-ID: <25288.14112.348044.505770@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <874jzs440s.fsf@localhost>
Correct.
1. Org should be the truth, not some export format that is picked
based on political opinion.
2. Lowest Common denominator in my vocabulary is a "bad word" that LCD
is something that makes everyone equally unhappy.
So Take-Away:
1. Make org the best format for holding the authored content.
2. Consider all exports to be either modality or use-case
specific and produce the best version that that export
format can support.
3. But then dont fall into the delusion that the export
format is the truth --
Ihor Radchenko writes:
> briangpowell <briangpowellms@gmail.com> writes:
>
> > Suggest OrgMode outputs focus on creating "Lowest Common Denominator"
> > documents as output:
> > TeXinfo docs should be used as the LCD doctype--suggest you focus on
> > creating 1 document in Texinfo that you use to create all other sorts of
> > documents, when possible:
> >
> > Pipeline should be more like
> > OrgMode->Texinfo->TROFF||DTD/XML/HTML/XHTML->LaTeX/TeX->DVI||SVG->PS->PDF
> >
> > * TeXinfo: https://savannah.gnu.org/projects/texinfo
> > https://www.gnu.org/software/texinfo
>
> I do not think that using Texinfo as intermediate format is useful.
> Texinfo does not support many of the available Org syntax structures
> like, for example, backend-specific export blocks. We will inevitably
> lose some document structure information when exporting to Texinfo.
> Please remember that Texinfo is by no means a generic export engine - it
> is tailored to produce software documentation specifically and may not
> be suitable for more generic authored documents.
>
> Note that we already have a much more feature-full export functionality.
> RMS even suggested that Org might be used as a replacement for Texinfo:
> https://yhetil.org/emacs-devel/E1nzQh5-0001OB-22@fencepost.gnu.org
>
> Best,
> Ihor
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
prev parent reply other threads:[~2022-07-08 13:55 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:30 About 'inline special blocks' Juan Manuel Macías
2022-05-23 15:20 ` Kaushal Modi
2022-05-23 21:06 ` Juan Manuel Macías
2022-05-24 2:36 ` Tim Cross
2022-05-24 2:51 ` Timothy
2022-05-24 6:54 ` Eric S Fraga
2022-05-26 7:30 ` Christian Moe
2022-05-24 15:09 ` Max Nikulin
2022-05-25 7:22 ` Ihor Radchenko
2022-05-25 17:05 ` Max Nikulin
2022-05-26 2:54 ` Merging paragraphs separated by comment lines during export (was: About 'inline special blocks') Ihor Radchenko
2022-05-24 3:56 ` About 'inline special blocks' Ihor Radchenko
2022-05-24 14:05 ` João Pedro
2022-05-26 4:56 ` Ihor Radchenko
2022-05-26 11:30 ` João Pedro
2022-05-26 12:20 ` Ihor Radchenko
2022-05-26 17:35 ` João Pedro
2022-05-26 21:22 ` About opening issues vs email [Was: About 'inline special blocks'] Kaushal Modi
2022-05-27 4:24 ` Ihor Radchenko
2022-05-27 4:36 ` João Pedro
2022-05-25 13:55 ` About 'inline special blocks' Juan Manuel Macías
2022-06-17 6:28 ` Ihor Radchenko
2022-06-17 19:49 ` Juan Manuel Macías
2022-06-19 12:47 ` Juan Manuel Macías
2022-06-19 19:30 ` Christian Moe
2022-06-19 20:15 ` Juan Manuel Macías
2022-06-19 22:18 ` Tim Cross
2022-06-20 16:57 ` Max Nikulin
2022-06-20 19:06 ` Juan Manuel Macías
2022-06-21 16:39 ` Max Nikulin
2022-06-21 18:19 ` Juan Manuel Macías
2022-06-20 22:46 ` Tim Cross
2022-06-26 4:07 ` Org mode export accessibility (was: About 'inline special blocks') Ihor Radchenko
2022-06-26 6:29 ` Tim Cross
2022-06-26 10:46 ` Org mode export accessibility Juan Manuel Macías
2022-06-26 10:54 ` Ihor Radchenko
2022-06-27 14:40 ` T.V Raman
2022-06-30 7:53 ` Ihor Radchenko
2022-07-07 14:18 ` briangpowell
2022-07-07 14:42 ` T.V Raman
2022-07-08 4:38 ` Ihor Radchenko
2022-07-08 13:55 ` T.V Raman
2022-07-09 3:39 ` Ihor Radchenko
2022-07-09 13:20 ` T.V Raman
2022-09-30 11:07 ` Max Nikulin
2022-09-30 13:29 ` T.V Raman
2022-09-30 16:43 ` Max Nikulin
2022-09-30 16:55 ` T.V Raman
2022-10-01 4:36 ` Ihor Radchenko
2022-10-01 14:59 ` T.V Raman
2022-10-02 2:54 ` Org source in PDF (Re: Org mode export accessibility) Max Nikulin
2022-10-02 3:50 ` Timothy
2022-07-07 14:43 ` Org mode export accessibility T.V Raman
2022-07-07 15:37 ` T.V Raman
2022-07-08 4:33 ` Ihor Radchenko
2022-07-08 13:54 ` T.V Raman [this message]
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=25288.14112.348044.505770@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=briangpowellms@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=theophilusx@gmail.com \
--cc=yantar92@gmail.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).