Re: m17n, otf0 and configuring on Kubuntu

[Kenichi Handa <handa@m17n.org>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 1297 bytes --]

In article <47C525C7.5030709@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:

> Jan Dj^[$(D+#^[(Brv wrote:
> > Does it make sense to add something about this in the summary 
> > configure puts out at the end?  Like
> >
> >   Complex Text Layout     yes/no
> >   OpenType fonts          yes/no
> >
> > I could to that.  Is it a one to one mapping, i.e. libotf => OpenType 
> > fonts and m17n => CTL or are both required?

> Does libotf enable the use of OpenType fonts, or does it just enable the 
> use of advanced features available in them?

The latter, even without m17n-lib and libotf, xft and ftx
font backends can use OpenType fonts just as TrueType fonts.

So, on GNU/Linux, if both m17n-lib and libotf are available,
   Complex Text Layout     yes
Otherwise
   Complex Text Layout     no

But, this message may be confusing.
> >   OpenType fonts          yes/no

Even the pre-unicode emacs can use OpenType fonts as X core
fonts because the recent X server supports TrueType fonts
(and most OpenType fonts are just TrueType fonts with some
additional tables).

So, perhaps the more correct message is:

   Local system font       yes/no
or
   Font Antialiasing       yes/no

On GNU/Linux, it's yes iff one of xft and ftx font backends
is available.

---
Kenichi Handa
handa@ni.aist.go.jp