# [luatex] luatex Digest, Vol 34, Issue 12

Mohamed Bana mohamed at bana.org.uk
Mon Oct 10 13:25:32 CEST 2011

I am having problems unsubscribing to this list.  Could someone please do
it.

I tried using the online interface but that did not work.  Someone please
help.

—Mohamed

On 10 October 2011 11:00, <luatex-request at tug.org> wrote:

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