<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Le 30/10/2011 13:20, George N. White III a écrit :<br>
<span style="white-space: pre;">> On Sun, Oct 30, 2011 at 7:42
AM, Khaled Hosny <a class="moz-txt-link-rfc2396E" href="mailto:khaledhosny@eglug.org"><khaledhosny@eglug.org></a> wrote:<br>
>> Writing an OpenType layout engine is not a simple task,
and you can<br>
>> judge from the many years it toke FOSS community to have
a really good<br>
>> one, HarfBuzz (the name luaotfload is misleading, font
loading is about<br>
>> the easiest part of luaotfload, OpenType implementation
is really what<br>
>> matters.) If it were for me, I'd plug HarfBuzz into
luatex proper and<br>
>> call it a day, but this does not align well with the
"design" principles<br>
>> of luatex so it is unlikely to happen.<br>
><br>
> If plugging harfbuzz into luatex does not require a huge
effort, it could<br>
> serve as bridge from xetex to luatex while a more principled
design<br>
> is being created. Principles are nice, and have benefits over
the long<br>
> haul, but in cases where the design is evolving it really
helps to get<br>
> an implementation into the hands of users and let them point
out the<br>
> areas where work is needed.</span><br>
<br>
As far as I can see, the principles behind LuaTeX are pretty clear;
it<br>
offers tools, not solutions. Sometimes that makes it apparently
slow-witted,<br>
like TeX itself, because it refuses to implement solutions that seem<br>
successful elsewhere. But one shouldn't forget that (Lua)TeX is an<br>
extremely sophisticated typographic system, and that flexibility is
an<br>
integral part of it. Using HarfBuzz would probably offer a simple
solution,<br>
but you'd lose what makes LuaTeX so worthwhile.<br>
<br>
Best,<br>
Paul<br>
<br>
</body>
</html>