unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal: include list of contributors on GNU Emacs website
Date: Tue, 29 Oct 2019 02:39:03 +0530	[thread overview]
Message-ID: <20191028210903.GR8382@protected.rcdrun.com> (raw)
In-Reply-To: <1d0af191-db77-f0fd-aa12-83dc5d22a537@cs.ucla.edu>

* Paul Eggert <eggert@cs.ucla.edu> [2019-10-29 02:21]:
> On 10/28/19 11:58 AM, Jean Louis wrote:
> > > There is no script. Someone could write a script that would do a
> > > good job of what you're suggesting, and volunteers are welcome to do
> > > so.
> > There is example I gave you.
> 
> That example is just part of the problem; it's not enough to generate the
> web page you asked for. For example, the file that the script generates for
> Emacs (once you modify it to work for Emacs), is improperly encoded because
> some of the names are in UTF-8 and some use a different (non-ASCII)
> encoding.

You mean some other encoding but not the UTF-8? But I could run it in
Emacs and edit the list without problems just as UTF-8. Which name
exactly? 

> There are other glitches like that that would need to be
> addressed. Plus, surely we can do better than a plain text file
> listing one name per line.
> 
> Furthermore, having just that script is not enough; there needs to be an
> automated way to generate the updated website. It's not a hard job to
> automate all this, but it is work that someone would need to do (and more
> importantly, test).

I do not have a clue how Emacs website is maintained.

I know how are my pages maintained, so I have templates and inside of
templates I can even run scripts, or Emacs functions, and such make
the output and it is inserted into the page, and later often
formatted by markdown to HTML.

When static page generator starts generating, script is run and I
don't need to take care of it.

For me that would be matter of few minutes to generate list of
authors, with some "," (commas) in between or similar.



  reply	other threads:[~2019-10-28 21:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28  7:29 Proposal: include list of contributors on GNU Emacs website Jean Louis
2019-10-28  8:49 ` Eli Zaretskii
2019-10-28  9:12   ` Jean Louis
2019-10-28 10:23     ` Eli Zaretskii
2019-10-28 10:41       ` Jean Louis
2019-10-28 18:45         ` Paul Eggert
2019-10-28 18:58           ` Jean Louis
2019-10-28 20:30             ` Eli Zaretskii
2019-10-28 21:12               ` Jean Louis
2019-10-28 20:50             ` Paul Eggert
2019-10-28 21:09               ` Jean Louis [this message]
2019-10-29  0:14                 ` Paul Eggert
2019-10-29  6:04               ` VanL
2019-10-28 20:05           ` Eli Zaretskii
2019-10-28 20:16             ` Jean Louis
2019-10-29  3:03     ` Richard Stallman

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=20191028210903.GR8382@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=eggert@cs.ucla.edu \
    --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).