unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Kenichi Handa <handa@gnu.org>, emacs-devel@gnu.org
Subject: Re: Face issue -- possible bug
Date: Tue, 17 Jul 2018 23:23:08 +0200	[thread overview]
Message-ID: <87bmb5wo8z.fsf@fastmail.fm> (raw)
In-Reply-To: <83r2k17tyw.fsf@gnu.org>


On Tue, Jul 17 2018, Eli Zaretskii wrote:
> Note how the first glyph of the composition data with the "bad" 
> font
> has zero as its 3rd component, whereas the "good" font has 110 
> there,
> which is the codepoint of 'n'.  Having zero there is not really
> normal, I think.
>
> I downloaded the Libertine O font and tried that on MS-Windows. 
> I
> don't see this problem there with that font.  So based on that, 
> and on
> the fact that another font displays this combination correctly 
> on your
> system, my primary suspect is neither Emacs nor the font, but 
> the
> shaping engine we use to compose characters.  On GNU/Linux we 
> use
> libm17n-flt as the shaping engine, so the first step is to make 
> sure
> you have its latest version installed.  I think the latest 
> version is
> only available in the CVS repository, which you can access 
> through
> Savannah:
>
>    http://savannah.nongnu.org/projects/m17n/
>
> If installing the latest version doesn't help, it might be a bug 
> in
> libm17n-flt, so I'm CC'ing Handa-san who might be able to help 
> fix
> this.

I'm actually having trouble accessing the sources. The invocation

cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/m17n 
co m17n

as described at <http://savannah.nongnu.org/cvs/?group=m17n>

just gives me an empty CVS repository. Substituting `m17n-lib' for 
`m17n' does seem to checkout the sources, but the newest source 
files there are from 2014. (Which is why I said "seem to check out 
the sources", but I have no experience with CVS, so I may be doing 
something silly.)

According to <https://www.nongnu.org/m17n/>, that would correspond 
to version 1.17, released in 2014, which also happens to be the 
version installed on my Linux system (which is based on Ubuntu 
16.04). That www page also lists a version 1.18, from February of 
this year. I can try and install that, if you think it makes 
sense.

(Actually, the package installed on my system is called libm17n, 
not libm17n-flt, not sure if that matters.)

TIA

-- 
Joost Kremers
Life has its moments



  reply	other threads:[~2018-07-17 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 20:49 Face issue -- possible bug Joost Kremers
2018-07-17  2:33 ` Eli Zaretskii
2018-07-17  7:56   ` Joost Kremers
2018-07-17 15:38     ` Eli Zaretskii
2018-07-17 21:23       ` Joost Kremers [this message]
2018-07-18 15:25         ` Eli Zaretskii
2018-08-13 21:53           ` Joost Kremers
2018-08-14  2:29             ` Eli Zaretskii
2018-09-10  8:24               ` 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=87bmb5wo8z.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@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 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).