all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 12273@debbugs.gnu.org
Subject: bug#12273: 24.2.50; complex text layout
Date: Mon, 27 Aug 2012 16:54:17 +0900	[thread overview]
Message-ID: <87r4qshis6.fsf@gnu.org> (raw)
In-Reply-To: <955FEE1A-949C-4F36-A66A-9E1777AEB9B5@Freenet.DE> (message from Peter Dyballa on Sat, 25 Aug 2012 00:41:03 +0200)

In article <955FEE1A-949C-4F36-A66A-9E1777AEB9B5@Freenet.DE>, Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> So the Fink variant uses libm17n and a modern libotf with
> OTF_get_variation_glyphs and the MacPorts variant has a
> bit older software. I launched both with -Q and them
> display the HELLO file and edited it to contain only
> complex scripts.

Thank you for the testing.

> I made a screenshot of both Emacsen side by side and made
> from the Fink variant's display a transparent copy with
> text colour in red and tried to position that over the
> same part of the edited HELLO buffer in the other Emacs.

Could you attach an image file of MacPorts version without
overwrapping with Fink verison?

> A few differences are visible. I cannot judge whether
> these differences are improvements, except for one: the
> Gujarati word in () seems to be in the m17n enabled Fink
> variant not OK – there is a low "accent" moved to the
> opening parenthesis.

Please show me the font names used for these scripts (which
are, I think, not-correctly rendered):
  Arabic, Burmese, Gularati, Kannada, Sinhara, 

---
Kenichi Handa
handa@gnu.org





  reply	other threads:[~2012-08-27  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 22:41 bug#12273: 24.2.50; complex text layout Peter Dyballa
2012-08-27  7:54 ` Kenichi Handa [this message]
2012-08-27  8:40   ` Peter Dyballa
2021-07-15 20:37 ` Lars Ingebrigtsen
2021-07-15 22:37   ` Peter Dyballa
2021-07-15 22:41     ` Lars Ingebrigtsen

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=87r4qshis6.fsf@gnu.org \
    --to=handa@gnu.org \
    --cc=12273@debbugs.gnu.org \
    --cc=Peter_Dyballa@Freenet.DE \
    /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.