all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37327@debbugs.gnu.org
Subject: bug#37327: Simplifying access to built-in tutorial
Date: Sat, 7 Sep 2019 11:20:39 +0200	[thread overview]
Message-ID: <11180519-e0ba-fa2d-0a17-60512bebc357@gmail.com> (raw)
In-Reply-To: <83tv9p5jt0.fsf@gnu.org>

>> English is still the main language for learning to use Emacs; the
>> tutorials in other languages are mainly for people who have
>> difficulties in understanding English (...)
>
> (...) more importantly, the English version (...) is maintained by
> the Emacs developers, so is always up to date; (...)  the
> translations are updated by translators if and when they become
> available, and so could potentially become outdated (...)

1.  English version is still among languages.  Additionally you could
change its name to "English (default)" or "English (official)" to
emphasize that it is recommended one.  You could even add it as
default argument - "Language (default English):".

2.  If English version is the recommended way, then why 'C-h t' loads
by default version that corresponds with user language environment,
i.e. if I type it I get Polish version?  If English version is most
up-to-date it should be loaded by default no matter what (I think
Emacs 25.2 behaved this way), and then the rest should be optional and
only available through 'help-with-tutorial-spec-language'.





  reply	other threads:[~2019-09-07  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 17:39 bug#37327: Simplifying access to built-in tutorial Sebastian Urban
2019-09-06 18:18 ` Eli Zaretskii
2019-09-06 19:03   ` Eli Zaretskii
2019-09-07  9:20     ` Sebastian Urban [this message]
2019-09-07 10:25       ` Eli Zaretskii
2019-09-07 19:31         ` Sebastian Urban
2021-09-22 21:00   ` Lars Ingebrigtsen

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=11180519-e0ba-fa2d-0a17-60512bebc357@gmail.com \
    --to=mrsebastianurban@gmail.com \
    --cc=37327@debbugs.gnu.org \
    --cc=eliz@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.