all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "fr_ml@t-online.de" <fr_ml@t-online.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "56695@debbugs.gnu.org" <56695@debbugs.gnu.org>
Subject: bug#56695: AW: bug#56695: A new and old font problem with Arabic
Date: Mon, 25 Jul 2022 17:29:23 +0200 (CEST)	[thread overview]
Message-ID: <1658762963915.1797956.84a8985b7fe32b4077cf35452c034178b85b515d@spica.telekom.de> (raw)
In-Reply-To: <838roihoph.fsf@gnu.org>

> This is expected: Emacs caches the results of previous text-shaping.
> You should invoke
> 
>   M-: (clear-composition-cache) RET
> 
> to force Emacs to forget the old text-shaping results.
If I have the positioning problem, this command doesn't solve it.

> > It works, Emacs uses the font correctly.
> > And it seems that the positioning is then much better. The old problem is still there but not so often.
> 
> Does this mean we can close this bug?
It's better but it's strange. And unfortunately  some years ago this problem wasn't there at all. But it's ok. 
We can close it.
Many thanks.





  reply	other threads:[~2022-07-25 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  8:11 bug#56695: A new and old font problem with Arabic fr_ml
2022-07-22 11:08 ` Eli Zaretskii
     [not found]   ` <1658497265479.1589294.1e7fbe71a9c257912af2f6c3a3b45532d616817d@spica.telekom.de>
2022-07-22 14:18     ` Eli Zaretskii
2022-07-22 15:58       ` bug#56695: AW: " fr_ml
2022-07-22 16:21         ` Eli Zaretskii
2022-07-24  7:24           ` bug#56695: AW: " fr_ml
2022-07-24  8:58             ` Eli Zaretskii
2022-07-25 15:29               ` fr_ml [this message]
2022-07-25 16:06                 ` Eli Zaretskii
2022-07-25 20:46                   ` bug#56695: AW: " fr_ml
2022-08-13 21:58                   ` fr_ml
2022-08-14  6:20                     ` Eli Zaretskii
2022-08-14 12:11                       ` bug#56695: AW: " fr_ml

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=1658762963915.1797956.84a8985b7fe32b4077cf35452c034178b85b515d@spica.telekom.de \
    --to=fr_ml@t-online.de \
    --cc=56695@debbugs.gnu.org \
    --cc=eliz@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 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.