bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] ELPA and gettext.el


From: Bruno Haible
Subject: Re: [bug-gettext] ELPA and gettext.el
Date: Sun, 20 Jan 2019 11:58:31 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-141-generic; KDE/5.18.0; x86_64; ; )

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]