unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Haible <bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org>
To: Glenn Morris <rgm-mXXj517/zsQ@public.gmane.org>
Cc: Paul Eggert <eggert-764C0pRuGfqVc3sceRu5cw@public.gmane.org>,
	emacs-devel-mXXj517/zsQ@public.gmane.org,
	Alexandre Garreau
	<galex-713-7424XhQ1Lrh7ZJesRCpzdA@public.gmane.org>,
	bug-gettext-mXXj517/zsQ@public.gmane.org
Subject: Re: ELPA and gettext.el
Date: Sun, 20 Jan 2019 11:58:31 +0100	[thread overview]
Message-ID: <18002249.PFuSW9TAes@omega> (raw)
In-Reply-To: <yjbm4cuwpd.fsf-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>

Glenn Morris wrote:
> >  2) The documentation is handled appropriately. Currently it is documented
> >     through some texinfo-formatted documentation [6]. Whereas ELPA packages,
> >     as far as I can see, currently only have plain text documentation, which
> >     is inferior to texinfo / hypertext formatted documentation.
> 
> ELPA packages may contain info pages. Ref
> 
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Multi_002dfile-Packages.html

Can ELPA packages also provide HTML-format documentation (generated from
texinfo sources) in a canonical way? HTML rendering is decent, 'info' rendering
in Emacs is inferior (use of fixed-width font for plain text, use of _xxx_
for @emph instead of slanted/italic face, etc.). Therefore I would want
to provide the documentation in HTML at least.

> Personally, I strongly recommend creating an ELPA package rather than
> adding to Emacs itself.

Hmm. I'm hearing mixed voices (Paul vs. Glenn).

> >   1) The responsibility of po-mode.el was transferred to the Emacs community
> >      at the same time. Yes, it would be welcome if someone could take care of
> >      the 5 open bugs regarding the PO mode. [1][2][3][4][5]
> 
> Simply moving the files to another repository (GNU Emacs or ELPA) won't
> create a maintainer for them. There is no GNU ELPA community AFAIK.
> Excepting perhaps Stefan, it seems to be individuals maintaining their
> own packages. Emacs itself has a small number of active people, but less
> used components can languish.

Would moving po-mode.el to emacs/lisp/ make it more probable that it gets
occasional attention and maintenance from developers familiar with Emacs Lisp,
than putting it in ELPA?

Bruno




  parent reply	other threads:[~2019-01-20 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  1:47 ELPA and gettext.el Alexandre Garreau
     [not found] ` <87zhrxxvsv.fsf-GJHrUhKTnLMAVn7cI0sOhGhLVPiuUekF@public.gmane.org>
2019-01-19 11:37   ` Bruno Haible
2019-01-19 17:58     ` [bug-gettext] " Paul Eggert
2019-01-19 22:08       ` Glenn Morris
     [not found]         ` <yjbm4cuwpd.fsf-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2019-01-20 10:58           ` Bruno Haible [this message]
2019-01-20 18:10             ` Alexandre Garreau
2019-01-25 20:58             ` Paul Eggert
2019-01-26  0:53               ` Stefan Monnier
     [not found]                 ` <jwvsgxgw8b2.fsf-monnier+emacs-mXXj517/zsQ@public.gmane.org>
2019-01-26  7:18                   ` Eli Zaretskii

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=18002249.PFuSW9TAes@omega \
    --to=bruno-nwnvuoht2mvytjvyw6ydsg@public.gmane.org \
    --cc=bug-gettext-mXXj517/zsQ@public.gmane.org \
    --cc=eggert-764C0pRuGfqVc3sceRu5cw@public.gmane.org \
    --cc=emacs-devel-mXXj517/zsQ@public.gmane.org \
    --cc=galex-713-7424XhQ1Lrh7ZJesRCpzdA@public.gmane.org \
    --cc=rgm-mXXj517/zsQ@public.gmane.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).