From: Werner LEMBERG <wl@gnu.org>
Cc: ats@acm.org, emacs-devel@gnu.org
Subject: Re: ChangeLog fontifications
Date: Fri, 14 May 2004 08:24:38 +0200 (CEST) [thread overview]
Message-ID: <20040514.082438.39646866.wl@gnu.org> (raw)
In-Reply-To: <20040513215623.GA14133@fencepost>
> > This ChangeLog style is a typographic nightmare IMHO.
>
> On the contrary, it looks quite nice. IMO.
This is a misunderstanding. I'm not talking about looking nice, I'm
talking about the typographical `correctness'. As has been pointed
out by others, the grouping becomes artificial. Besides this, it
isn't something used anywhere else in the English language, AFAIK:
Imagine a sentence (consisting of nouns) (verbs, adjectives) (and
other words) like this and you see what you mean.
I know that it is not of importance that a ChangeLog entry is
grammatically correct, but intentionally working against such rules is
plain wrong for me. A good solution to make human and computerized
parsers happy could be this -- a traditional solution used by
typsetters since a few hundred years:
* foo/bar (long_item_1, long_item_2,
long_item_3, long_item_4,
long_item_5): Explanation of long
items 1 to five.
Or this (at the cost of making the entry longer):
* foo/bar (long_item_1, long_item_2,
long_item_3, long_item_4,
long_item_5):
Explanation of long items 1 to five.
Don't make man obey the tools, let's rather make the tools obey man!
Werner
next prev parent reply other threads:[~2004-05-14 6:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 18:50 ChangeLog fontifications Bruno Haible
2004-05-13 19:26 ` Miles Bader
2004-05-13 19:43 ` Bruno Haible
2004-05-13 20:38 ` Miles Bader
2004-05-13 21:12 ` Sam Steingold
2004-05-13 21:15 ` Miles Bader
2004-05-13 20:13 ` Alan Shutko
2004-05-13 20:42 ` Miles Bader
2004-05-13 21:37 ` Werner LEMBERG
2004-05-13 21:56 ` Miles Bader
2004-05-13 22:25 ` Stefan Monnier
2004-05-14 3:00 ` Karl Eichwalder
2004-05-14 4:24 ` Miles Bader
2004-05-14 13:56 ` Robert J. Chassell
2004-05-14 6:24 ` Werner LEMBERG [this message]
2004-05-14 6:36 ` Werner LEMBERG
2004-05-14 15:31 ` Sam Steingold
2004-05-14 21:02 ` Richard Stallman
2004-05-16 15:14 ` Bruno Haible
2004-05-16 16:52 ` Eli Zaretskii
2004-05-16 20:52 ` Miles Bader
2004-05-17 22:57 ` Richard Stallman
2004-05-18 5:02 ` Karl Eichwalder
2004-05-19 1:32 ` Miles Bader
2004-05-19 13:08 ` Sam Steingold
2004-05-19 13:22 ` Miles Bader
2004-05-19 14:59 ` Stefan Monnier
2004-05-19 13:45 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 17:15 Sam Steingold
2004-05-11 18:03 ` Juri Linkov
2004-05-11 22:54 ` Sam Steingold
2004-05-11 23:02 ` Miles Bader
2004-05-12 8:33 ` Werner LEMBERG
2004-05-12 10:10 ` Miles Bader
2004-05-12 12:36 ` Eli Zaretskii
2004-05-13 17:22 ` Sam Steingold
2004-05-14 21:01 ` Richard Stallman
2004-05-11 23:26 ` Stefan Monnier
2004-05-12 0:08 ` Juri Linkov
2004-05-12 5:48 ` Eli Zaretskii
2004-05-12 12:55 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040514.082438.39646866.wl@gnu.org \
--to=wl@gnu.org \
--cc=ats@acm.org \
--cc=emacs-devel@gnu.org \
/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.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).