I am having problems unsubscribing to this list. Could someone please do it.<div><br></div><div>I tried using the online interface but that did not work. Someone please help.</div><div><br><div> —Mohamed<br>
<br><br><div class="gmail_quote">On 10 October 2011 11:00, <span dir="ltr"><<a href="mailto:luatex-request@tug.org">luatex-request@tug.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Send luatex mailing list submissions to<br>
<a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://tug.org/mailman/listinfo/luatex" target="_blank">http://tug.org/mailman/listinfo/luatex</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:luatex-request@tug.org">luatex-request@tug.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:luatex-owner@tug.org">luatex-owner@tug.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of luatex digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: ligatures with luaotfload (Javier M?gica de Rivera)<br>
2. Re: ligatures with luaotfload (Khaled Hosny)<br>
3. Re: Building LuaTeX (again). (Taco Hoekwater)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 9 Oct 2011 12:58:37 +0200<br>
From: Javier M?gica de Rivera <<a href="mailto:javieraritz.ribadeo@gmail.com">javieraritz.ribadeo@gmail.com</a>><br>
To: <a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
Subject: Re: [luatex] ligatures with luaotfload<br>
Message-ID:<br>
<<a href="mailto:CABCShTg3Oe25L1bP8V-g_FqW1D1T%2BOMcPQBKoEUM3Bib4vXEbg@mail.gmail.com">CABCShTg3Oe25L1bP8V-g_FqW1D1T+OMcPQBKoEUM3Bib4vXEbg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
> you have to explicitly set kern and ligatures: [...] +liga;+kern<br>
<br>
> if you don't select a script no feature will be enabled by default<br>
<br>
Thank you two, both of<br>
<br>
\def\otffont#1=#2 at{\font#1={#2: +kern;+liga} at}<br>
\def\otffont#1=#2 at{\font#1={#2: script=latn} at}<br>
<br>
work.<br>
<br>
Now that I know the answer I have looked again into the luaoftload<br>
manual and the OpenType Feature File Specification, and see that all<br>
the nedeed pieces are present, but they appear scatered here and<br>
there. You don't need to know anything about .tfm fonts in order to<br>
use them. I would expect the same for otf fonts as long as you don't<br>
ask for complicate operations. That is, I would expect<br>
<br>
\input luaotfload.sty<br>
\font\tenrm=LMRoman10-Regular<br>
<br>
to be the same as<br>
<br>
\font\tenrm=ec-lmr10<br>
<br>
<br>
I _had_ read:<br>
<br>
"script<br>
OpenType script string, default value is dflt. Some fonts don?t assign<br>
features to<br>
the dflt script, in which case the script need to be set explicitly."<br>
<br>
but since Latin Modern fonts are designed just for the Latin script I<br>
could not imagine that keeping the default would miss features.<br>
And it is true that at the section of "Troubleshooting" there appears<br>
the example<br>
<br>
\font\myfont = MyFont.otf:script=latn;+liga;<br>
<br>
but here the key words latn and liga just happen to appear. That is,<br>
if you want kerning you still have to find the appropriate word for<br>
that somewhere else, as well as if you want some other script. And<br>
after a good deal of browsing through the Internet to find the right<br>
answer (the name for the kerning and ligature features) I had simply<br>
forgotten about this last example, something likely to happen if you<br>
need to put ten different pieces of information together in order to<br>
make something work.<br>
<br>
To summarize, in my opinion<br>
<br>
a) The package should try hard to make its default behavior what a<br>
user would want when loading an OpenType font.<br>
<br>
and<br>
<br>
b) It should provide a list of script names when it describes the<br>
keyword script, and a list of feature names when it mentions that font<br>
features are enabled/disabled "in the form of +feat/-feat" (there is<br>
not a single example).<br>
<br>
The solution for point a) may just be to always activate kerning,<br>
ligatures and final or other alternatives shapes for glyphs (is this<br>
what is called contextual ligatures?)<br>
<br>
<br>
Finally, Khaled, thank you very much for the package! I had asked some<br>
two or three years ago how I could use an OpenType font in Luatex and<br>
the answer was essentially "program it yourself"<br>
<br>
Regards<br>
Javier A. M?gica<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 10 Oct 2011 01:56:15 +0200<br>
From: Khaled Hosny <<a href="mailto:khaledhosny@eglug.org">khaledhosny@eglug.org</a>><br>
To: "General discussion of LuaTeX." <<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Subject: Re: [luatex] ligatures with luaotfload<br>
Message-ID: <20111009235615.GA13725@khaled-laptop><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On Sun, Oct 09, 2011 at 12:58:37PM +0200, Javier M?gica de Rivera wrote:<br>
> > you have to explicitly set kern and ligatures: [...] +liga;+kern<br>
><br>
> > if you don't select a script no feature will be enabled by default<br>
><br>
> Thank you two, both of<br>
><br>
> \def\otffont#1=#2 at{\font#1={#2: +kern;+liga} at}<br>
> \def\otffont#1=#2 at{\font#1={#2: script=latn} at}<br>
><br>
> work.<br>
><br>
> Now that I know the answer I have looked again into the luaoftload<br>
> manual and the OpenType Feature File Specification, and see that all<br>
> the nedeed pieces are present, but they appear scatered here and<br>
> there. You don't need to know anything about .tfm fonts in order to<br>
> use them. I would expect the same for otf fonts as long as you don't<br>
> ask for complicate operations. That is, I would expect<br>
><br>
> \input luaotfload.sty<br>
> \font\tenrm=LMRoman10-Regular<br>
><br>
> to be the same as<br>
><br>
> \font\tenrm=ec-lmr10<br>
><br>
><br>
> I _had_ read:<br>
><br>
> "script<br>
> OpenType script string, default value is dflt. Some fonts don?t assign<br>
> features to<br>
> the dflt script, in which case the script need to be set explicitly."<br>
><br>
> but since Latin Modern fonts are designed just for the Latin script I<br>
> could not imagine that keeping the default would miss features.<br>
> And it is true that at the section of "Troubleshooting" there appears<br>
> the example<br>
><br>
> \font\myfont = MyFont.otf:script=latn;+liga;<br>
><br>
> but here the key words latn and liga just happen to appear. That is,<br>
> if you want kerning you still have to find the appropriate word for<br>
> that somewhere else, as well as if you want some other script. And<br>
> after a good deal of browsing through the Internet to find the right<br>
> answer (the name for the kerning and ligature features) I had simply<br>
> forgotten about this last example, something likely to happen if you<br>
> need to put ten different pieces of information together in order to<br>
> make something work.<br>
><br>
> To summarize, in my opinion<br>
><br>
> a) The package should try hard to make its default behavior what a<br>
> user would want when loading an OpenType font.<br>
<br>
OpenType is a complicated beast and will never be as simple as old TFM<br>
fonts (feature activation wise, else I see nothing simple about TFM<br>
fonts; you had to do a good deal of complicated setup to merely install<br>
them). However, \font\tenrm=LMRoman10-Regular was supposed to such work,<br>
but the way it was actually implemented requires selecting a script for<br>
things to work. This have been fixed in the unstable branch, so you may<br>
want to use that until there is a release.<br>
<br>
> and<br>
><br>
> b) It should provide a list of script names when it describes the<br>
> keyword script, and a list of feature names when it mentions that font<br>
> features are enabled/disabled "in the form of +feat/-feat" (there is<br>
> not a single example).<br>
<br>
I'm not going to duplicate OpenType layout tag[1] registry in the<br>
package documentation, sorry. However, improvements to make the<br>
documentation more clear to people not familiar with OpenType are very<br>
welcomed.<br>
<br>
> The solution for point a) may just be to always activate kerning,<br>
> ligatures and final or other alternatives shapes for glyphs (is this<br>
> what is called contextual ligatures?)<br>
<br>
Things are more complicated than that since different scripts have<br>
different set of features that need to be activated by default, this why<br>
the old code required setting a script, now if no script is specified I<br>
just assume it is DFLT and activates the respective set of feature<br>
(which is the same as that of Latin script).<br>
<br>
> Finally, Khaled, thank you very much for the package! I had asked some<br>
> two or three years ago how I could use an OpenType font in Luatex and<br>
> the answer was essentially "program it yourself"<br>
<br>
Thanks all goes to Hans who is doing all the real work, Elie and others<br>
who wrote the plain tex/latex package, I'm merely glueing things<br>
together.<br>
<br>
Regards,<br>
Khaled<br>
<br>
[1] <a href="http://www.microsoft.com/typography/otspec/ttoreg.htm" target="_blank">http://www.microsoft.com/typography/otspec/ttoreg.htm</a><br>
<br>
--<br>
Khaled Hosny<br>
Egyptian<br>
Arab<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 10 Oct 2011 10:05:32 +0200<br>
From: Taco Hoekwater <<a href="mailto:taco@elvenkind.com">taco@elvenkind.com</a>><br>
To: "General discussion of LuaTeX." <<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Subject: Re: [luatex] Building LuaTeX (again).<br>
Message-ID: <<a href="mailto:4E92A74C.4050203@elvenkind.com">4E92A74C.4050203@elvenkind.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
<br>
Hi,<br>
<br>
On 10/04/2011 11:10 AM, Keith J. Schultz wrote:<br>
> Hi Hartmut,<br>
><br>
> I am not know the system you are using, but I can other you some thoughts.<br>
<br>
Same failure during crosscompile here<br>
<br>
> 2) the is not finding the reference for EnumFontsA@16<br>
<br>
EnumFonts() is in gdi32.dll, which is not linked in luatex. That bit of<br>
code in GlobalParams.cc should have been preprocessed out (as it was in<br>
earlier versions, I think, thanks to PDF_PARSER_ONLY). Hartmut, is that<br>
enough information for you to fix it?<br>
<br>
Best wishes,<br>
Taco<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
luatex mailing list<br>
<a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/luatex" target="_blank">http://tug.org/mailman/listinfo/luatex</a><br>
<br>
<br>
End of luatex Digest, Vol 34, Issue 12<br>
**************************************<br>
</blockquote></div><br></div></div>