Re: master bf0aeaa0d7a: Re-enable displaying `han' characters on Android

[Po Lu <luangruo@yahoo.com>]

Eli Zaretskii <eliz@gnu.org> writes:

> But users can add a font spec for 'han' to the fontset, cannot they?
> And if they do, then the representative characters _are_ important,
> aren't they?  So I don't think we should remove those characters.

Such an action would be pointless, as the fontset would not match any
CJK font actually in existence, and it would break the Android build to
boot.  If anyone seriously considers non-existent characters important
enough to construct a font spec that matches them, he can easily amend
script-representative-chars for himself or define another script.  If
these pages are opened, for example:

  https://www.compart.com/en/unicode/U+20000
  https://www.compart.com/en/unicode/U+2a700
  https://www.compart.com/en/unicode/U+2b740
  https://www.compart.com/en/unicode/U+2b820
  https://www.compart.com/en/unicode/U+2ceb0

in Mozilla (not to mention Emacs) on my GNU/Linux system or on Android,
tofu is displayed, and there can hardly be said to exist an OS system
that is better internationalized out of the box than is Android.  The
remaining characters:

  https://www.compart.com/en/unicode/U+2f804
  https://www.compart.com/en/unicode/U+1f210

are displayed correctly, but are barely attested or expected to be
present by CJK users in practice, and U+1F210 is arguably rather a
symbol than a proper character.