From: Werner LEMBERG <wl@gnu.org>
To: cyd@stupidchicken.com
Cc: emacs-devel@gnu.org
Subject: Re: other serious problems with non-English tutorials
Date: Tue, 12 May 2009 20:55:24 +0200 (CEST) [thread overview]
Message-ID: <20090512.205524.216247862.wl@gnu.org> (raw)
In-Reply-To: <87ws8mnvem.fsf@cyd.mit.edu>
>> 1. *All* translations have this wrong because they assume that the
>> name is `TUTORIAL.XX', where `XX' is a two-letter country code
>> (or `XX_YY' if language and country names differ).
>
> Yes, I'll revert this change.
Thanks.
>> 2. A language specific tutorial is now loaded into a buffer only;
>> it is no longer associated with a real file. This invalidates
>> big parts of the translated tutorials; from a didactic point of
>> view it's a bad idea also IMHO.
>
> I don't understand the problem. The reason we put the tutorial in a
> buffer is so that the reader can edit the buffer freely.
For German, say, the tutorial expects that there exists a real file
called TUTORIAL.de (even if it is a local copy for the user), and the
corresponding buffer is called TUTORIAL.de too. Currently, we have a
buffer name `TUTORIAL (German)'.
> As far as I know, the tutorial code has not changed significantly
> since Emacs 22, when Lennart introduced tutorial.el. We did ask the
> translators to update the language-specific tutorials for the Emacs
> 22 release.
Hmm. I have missed that. And indeed, the problematic behaviour is
already present in Emacs 22 (and it seems that all other translators
have missed it too).
Werner
next prev parent reply other threads:[~2009-05-12 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 6:38 other serious problems with non-English tutorials Werner LEMBERG
2009-05-12 16:22 ` Chong Yidong
2009-05-12 17:43 ` Eli Zaretskii
2009-05-12 18:55 ` Werner LEMBERG [this message]
2009-05-13 7:48 ` Per Starbäck
2009-05-13 7:52 ` Werner LEMBERG
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=20090512.205524.216247862.wl@gnu.org \
--to=wl@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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.