bug#40502: closed (28.0.50; Hangul Jamo conjoining characters are not composed)

[GNU bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:11:56 +0200
with message-id <address@hidden>
and subject line Re: bug#40502: 28.0.50; Hangul Jamo conjoining characters are 
not composed
has caused the debbugs.gnu.org bug report #40502,
regarding 28.0.50; Hangul Jamo conjoining characters are not composed
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
40502: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40502
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 28.0.50; Hangul Jamo conjoining characters are not composed
>
>
>
>
> Date: 
>
> Wed, 08 Apr 2020 11:28:25 +0200
>
>
>
>
> According to Unicode 13 Chapter 18.6, Hangul Jamo characters should be
> composed into the corresponding pre-composed Hangul characters. Iʼm
> not seeing this, e.g
>
> 하 (U+1112 U+1161) should be displayed as 하 (U+D558), but is shown as
> two separate glyphs (all using Apple SD Gothic Neo)
>
> (set-char-table-range composition-function-table
>                       #x1112
>                       (list (vector "..")
>                             0
>                             'compose-gstring-for-graphic))
>
> does not help.
>
> This is:
>
> In GNU Emacs 28.0.50 (build 127, x86_64-apple-darwin18.7.0, NS appkit-1671.60 
> Version 10.14.6 (Build 18G4032))
>  of 2020-04-02 built on rpluim-mac
>
> although I see the same in a Cairo+HarfBuzz build on GNU/Linux.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#40502: 28.0.50; Hangul Jamo conjoining characters are not composed
>
>
>
>
> Date: 
>
> Wed, 08 Apr 2020 12:11:56 +0200
>
>
>
>
> >>>>> On Wed, 08 Apr 2020 12:55:19 +0300, Eli Zaretskii <address@hidden> said:
>
>     >> From: Robert Pluim <address@hidden>
>     >> Date: Wed, 08 Apr 2020 11:28:25 +0200
>     >> 
>     >> According to Unicode 13 Chapter 18.6, Hangul Jamo characters should be
>     >> composed into the corresponding pre-composed Hangul characters. Iʼm
>     >> not seeing this, e.g
>     >> 
>     >> 하 (U+1112 U+1161) should be displayed as 하 (U+D558), but is shown as
>     >> two separate glyphs (all using Apple SD Gothic Neo)
>
>     Eli> I hope I've just fixed that on the master branch, please take a look.
>
> Yes, on both macOS and GNU/Linux, including the three character
> variant (I tested with U+1112 U+1161 U+11AB).
>
>     >> (set-char-table-range composition-function-table
>     >> #x1112
>     >> (list (vector "..")
>     >> 0
>     >> 'compose-gstring-for-graphic))
>     >> 
>     >> does not help.
>
>     Eli> The call is incorrect: 'vector' should include both 0 and the function
>     Eli> symbol.
>
> Yes. I misread the docstring of composition-function-table rather than
> copying the correct call I had sitting in a buffer already.
>
> Closing.
>
> Robert
>
>
> --- End Message ---