unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: Hebrew xlation of Emacs tutorial
Date: Fri, 2 Feb 2007 12:28:18 -0800	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMKEKDCOAA.drew.adams@oracle.com> (raw)
In-Reply-To: <ulkjg1fti.fsf@gnu.org>

> > > I think we should encourage people to write tutorials
> > > for any language, whether it's well supported by Emacs or not.
> >
> > I agree strongly.
>
> Do you read Hebrew?  If not, try to imagine your beloved language
> hopelessly messed up by Emacs, and you will begin to understand why I
> don't want to see such abomination in the Emacs distribution.

Who said anything about it being in the Emacs distribution?

> No way I will agree to something like that.

You also said:

> If someone wants to contribute just the text, we could perhaps
> keep it in admin somewhere

That's what I had in mind: let people think now about translating, but don't
integrate any translations into Emacs until the display can support them. I
thought that was also what Stefan had in mind, but I don't know.

However, I also added a caveat that we should let potential translators know
that their effort might be partly wasted if the tutorial is revisited after
the release.

Stefan spoke not of translating, in fact, but of "writing tutorials", which
I also agree with. That is, I think it would be good for people to think now
about possible improvements to the Emacs tutorial. Recently, people here
looked at another tutorial (with screenshots etc.), which some found useful.
I say, let's get input from all quarters on how the Emacs tutorial might be
improved.

Input should be welcome, both translation and new tutorial ideas. You may
not "agree to something like that", but that's what I meant and what I still
mean.

  reply	other threads:[~2007-02-02 20:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 23:48 Hebrew xlation of Emacs tutorial Yotam Medini יותם מדיני
2007-02-02 12:57 ` David Kastrup
2007-02-02 13:13 ` Eli Zaretskii
2007-02-02 15:25   ` Yotam Medini יותם מדיני
2007-02-02 15:33     ` David Kastrup
2007-02-02 16:16       ` Yotam Medini יותם מדיני
2007-02-02 18:21         ` Eli Zaretskii
2007-02-02 18:19       ` Eli Zaretskii
2007-02-02 22:39         ` David Kastrup
2007-02-03 11:04           ` Eli Zaretskii
2007-02-03 11:11             ` David Kastrup
2007-02-03 11:43               ` Eli Zaretskii
2007-02-03 11:47                 ` David Kastrup
2007-02-03 14:06                   ` Eli Zaretskii
2007-02-02 18:16     ` Eli Zaretskii
2007-02-02 19:07       ` Stefan Monnier
2007-02-02 19:12         ` Drew Adams
2007-02-02 20:10           ` Eli Zaretskii
2007-02-02 20:28             ` Drew Adams [this message]
2007-02-02 20:04         ` Eli Zaretskii
2007-02-03  1:52           ` Stefan Monnier
2007-02-03 11:18             ` Eli Zaretskii
2007-02-03 16:01           ` James Cloos
2007-02-03 16:21             ` David Kastrup
2007-02-03 18:42               ` Eli Zaretskii
2007-02-03 19:12                 ` David Kastrup
2007-02-03 21:01                   ` James Cloos
2007-02-04 19:00                     ` James Cloos
2007-02-05  0:52                       ` Kenichi Handa
2007-02-05 18:37                         ` James Cloos
2007-02-10 11:43                         ` Eli Zaretskii
2007-02-11 14:51                           ` Kenichi Handa
2007-02-03 21:40                   ` Eli Zaretskii
2007-02-05  1:35                   ` Kenichi Handa
2007-02-05 17:51                     ` David Kastrup
2007-02-02 22:12         ` Jason Rumney
2007-02-03 11:19 ` Richard Stallman

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=EIENLHALHGIMHGDOLMIMKEKDCOAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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 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).