unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Kangas <stefan@marxist.se>
Cc: 34035@debbugs.gnu.org, Stephen Berman <stephen.berman@gmx.net>,
	Peter <craven@gmx.net>
Subject: bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly
Date: Wed, 19 Aug 2020 11:48:20 +0100	[thread overview]
Message-ID: <87tuwyx66j.fsf@tcd.ie> (raw)
In-Reply-To: <CADwFkm=bDn=Q6inXxR5cfmQsoktxQ7LbDOts7HK2TgMS5NVi6w@mail.gmail.com> (Stefan Kangas's message of "Wed, 19 Aug 2020 09:49:37 +0000")

Stefan Kangas <stefan@marxist.se> writes:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> This seems to be a font issue independent of Emacs, e.g., I also see the
>> same thing in LibreOffice Writer: with DejaVu Sans the kasrah is
>> correctly displayed between the shadda and the seen, and with DejaVu
>> Sans Mono, the kasrah is incorrectly displayed below the seen.
>
> I can confirm that the font Emacs uses to correctly display this for me
> in "emacs -Q" is:
>
> ftcrhb:-PfEd-DejaVu Sans-normal-normal-normal-*-48-*-*-*-*-0-iso10646-1
>
> I also tried LibreOffice Writer, fonts "FreeSans" and "DejaVu Sans Mono"
> seem to be broken, while "DejaVu Sans" displays it correctly.
>
> Does that mean that this is a bug/missing feature in the fonts, and not
> in Emacs?

Sounds like it, though I'm curious whether Eli's concerns in
https://debbugs.gnu.org/34035#35 still apply.

Thanks,

-- 
Basil





  reply	other threads:[~2020-08-19 10:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 17:20 bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly Peter
2019-01-10 18:55 ` Eli Zaretskii
2019-01-10 19:45   ` Peter
2019-01-10 19:52     ` Eli Zaretskii
2019-01-10 20:05       ` Peter
2019-01-11  9:24   ` Stephen Berman
2019-01-11  9:30     ` Eli Zaretskii
2019-01-11  9:47       ` Stephen Berman
2019-01-11 10:34         ` Eli Zaretskii
2019-01-11 10:54           ` Stephen Berman
2019-01-11 13:30             ` Eli Zaretskii
2019-01-11 16:14               ` Stephen Berman
2020-08-18 18:11   ` Stefan Kangas
2020-08-19  8:01     ` Basil L. Contovounesios
2020-08-19  9:07       ` Stephen Berman
2020-08-19  9:49         ` Stefan Kangas
2020-08-19 10:48           ` Basil L. Contovounesios [this message]
2020-08-19 14:54             ` Eli Zaretskii
2020-08-19 16:20               ` Basil L. Contovounesios
2020-08-19 16:58                 ` Eli Zaretskii
2020-09-18 10:02             ` Stefan Kangas
2020-08-19 14:32       ` Eli Zaretskii
2020-08-19 16:18         ` Basil L. Contovounesios
2020-08-19 17:11           ` Eli Zaretskii
2020-08-20  0:59             ` Basil L. Contovounesios
2020-08-23  6:41             ` James Cloos
2020-08-23  7:15               ` Eli Zaretskii
2020-08-23  9:26                 ` Stephen Berman
2020-08-23 11:36                   ` Eli Zaretskii

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=87tuwyx66j.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=34035@debbugs.gnu.org \
    --cc=craven@gmx.net \
    --cc=stefan@marxist.se \
    --cc=stephen.berman@gmx.net \
    /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).