From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: emacs hebrew script bidi nikud rendering bugs
Date: Sat, 07 Nov 2015 13:36:16 +0200 [thread overview]
Message-ID: <83vb9eoxcf.fsf@gnu.org> (raw)
In-Reply-To: <87si4iywmd.fsf@mat.ucm.es>
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Sat, 07 Nov 2015 09:41:46 +0000
>
> >>> "Mark" == Mark David <markhd@fastmail.fm> writes:
>
> > I want to report and maybe fix bugs in rendering Hebrew script,
> > particularly with diacritics (nikud). It only partially works in
> > environments I'm using (Ubunutu, Emacs 25.x). (Hebrew without
> > diacritics, used for everyday Hebrew language writing, is evidently
> > functioning well.) Is there a mailing list best suited for that? Is
> > there a separate development team for that kind of thing? Where would
> > I report, say, inability to correctly render a sequence of Hebrew base
> > character and diacritic like this
>
> > Unicode Character 'HEBREW LETTER ALEF' (U+05D0)
>
> > Unicode Character 'HEBREW POINT QAMATS' (U+05B8)
>
> I am not sure what you mean by rendered correctly.
>
> Let A=aleph
> ^=QAMATS
>
> Then for example OpenOffice displays this correctly as
>
> A
> ^
> while Emacs 25 (and 24.5) displays it as
>
> A
> ^
Not here: I see A, as expected.
^
next prev parent reply other threads:[~2015-11-07 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 19:36 emacs hebrew script bidi nikud rendering bugs Mark David
2015-11-06 20:08 ` Eli Zaretskii
2015-11-07 9:41 ` Uwe Brauer
2015-11-07 11:36 ` Eli Zaretskii [this message]
2015-11-07 17:27 ` Uwe Brauer
2015-11-07 18:00 ` Eli Zaretskii
2015-11-07 18:32 ` Uwe Brauer
2015-11-07 18:52 ` Eli Zaretskii
2015-11-08 9:05 ` [SOLVED] (was: emacs hebrew script bidi nikud rendering bugs) Uwe Brauer
2015-11-09 17:52 ` [SOLVED] Benjamin Riefenstahl
2015-11-07 20:20 ` emacs hebrew script bidi nikud rendering bugs Benjamin Riefenstahl
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=83vb9eoxcf.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.