From: "Yotam Medini יותם מדיני" <yotam.medini@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Hebrew xlation of Emacs tutorial
Date: Fri, 2 Feb 2007 17:25:51 +0200 [thread overview]
Message-ID: <20070202172551.3a25b37f.yotam.medini@gmail.com> (raw)
In-Reply-To: <ur6t83doz.fsf@gnu.org>
On Fri, 02 Feb 2007 15:13:16 +0200
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 2 Feb 2007 01:48:16 +0200
> > From: Yotam Medini
> >
> > Should someone would volunteer to make a Hebrew translation
> > of the Emacs tutorial, how can that be coordinated?
>
> I don't see any sense in having a Hebrew translation of the tutorial
> as long as Emacs cannot display Hebrew text in a reasonably correct
> way.
While Emacs cannot display Hebrew text right, the TUTORIAL.he can
be converted to visual order.
I understand that Emacs tutorial in Hebrew will be much more important
once full Bidi support will be released.
Still, there is small young Linux community, that can use Emacs
to edit scripts and configuration files in Gnu/Linux.
I teach a small class of kids Python programming on Gnu/Linux.
The kids' English is poor. They understand enough, so they
can type simple code - using English letters of course.
As part of the course, I teach them basic Emacs usage. I wish I could
refer them to a tutorial. So my thinking of the tutorial
translation, is to explain in Hebrew how to do English text editing.
May be there is also a chicken & egg situation here. The very fact
that there are too few young Emacs users who understand Hebrew,
is the reason that there are not enough people who can bring
Bidi support in Emacs to life.
next prev parent reply other threads:[~2007-02-02 15:25 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 יותם מדיני [this message]
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
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=20070202172551.3a25b37f.yotam.medini@gmail.com \
--to=yotam.medini@gmail.com \
--cc=eliz@gnu.org \
--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).