From: Bruno Haible <bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org>
To: bug-gettext-mXXj517/zsQ@public.gmane.org,
emacs-devel-mXXj517/zsQ@public.gmane.org
Cc: Alexandre Garreau <galex-713-7424XhQ1Lrh7ZJesRCpzdA@public.gmane.org>
Subject: Re: ELPA and gettext.el
Date: Sat, 19 Jan 2019 12:37:43 +0100 [thread overview]
Message-ID: <2796499.L7i9Ne0m1H@omega> (raw)
In-Reply-To: <87zhrxxvsv.fsf-GJHrUhKTnLMAVn7cI0sOhGhLVPiuUekF@public.gmane.org>
Hi,
Alexandre Garreau wrote:
> Why isn’s gettext.el inside elpa?
You mean po-mode.el?
Many years ago, it was decided to distribute po-mode.el as part of GNU gettext,
not as part of GNU Emacs, because it should also run in XEmacs.
Nowadays, it appears that XEmacs has become insignificant:
- see https://trends.google.com/trends/explore?q=emacs,xemacs
- in major distros it has rendering problems in the menus
- XEmacs appears to have only 1 active developer nowadays
https://bitbucket.org/xemacs/xemacs/commits/all
Therefore I wouldn't mind if po-mode.el was moved outside gettext, if
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]
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.
> Would it be relevant and or reasonable to replicate it in ELPA?
Or maybe into emacs/lisp/ ?
I guess that when moving it to emacs/lisp/, the documentation could be
transferred easily into the Emacs documentation. On the other hand, users
would not have the "get the newest version easily" advantage, this way.
In any case, it should be a move (transfer), not a fork.
Bruno
[1] https://savannah.gnu.org/bugs/index.php?51547
[2] https://savannah.gnu.org/bugs/index.php?55145
[3] https://savannah.gnu.org/bugs/index.php?55146
[4] https://savannah.gnu.org/bugs/index.php?55147
[5] https://savannah.gnu.org/bugs/index.php?55150
[6] https://www.gnu.org/software/gettext/manual/html_node/PO-Mode.html
next prev parent reply other threads:[~2019-01-19 11:37 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 [this message]
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
2019-01-20 18:10 ` [bug-gettext] " 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=2796499.L7i9Ne0m1H@omega \
--to=bruno-nwnvuoht2mvytjvyw6ydsg@public.gmane.org \
--cc=bug-gettext-mXXj517/zsQ@public.gmane.org \
--cc=emacs-devel-mXXj517/zsQ@public.gmane.org \
--cc=galex-713-7424XhQ1Lrh7ZJesRCpzdA@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).