From: Marcin Borkowski <mbork@mbork.pl>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Official Org manual in Org! (Was: Dog food, anyone?)
Date: Thu, 21 Dec 2017 09:00:00 +0100 [thread overview]
Message-ID: <87wp1go6in.fsf@mbork.pl> (raw)
In-Reply-To: <CAFyQvY1d3SkC-3hLEEo4pgfBKR0zOwYwjhuf8wdiaUy3edN2ag@mail.gmail.com>
Hi all,
my 2 cents.
1. Now that we know that it is possible to construct a texi document
from org automatically, whould it be feasible to get back to the topic
of converting the Emacs manual(s) to org? Would it make sense?
2. Re: the style guide: why not ditch em-dashes altogether? Quoting
Robert Brighurst:
,----
| The em dash is the nineteenth-century standard, still prescribed by
| many editorial style books, but the em dash is too long for use with
| the best text faces. Like the oversized space between sentences, it
| belongs to the padded and corseted aesthetic of Victorian
| typography. Use spaced en dashes – rather than em dashes or hyphens –
| to set off phrases.
`----
In case you think this is not something of utmost importance: I quoted
Bringhurst after the article
http://www.denizcemonduygu.com/2009/09/where-to-use-en-and-em-dashes-lupton-vs-bringhurst/,
where this gem can be found:
,----
| The en dash between your birth and death dates on your headstone will
| be representing your whole life. All your joys and sorrows, adventures
| and disappointments, tucked in something slightly longer than a hyphen
| and shorter than an em dash. So go on ignoring them. The dashes will
| have the last word.
`----
Best,
Marcin
On 2017-12-17, at 19:58, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> Hi Nicholas,
>
> Thanks for taking up this humongous project. It was a dream of many like me
> to eventually read and maintain the Org manual in Org :)
>
> To be honest, I discarded this email by instinct by just reading the title
> "Dog food, anyone?", as I assumed that email to be from my neighborhood
> community, with someone giving away their extra dog food (literally).. and
> I don't own dogs.. so off the email went.. to my "read bin".. :)
>
> It wasn't until few minutes back that I realized what this email was and
> that it was actually on the Org list.. so changing the title for more
> visibility.
>
> This arduous task shouldn't go unrecognized.
>
> ---------- Forwarded message ---------
> From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Sun, Dec 17, 2017 at 5:35 AM
> Subject: [O] [RFC] Dog food, anyone?
> To: Org Mode List <emacs-orgmode@gnu.org>
>
>
> Hello,
>
> The task started by Thomas S. Dye a couple years ago is now complete.
> The "manual.org" file in "contrib/" directory is an up-to-date,
> sometimes enhanced, version of the Org manual. Org can now eat its own
> dog food.
>
> During the process, I had to re-organize some parts of the manual (e.g.,
> "Working with source code" section, the concept index...) and improve
> the "texinfo" export back-end, which was not up to the task when Thomas
> started it.
>
> Ultimately, this file is going to serve as the source for a new
> "org.texi". IOW, it could go into "doc/" and "make info" should export
> "manual.org" to "org.texi". First, however, it would be nice to review
> it, either as an Org file, or within the Info viewer, with
>
> (require 'ox-texinfo)
>
> and
>
> `C-c C-e i o' from "manual.org".
>
> Note that Info output is expected to be sometimes different from the
> current manual. This is not a 1:1 conversion.
>
> Feedback welcome!
>
>
> Regards,
>
> --
> Nicolas Goaziou 0x80A93738
--
Marcin Borkowski
next prev parent reply other threads:[~2017-12-21 8:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 10:34 [RFC] Dog food, anyone? Nicolas Goaziou
2017-12-17 11:59 ` Vikas Rawal
2017-12-17 18:41 ` Thomas S. Dye
2017-12-17 19:01 ` Nicolas Goaziou
2017-12-17 21:58 ` Thomas S. Dye
2017-12-17 23:03 ` Adrian Bradd
2017-12-18 1:13 ` Thomas S. Dye
2017-12-17 23:44 ` Nicolas Goaziou
2017-12-18 1:15 ` Vikas Rawal
2017-12-18 1:23 ` Thomas S. Dye
2017-12-17 18:51 ` Kaushal Modi
2017-12-17 19:27 ` Nicolas Goaziou
2017-12-17 18:58 ` [RFC] Official Org manual in Org! (Was: Dog food, anyone?) Kaushal Modi
2017-12-21 8:00 ` Marcin Borkowski [this message]
2017-12-21 13:47 ` [RFC] Official Org manual in Org! Nicolas Goaziou
2017-12-17 23:10 ` [RFC] Dog food, anyone? Eric Abrahamsen
2017-12-18 21:02 ` Thomas S. Dye
2017-12-18 22:04 ` Nicolas Goaziou
2017-12-19 0:12 ` Thomas S. Dye
2017-12-19 19:25 ` Nicolas Goaziou
2017-12-19 20:11 ` Thomas S. Dye
2017-12-19 20:16 ` Jonathan Leech-Pepin
2017-12-19 23:11 ` Nicolas Goaziou
2017-12-20 0:05 ` Jonathan Leech-Pepin
2017-12-20 0:59 ` Thomas S. Dye
[not found] ` <WM!57dfd1c25b2c2af3021c1294841c916968d326cf362c32864a6fbc9615cf19dba6ceadc1960e4c3ef5578687af476fba!@mailhub-mx1.ncl.ac.uk>
2017-12-21 12:58 ` Phillip Lord
2017-12-21 13:37 ` Nicolas Goaziou
2017-12-21 17:26 ` Phillip Lord
2017-12-21 19:53 ` Nicolas Goaziou
[not found] ` <WM!3e1c2e8dc2d528e2348759d2a34555337e2f3a5782534bcece582121239ecf030ff1b6d5efd2b2c4955a04c496f00ac6!@mailhub-mx2.ncl.ac.uk>
2017-12-21 22:13 ` Phillip Lord
2017-12-22 18:30 ` Nicolas Goaziou
2017-12-23 6:56 ` Yasushi SHOJI
2017-12-23 14:12 ` Kaushal Modi
2017-12-25 1:44 ` Yasushi SHOJI
2018-04-26 23:34 ` Bastien
2018-04-28 10:56 ` Nicolas Goaziou
2018-04-28 12:43 ` Bastien
2018-05-09 0:30 ` Nicolas Goaziou
2018-05-09 18:16 ` Gregor Zattler
2018-05-09 19:12 ` Nicolas Goaziou
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=87wp1go6in.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).