all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: some progress
Date: Fri, 21 Jun 2013 17:35:31 +0300	[thread overview]
Message-ID: <83obazmszw.fsf@gnu.org> (raw)
In-Reply-To: <8738sbh87c.fsf@gilgamesch.quim.ucm.es>

> From: Uwe Brauer <oub@mat.ucm.es>
> Cc: emacs-devel@gnu.org
> Date: Fri, 21 Jun 2013 16:03:35 +0200
> 
>    > Does it help to type "C-x C-+"?
> Only  a little bit, the ascii chars are getting really bigger the hebrew
> ones only a slightly bit. Do I need additional fonts (I am on (K)ubuntu 10.04)???

You need more/better fonts.

> However the input methods which are offered do no include hebrew
> phonetic, by which I mean 
> 
> 
>  "aleph" is on "a" etc.

Try hebrew-biblical-sil, it comes close.

And "C-h C-\" will display a keyboard schematics that will tell you
which key inserts which character.

> That is why I use the input via KDE and that is why I need to turn on
> R2L manually.

??? I don't understand: as long as Emacs gets the correct characters,
no matter how they were created, everything else, including paragraph
direction, should "just work".

> So maybe the best solution would be to provide also hebrew-phonetical[1]
> Because I am a little worried how KDE keyboard and nested text may work
> together.
> 
> I can give it a try to have also a hebrew-phonetical. Which are the
> files to be modified?

leim/quail/hebrew.el.

> [1]  (BTW what is hebrew-lyx suppose to be? KDE also offers it and I cannot
> see any difference to standard hebrew, ok I don't have a hebrew keyboard
> here, so maybe . /  etc are different.

I expect hebrew-lyx in Emacs to be the same as what KDE offers.  But I
never checked.



  reply	other threads:[~2013-06-21 14:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 11:16 bidi support? (Hebrew) Uwe Brauer
2013-06-21 13:27 ` some progress (was: bidi support? (Hebrew)) Uwe Brauer
2013-06-21 13:50   ` Eli Zaretskii
2013-06-21 14:03     ` some progress Uwe Brauer
2013-06-21 14:35       ` Eli Zaretskii [this message]
2013-06-21 14:53         ` Uwe Brauer
2013-06-21 15:05           ` Eli Zaretskii
2013-06-21 16:04             ` Uwe Brauer
2013-06-21 18:09               ` Eli Zaretskii
2013-06-21 17:45             ` Uwe Brauer
2013-06-21 18:12               ` Eli Zaretskii
2013-06-21 15:02         ` Uwe Brauer
2013-06-21 16:42         ` Uwe Brauer
2013-06-21 18:10           ` Eli Zaretskii
2013-06-21 19:46             ` Uwe Brauer
2013-06-22  9:53               ` Eli Zaretskii
2013-06-22 16:25                 ` Uwe Brauer
2013-06-22 17:09                 ` a strict visual cursor in r2l and l2r buffers (was: some progress) Uwe Brauer
2013-06-22 22:17                   ` Eli Zaretskii
2013-06-23 16:22                     ` a strict visual cursor in r2l and l2r buffers Uwe Brauer
2013-06-23 16:47                       ` Eli Zaretskii
2013-06-23 19:43                         ` Uwe Brauer
2013-06-24 16:21                           ` Eli Zaretskii
2013-06-29 13:50                           ` Eli Zaretskii
2013-06-29 15:17                             ` Stefan Monnier
2013-06-29 15:26                               ` Eli Zaretskii
2013-06-29 16:10                             ` Uwe Brauer
2013-06-29 17:01                               ` Eli Zaretskii
2013-06-29 17:04                                 ` Uwe Brauer
2013-06-29 18:09                                   ` Eli Zaretskii
2013-06-29 19:33                                     ` Uwe Brauer
2013-06-29 19:38                                       ` Eli Zaretskii
2013-06-21 13:39 ` bidi support? (Hebrew) Eli Zaretskii
2013-06-21 15:01 ` Stefan Monnier
2013-06-21 16:09 ` Glenn Morris
  -- strict thread matches above, loose matches on Subject: below --
2016-06-16 16:09 tag search seems not to work Uwe Brauer
2016-06-16 16:34 ` Some progress (was: tag search seems not to work.) Uwe Brauer
2016-06-17  7:37   ` Some progress Marco Wahl
2016-06-17  8:47     ` Uwe Brauer
2016-06-17 15:37       ` Marco Wahl

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=83obazmszw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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.