all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Changing the language of gnus menu entries
Date: Wed, 25 Sep 2013 20:29:55 +0200	[thread overview]
Message-ID: <87li2k92l8.fsf@web.de> (raw)
In-Reply-To: 837ge4hpco.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Date: Wed, 25 Sep 2013 15:30:11 +0200
> > 
> > I don't have a good feeling about that.  It's already lots of work to
> > keep the English docstrings up to date.  And if some volunteers leave,
> > people are left with outdated docstrings in their language they count
> > on.
> > 
> > I'm not against localizing menus, but docstrings?  Most of programmers
> > will understand English, and binding so much work, constantly, for very
> > few users?  IMHO we should spend our time with other important tasks to
> > improve user experience.
>
> You are, in effect, saying that Emacs should not be localized.  If doc
> strings, echo-area messages, and help-echo messages are not to be
> localized, what's the value of having single-word menus localized?

There are some beginners that even don't know M-x - localized menus
would be cool for such users, as a start in using Emacs - nothing more.
But you're right about me saying that Emacs should not be localized, in
general.

Why?  Even if I ignore the massive amount of work that could be invested
at other places for more benefit, I see many disadvantages:

- Half of docstring words are Emacs-specific technical terms.  How
  would you translate such words as "frame", "point", "face" into, say,
  German?  There are now words for that.  When I talk about Emacs with
  my friends (in German), I also say "frame", "point" etc.

- If you don't speak English, how will you memorize hundreds of command
  names?  We would have to localize command names, too.  But then,
  keybindings are hard to remember, because lots of them are
  abbreviations of (English) command names.

- Do we do people a favor?  Not speaking English, you won't be able to
  get help from gnu.emacs.help.  You won't write bug reports.  Yes,
  that's possible - theoretically.  But Emacs community is too small to
  keep this alive in practice.  You won't be able to talk to developers.
  You just can't participate.

- A great feature of Emacs is that there are third party packages for
  lots of stuff.  Packages that are explained in English and nobody has
  time to translate.

At the end, I think, we would make some progress, and after most of the
work is done after some months or years, development will stop, and
nobody is there keeping things ticking over.  Because work having to be
done continuously must be fun, else, nobody cares.  We already see this
today with the English docs: how many reports arriving at gnu.emacs.bug
contain patches that are concerning documentation?


Regards,

Michael.




  reply	other threads:[~2013-09-25 18:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  7:29 Changing the language of gnus menu entries Uwe Scholz
2013-09-24 14:16 ` Peter Dyballa
2013-09-24 15:14 ` Joost Kremers
2013-09-24 16:41   ` Uwe Scholz
2013-09-24 19:48     ` Stefan Monnier
2013-09-24 20:07       ` Eli Zaretskii
     [not found]       ` <mailman.2807.1380053246.10748.help-gnu-emacs@gnu.org>
2013-09-24 21:48         ` Stefan Monnier
2013-09-25 13:30           ` Michael Heerdegen
2013-09-25 15:51             ` Eli Zaretskii
2013-09-25 18:29               ` Michael Heerdegen [this message]
2013-09-25 19:14                 ` Eli Zaretskii
2013-09-25 20:45                   ` Michael Heerdegen
     [not found]                   ` <mailman.2878.1380138900.10748.help-gnu-emacs@gnu.org>
2013-09-25 21:15                     ` Joost Kremers
2013-09-26  8:56                   ` Óscar Fuentes
2013-09-26  9:32                     ` Eli Zaretskii
     [not found]                 ` <<8338oshfy5.fsf@gnu.org>
2013-09-25 19:54                   ` Drew Adams
2013-09-25 20:08                     ` Drew Adams
2013-09-25 20:24                     ` Peter Dyballa
2013-09-25 23:09                       ` Drew Adams
     [not found]                       ` <mailman.2886.1380150595.10748.help-gnu-emacs@gnu.org>
2013-09-26  4:05                         ` Joost Kremers
2013-09-26 17:02                           ` Drew Adams
2013-09-26 17:09                           ` Peter Dyballa
2013-09-26 19:15                           ` Dale Snell
     [not found]                           ` <mailman.2935.1380214979.10748.help-gnu-emacs@gnu.org>
2013-09-26 17:22                             ` Dan Espen
2013-09-26 18:31                               ` Drew Adams
2013-09-26 20:37                             ` Joost Kremers
     [not found]                               ` <mailman.2964.1380232675.10748.help-gnu-emacs@gnu.org>
2013-09-26 22:21                                 ` Joost Kremers
     [not found]                             ` <<slrnl496os.2vt.joostkremers@j.kremers4.news.arnhem.chello.nl>
2013-09-26 21:57                               ` Drew Adams
     [not found]                           ` <mailman.2936.1380215384.10748.help-gnu-emacs@gnu.org>
2013-09-26 20:44                             ` Joost Kremers
     [not found]                           ` <mailman.2954.1380222979.10748.help-gnu-emacs@gnu.org>
2013-09-26 20:46                             ` Joost Kremers
2013-09-25 20:50                     ` Michael Heerdegen
     [not found]                 ` <mailman.2876.1380136471.10748.help-gnu-emacs@gnu.org>
2013-09-27  6:26                   ` Jason Rumney
2013-09-27  9:00                     ` Eli Zaretskii
2013-09-25 19:00             ` Stefan Monnier
2013-09-26  0:37               ` Stefan Monnier
     [not found]             ` <mailman.2861.1380124268.10748.help-gnu-emacs@gnu.org>
2013-09-25 19:13               ` Uwe Scholz
2013-09-24 20:08   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87li2k92l8.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.