Re: Build problem

[<tim...@en...>]

Ethan A Merritt wrote:
> On Sunday 09 July 2006 01:11 pm, Timoth=C3=A9e Lecomte wrote:
>  =20
>>> The file /usr/local/etc/pango/pango.modules actually exists, but is
>>> empty apart from comments.
>>>      =20
>> Have you tried to run 'pango-querymodules' ? It may tell you why it di=
d=20
>> not find the so-called modules.
>>    =20
>
> So now I'm curious.=20
> What, exactly, is this modules list supposed to tell us?
>
> The list on my machine looks very much like the one on yours.
> The curious thing is that Japanese/Chinese character support is
> listed nowhere in it. Why is this curious? Because my machine is in fac=
t
> configured for Japanese, and the Chinese characters are rendered nicely
> in wxWidgets.  So at the least it seems the module list is an
> incomplete description of the actual capabilities.
>  =20
> Furthermore, to the extent that these various character sets are all
> implemented via UTF-8,  why would one need separate modules anyhow?
>  =20
First, it can be either in modules or builtin (which *may* explain why=20
Juergen has an empty file). And it is probably possible to configure=20
that when you compile Pango, for example by removing this modules for an=20
embedded platform.

Then, Pango and text rendering in general is not only about drawing=20
individual characters. It is about glyphs, layout, typography and I=20
should maybe add calligraphy. And this goes very language-specific. Arab=20
for example needs the glyphs to be joint together, and the same=20
character at the end or in the middle of a word would be drawn as a=20
different glyph. I guess Pango uses modules to handle these=20
particularities. Maybe Chinese and Japanese don't need those special=20
modules, because the typography is closer to occidental languages (one=20
character in utf8=3D one glyph in the output, always the same ?).

Best regards,

Timoth=C3=A9e