Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
2012/9/9 François Patte : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Le 09/09/2012 19:04, Steve White a écrit : >> François, >> >> On my standard-distribution Ubuntu system, it's 'FakeSlant' rather >> than 'AutoFakeSlant'. >> >> With that change to your file, I get the attached. Is this what you >> intended? > > No, "AutoFakeSlant" comes from the cut and paste I have made from an > existing file. What I wanted to say is that I don't understand why > Zdének says that some ligatures are missing: kta, pta > These are missing from FreeSans. The font contains the forms used in modern Hindi, not the Sanskrit ones. > Difference between FakeSlant and AutoFakeSlant seems to be (this is not > so much documented): > > FakeSlant the whole text is slanted > > AutoFakeSlant: slanted text comes with the latex commands \textit{...} > or {\itshape ...} > > Curiously, if you use FakeSlant, the whole text is slanted and there are > question marks for any text you put in \textit{} > > Regards > - -- > François Patte > UFR de mathématiques et informatique > Laboratoire MAP5 --- UMR CNRS 8145 > Université Paris Descartes > 45, rue des Saints Pères > F-75270 Paris Cedex 06 > Tél. +33 (0)1 8394 5849 > http://www.math-info.univ-paris5.fr/~patte > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAlBM0qsACgkQdE6C2dhV2JV0KACfWvUl0csYCym6MQNGKYFl1ZSP > 3qMAn1iCS+4h6cSKS9FoYWArM898mK0a > =CD4d > -END PGP SIGNATURE- > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
2012/9/9 Steve White : > François, > > On my standard-distribution Ubuntu system, it's 'FakeSlant' rather > than 'AutoFakeSlant'. > Maybe Ubuntu contains an older version of the fontspec package. Now FakeSlant makes the geometrically slanted version only if it does not exist, AutoFakeSlant makes it always. Since FreeSerif italic exists, FakeSlant will be ignored and italic Devanagari will be missing. > With that change to your file, I get the attached. Is this what you intended? > > I don't know what the warning messages mean. > I have the same warning messages but they seem to be (almost) harmless. The only problem is that I cannot copy&paste the text from PDF to a text editor. Search will probably not work either. > Cheers! > > On Sun, Sep 9, 2012 at 12:29 PM, François Patte > wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Le 09/09/2012 11:09, Zdenek Wagner a écrit : >>> 2012/9/9 Steve White : >> >>> >>> Hindi support is complete, I have verified it on several Hindi texts, >>> displayed all conjuncts separately and since it was released used in >>> several other Hindi texts. I have just tried to reprocess Neal's >>> sample with FreeSans and indeed ligatures are missing, kta, pta, dga >>> and others. >> >> I cannot see what is wrong with these ligatures >> >> I get a warning while compiling: >> >> ** WARNING ** Unable to read OpenType/TrueType Unicode cmap table. >> ** WARNING ** Failed to load ToUnicode CMap for font "FreeSerif" >> >> Best regards. >> >> - -- >> François Patte >> UFR de mathématiques et informatique >> Laboratoire MAP5 --- UMR CNRS 8145 >> Université Paris Descartes >> 45, rue des Saints P?res >> F-75270 Paris Cedex 06 >> Tél. +33 (0)1 8394 5849 >> http://www.math-info.univ-paris5.fr/~patte >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.11 (GNU/Linux) >> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ >> >> iEYEARECAAYFAlBMb3MACgkQdE6C2dhV2JXrvACeP6xbJncuW1MjaDCrXC5o9vJG >> DLMAoNGmDUP0KLcVrtFENoSeRyzKQEHA >> =k+EI >> -END PGP SIGNATURE- >> >> >> >> -- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex >> > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
François, On Sun, Sep 9, 2012 at 7:32 PM, François Patte wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Le 09/09/2012 19:04, Steve White a écrit : >> François, >> >> On my standard-distribution Ubuntu system, it's 'FakeSlant' rather >> than 'AutoFakeSlant'. >> >> With that change to your file, I get the attached. Is this what you >> intended? > > No, "AutoFakeSlant" comes from the cut and paste I have made from an > existing file. What I wanted to say is that I don't understand why > Zdének says that some ligatures are missing: kta, pta > Oh. I think he was referring to FreeSans, not FreeSerif. And he's right -- I had added some of those letters earlier this year, but never finished the job. > Difference between FakeSlant and AutoFakeSlant seems to be (this is not > so much documented): > > FakeSlant the whole text is slanted > I don't have AutoFakeSlant... > AutoFakeSlant: slanted text comes with the latex commands \textit{...} > or {\itshape ...} > > Curiously, if you use FakeSlant, the whole text is slanted and there are > question marks for any text you put in \textit{} > I think there should just be a \slant function, which simply applys a skew operator to everything in it. This would be fine for most purposes. Why call it "fake"? It would be a fake italic, but not a fake *slant*. Cheers! -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 09/09/2012 19:04, Steve White a écrit : > François, > > On my standard-distribution Ubuntu system, it's 'FakeSlant' rather > than 'AutoFakeSlant'. > > With that change to your file, I get the attached. Is this what you > intended? No, "AutoFakeSlant" comes from the cut and paste I have made from an existing file. What I wanted to say is that I don't understand why Zdének says that some ligatures are missing: kta, pta Difference between FakeSlant and AutoFakeSlant seems to be (this is not so much documented): FakeSlant the whole text is slanted AutoFakeSlant: slanted text comes with the latex commands \textit{...} or {\itshape ...} Curiously, if you use FakeSlant, the whole text is slanted and there are question marks for any text you put in \textit{} Regards - -- François Patte UFR de mathématiques et informatique Laboratoire MAP5 --- UMR CNRS 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAlBM0qsACgkQdE6C2dhV2JV0KACfWvUl0csYCym6MQNGKYFl1ZSP 3qMAn1iCS+4h6cSKS9FoYWArM898mK0a =CD4d -END PGP SIGNATURE- -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
François, On my standard-distribution Ubuntu system, it's 'FakeSlant' rather than 'AutoFakeSlant'. With that change to your file, I get the attached. Is this what you intended? I don't know what the warning messages mean. Cheers! On Sun, Sep 9, 2012 at 12:29 PM, François Patte wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Le 09/09/2012 11:09, Zdenek Wagner a écrit : >> 2012/9/9 Steve White : > >> >> Hindi support is complete, I have verified it on several Hindi texts, >> displayed all conjuncts separately and since it was released used in >> several other Hindi texts. I have just tried to reprocess Neal's >> sample with FreeSans and indeed ligatures are missing, kta, pta, dga >> and others. > > I cannot see what is wrong with these ligatures > > I get a warning while compiling: > > ** WARNING ** Unable to read OpenType/TrueType Unicode cmap table. > ** WARNING ** Failed to load ToUnicode CMap for font "FreeSerif" > > Best regards. > > - -- > François Patte > UFR de mathématiques et informatique > Laboratoire MAP5 --- UMR CNRS 8145 > Université Paris Descartes > 45, rue des Saints P?res > F-75270 Paris Cedex 06 > Tél. +33 (0)1 8394 5849 > http://www.math-info.univ-paris5.fr/~patte > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAlBMb3MACgkQdE6C2dhV2JXrvACeP6xbJncuW1MjaDCrXC5o9vJG > DLMAoNGmDUP0KLcVrtFENoSeRyzKQEHA > =k+EI > -END PGP SIGNATURE- > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > test-freeserif.pdf Description: Adobe PDF document -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 09/09/2012 11:09, Zdenek Wagner a écrit : > 2012/9/9 Steve White : > > Hindi support is complete, I have verified it on several Hindi texts, > displayed all conjuncts separately and since it was released used in > several other Hindi texts. I have just tried to reprocess Neal's > sample with FreeSans and indeed ligatures are missing, kta, pta, dga > and others. I cannot see what is wrong with these ligatures I get a warning while compiling: ** WARNING ** Unable to read OpenType/TrueType Unicode cmap table. ** WARNING ** Failed to load ToUnicode CMap for font "FreeSerif" Best regards. - -- François Patte UFR de mathématiques et informatique Laboratoire MAP5 --- UMR CNRS 8145 Université Paris Descartes 45, rue des Saints P?res F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAlBMb3MACgkQdE6C2dhV2JXrvACeP6xbJncuW1MjaDCrXC5o9vJG DLMAoNGmDUP0KLcVrtFENoSeRyzKQEHA =k+EI -END PGP SIGNATURE- test-freeserif.pdf Description: Adobe PDF document test-freeserif.tex Description: TeX document -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
2012/9/9 Steve White : > Hi Zdenek, > > I'm glad you like the looks of Sanskrit in FreeSerif! > And I like the looks of Hindi in both FreeSans and FreeSerif. As a matter of fact, I use them regularly for Hindi texts and I made them as default sans and serif fonts in my web browsers. My teacher of Hindi likes them too but I will have to help her installing them, her computer skill are not so good. > Regarding Sanskrit in FreeSans: You're right, it is incomplete. I > now remember, had started implementing Sanskrit there, but was > interrupted. I hope to push that effort forward in the next release. > > I also see one or two glitches regarding mark placement in FreeSerif. > I'll work with you guys off-line on those. > > Thanks for your support! > > On Sun, Sep 9, 2012 at 11:09 AM, Zdenek Wagner > wrote: >> 2012/9/9 Steve White : >>> I finally got Neal's examples working, too. (The problem was, I had >>> altered the header tex file he provided, so that it would run with my >>> set of fonts, but had unwittingly also cut out one instance of >>> RomDev). The process is: obtain the RomDev.map file, compile it with >>> 'teckit_compile -u RomDev.map', place the resulting RomDev.tec file in >>> the same directory as the .tex files. The xelatex the main tex file. >>> >>> The result is pretty to my eyes; the conjuncts are working, as near as >>> I can tell. >>> >>> Concerning Zdenek's comments: >>> >>> The Devanagari feature lookup tables in FreeSerif are arranged so that >>> modern forms are default, and the more extensive Sanskrit forms must >>> be turned on by explicitly specifying Sanskrit as the text language. >>> (It is safest always to specify the language. Unfortunately, xelatex >>> complains very confusingly if no tables are explicitly turned on by >>> the specified language.) >>> >>> FreeSans is indeed derived from Gargi, but it has been extensively >>> modified. It (is intended to) have complete support for Hindi and >>> Sanskrit, as well as Marathi. If any conjuncts in FreeSerif are >>> missing in FreeSans, it is a bug. >>> >> Hindi support is complete, I have verified it on several Hindi texts, >> displayed all conjuncts separately and since it was released used in >> several other Hindi texts. I have just tried to reprocess Neal's >> sample with FreeSans and indeed ligatures are missing, kta, pta, dga >> and others. I hope you still have the sample table with all conjuncts >> from the Velthuis manual. This will help you to find what is missing. >> If you make the same sample as you sent me many times during >> development, I will review it quickly and send the feedback. >> >> -- >> Zdeněk Wagner >> http://hroch486.icpf.cas.cz/wagner/ >> http://icebearsoft.euweb.cz >> >> >> >> -- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
Hi Zdenek, I'm glad you like the looks of Sanskrit in FreeSerif! Regarding Sanskrit in FreeSans: You're right, it is incomplete. I now remember, had started implementing Sanskrit there, but was interrupted. I hope to push that effort forward in the next release. I also see one or two glitches regarding mark placement in FreeSerif. I'll work with you guys off-line on those. Thanks for your support! On Sun, Sep 9, 2012 at 11:09 AM, Zdenek Wagner wrote: > 2012/9/9 Steve White : >> I finally got Neal's examples working, too. (The problem was, I had >> altered the header tex file he provided, so that it would run with my >> set of fonts, but had unwittingly also cut out one instance of >> RomDev). The process is: obtain the RomDev.map file, compile it with >> 'teckit_compile -u RomDev.map', place the resulting RomDev.tec file in >> the same directory as the .tex files. The xelatex the main tex file. >> >> The result is pretty to my eyes; the conjuncts are working, as near as >> I can tell. >> >> Concerning Zdenek's comments: >> >> The Devanagari feature lookup tables in FreeSerif are arranged so that >> modern forms are default, and the more extensive Sanskrit forms must >> be turned on by explicitly specifying Sanskrit as the text language. >> (It is safest always to specify the language. Unfortunately, xelatex >> complains very confusingly if no tables are explicitly turned on by >> the specified language.) >> >> FreeSans is indeed derived from Gargi, but it has been extensively >> modified. It (is intended to) have complete support for Hindi and >> Sanskrit, as well as Marathi. If any conjuncts in FreeSerif are >> missing in FreeSans, it is a bug. >> > Hindi support is complete, I have verified it on several Hindi texts, > displayed all conjuncts separately and since it was released used in > several other Hindi texts. I have just tried to reprocess Neal's > sample with FreeSans and indeed ligatures are missing, kta, pta, dga > and others. I hope you still have the sample table with all conjuncts > from the Velthuis manual. This will help you to find what is missing. > If you make the same sample as you sent me many times during > development, I will review it quickly and send the feedback. > > -- > Zdeněk Wagner > http://hroch486.icpf.cas.cz/wagner/ > http://icebearsoft.euweb.cz > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
2012/9/9 Steve White : > I finally got Neal's examples working, too. (The problem was, I had > altered the header tex file he provided, so that it would run with my > set of fonts, but had unwittingly also cut out one instance of > RomDev). The process is: obtain the RomDev.map file, compile it with > 'teckit_compile -u RomDev.map', place the resulting RomDev.tec file in > the same directory as the .tex files. The xelatex the main tex file. > > The result is pretty to my eyes; the conjuncts are working, as near as > I can tell. > > Concerning Zdenek's comments: > > The Devanagari feature lookup tables in FreeSerif are arranged so that > modern forms are default, and the more extensive Sanskrit forms must > be turned on by explicitly specifying Sanskrit as the text language. > (It is safest always to specify the language. Unfortunately, xelatex > complains very confusingly if no tables are explicitly turned on by > the specified language.) > > FreeSans is indeed derived from Gargi, but it has been extensively > modified. It (is intended to) have complete support for Hindi and > Sanskrit, as well as Marathi. If any conjuncts in FreeSerif are > missing in FreeSans, it is a bug. > Hindi support is complete, I have verified it on several Hindi texts, displayed all conjuncts separately and since it was released used in several other Hindi texts. I have just tried to reprocess Neal's sample with FreeSans and indeed ligatures are missing, kta, pta, dga and others. I hope you still have the sample table with all conjuncts from the Velthuis manual. This will help you to find what is missing. If you make the same sample as you sent me many times during development, I will review it quickly and send the feedback. > Gargi has undergone big improvements this year, thanks to Monika Shah. > I have seen some interim versions, and have been told it will be released > soon. > (The glyphs in FreeSans are drawn from earlier versions of Gargi, > and the font has developed independently since.) > My understanding however is that Gargi was originally developed by > Hindi speakers. > > Cheers! > > > On Sun, Sep 9, 2012 at 6:35 AM, Neal Delmonico > wrote: >> I am not sure this made it to the full list. Therefore, I am forwarding >> it. >> >> My problem with FreeSerif has been solved. Everything is working now, >> even the page headings with the help of FakeSlant. I think it is the >> best font yet for those of us working with Devanagari on a regular >> basis. >> >> Best >> >> Neal >> >> >> -- Forwarded message -- >> From: Zdenek Wagner >> To: Steve White >> Cc: >> Date: Sun, 9 Sep 2012 01:05:01 +0200 >> Subject: Re: [XeTeX] FreeSerif not working for me in Devanagari >> 2012/9/8 Steve White : >>> Hi Neal, >>> >>> I'm very pleased to hear it's working for you! >>> >>> Could you please write to the mailing list, to let them know? (To >>> date, the advice has been "don't use FreeFont".) It would be great to >>> see your working examples there, too. >>> >> I had some communication with Neal off list so I will summarize now. >> >> 1. Devanagari is a script used for several languages. They differ >> mainly in the repertoire of ligatures used, the full list being used >> in Sanskrit. Up to now, there anre Snaskrit fonts (not usable for >> Hindi, Marathi etc. because the users without education in Sanskrit >> will be unable to read them), Hindi fonts (not usable for Sanskrit due >> to missing ligatures), Marathi fonts (not usable even for Hindi), yet >> all of them use the Devanagari script. FreeSerif is the "new >> generation" font because it supplies the Devanagari script and the set >> of ligatures are set according to the language. FreeSans does not >> contain all Sanskrit ligatures. >> >> 2. The Devanagari block is missing in the italic shapes in both >> FreeSerif and FreeSans. In order to use them, AutoFakeSlant has to be >> specified. The default value is 0.2 if not given. >> >> Written shortly, Neal Delmonico uses Charis SIL as the default font >> and FreeSerif as the Sanskrit font. In order to have it work with all >> Sanskrit ligatures and italic, the header shouldbe as follows: >> >> \usepackage{xltxtra} >> \usepackage{polyglossia} >> \setmainfont{Charis SIL} >> \newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Language=Sanskrit,AutoFakeSlant=0.195]{FreeSerif} >> >> Mapping=RomDev is only needed if the text is input in transliteration, >> if the text is typed directly in UTF-8, it is not needed. >> >> For those who need more information: >> FreeSerif contains the Velthuis glyphs (I hope that the PFB files >> hand-tuned by Karel Piska were used). Positions of matras were >> precisely adjusted. Some characters with nuktas require different >> positions of u and uu matras in order to be readable and the nukta >> were visible and Steve made it. Consonants ka and pha need different >> position of e and ai matras. All this is done. >> >> FreeSans is derived from Gargi. It seems to me that G
Re: [XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
I finally got Neal's examples working, too. (The problem was, I had altered the header tex file he provided, so that it would run with my set of fonts, but had unwittingly also cut out one instance of RomDev). The process is: obtain the RomDev.map file, compile it with 'teckit_compile -u RomDev.map', place the resulting RomDev.tec file in the same directory as the .tex files. The xelatex the main tex file. The result is pretty to my eyes; the conjuncts are working, as near as I can tell. Concerning Zdenek's comments: The Devanagari feature lookup tables in FreeSerif are arranged so that modern forms are default, and the more extensive Sanskrit forms must be turned on by explicitly specifying Sanskrit as the text language. (It is safest always to specify the language. Unfortunately, xelatex complains very confusingly if no tables are explicitly turned on by the specified language.) FreeSans is indeed derived from Gargi, but it has been extensively modified. It (is intended to) have complete support for Hindi and Sanskrit, as well as Marathi. If any conjuncts in FreeSerif are missing in FreeSans, it is a bug. Gargi has undergone big improvements this year, thanks to Monika Shah. I have seen some interim versions, and have been told it will be released soon. (The glyphs in FreeSans are drawn from earlier versions of Gargi, and the font has developed independently since.) My understanding however is that Gargi was originally developed by Hindi speakers. Cheers! On Sun, Sep 9, 2012 at 6:35 AM, Neal Delmonico wrote: > I am not sure this made it to the full list. Therefore, I am forwarding > it. > > My problem with FreeSerif has been solved. Everything is working now, > even the page headings with the help of FakeSlant. I think it is the > best font yet for those of us working with Devanagari on a regular > basis. > > Best > > Neal > > > -- Forwarded message -- > From: Zdenek Wagner > To: Steve White > Cc: > Date: Sun, 9 Sep 2012 01:05:01 +0200 > Subject: Re: [XeTeX] FreeSerif not working for me in Devanagari > 2012/9/8 Steve White : >> Hi Neal, >> >> I'm very pleased to hear it's working for you! >> >> Could you please write to the mailing list, to let them know? (To >> date, the advice has been "don't use FreeFont".) It would be great to >> see your working examples there, too. >> > I had some communication with Neal off list so I will summarize now. > > 1. Devanagari is a script used for several languages. They differ > mainly in the repertoire of ligatures used, the full list being used > in Sanskrit. Up to now, there anre Snaskrit fonts (not usable for > Hindi, Marathi etc. because the users without education in Sanskrit > will be unable to read them), Hindi fonts (not usable for Sanskrit due > to missing ligatures), Marathi fonts (not usable even for Hindi), yet > all of them use the Devanagari script. FreeSerif is the "new > generation" font because it supplies the Devanagari script and the set > of ligatures are set according to the language. FreeSans does not > contain all Sanskrit ligatures. > > 2. The Devanagari block is missing in the italic shapes in both > FreeSerif and FreeSans. In order to use them, AutoFakeSlant has to be > specified. The default value is 0.2 if not given. > > Written shortly, Neal Delmonico uses Charis SIL as the default font > and FreeSerif as the Sanskrit font. In order to have it work with all > Sanskrit ligatures and italic, the header shouldbe as follows: > > \usepackage{xltxtra} > \usepackage{polyglossia} > \setmainfont{Charis SIL} > \newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Language=Sanskrit,AutoFakeSlant=0.195]{FreeSerif} > > Mapping=RomDev is only needed if the text is input in transliteration, > if the text is typed directly in UTF-8, it is not needed. > > For those who need more information: > FreeSerif contains the Velthuis glyphs (I hope that the PFB files > hand-tuned by Karel Piska were used). Positions of matras were > precisely adjusted. Some characters with nuktas require different > positions of u and uu matras in order to be readable and the nukta > were visible and Steve made it. Consonants ka and pha need different > position of e and ai matras. All this is done. > > FreeSans is derived from Gargi. It seems to me that Gargi was a > Marathi font because unlike Hindi, Marathi does not use characters > with nuktas. The characters with nuktas were present but there half > forms were missing. Thus the font was almost unusable fot Hindi. I > know that nuktas are often omitted in Hindi, ja is often used instead > of za (some people even pronounce jaruur instead of zaruur), pha is > often used instead of fa, qa is almost always replaced with ka. The > correct half forms were added to FreeSans. Nowadays fonts often omit > the classical kra ligatures. I have asked my Indian friends and they > replied that the they would prefare the classical shape. It was > therefore made by Steve. And as with FreeSerif, posit
[XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]
I am not sure this made it to the full list. Therefore, I am forwarding it. My problem with FreeSerif has been solved. Everything is working now, even the page headings with the help of FakeSlant. I think it is the best font yet for those of us working with Devanagari on a regular basis. Best Neal --- Begin Message --- 2012/9/8 Steve White : > Hi Neal, > > I'm very pleased to hear it's working for you! > > Could you please write to the mailing list, to let them know? (To > date, the advice has been "don't use FreeFont".) It would be great to > see your working examples there, too. > I had some communication with Neal off list so I will summarize now. 1. Devanagari is a script used for several languages. They differ mainly in the repertoire of ligatures used, the full list being used in Sanskrit. Up to now, there anre Snaskrit fonts (not usable for Hindi, Marathi etc. because the users without education in Sanskrit will be unable to read them), Hindi fonts (not usable for Sanskrit due to missing ligatures), Marathi fonts (not usable even for Hindi), yet all of them use the Devanagari script. FreeSerif is the "new generation" font because it supplies the Devanagari script and the set of ligatures are set according to the language. FreeSans does not contain all Sanskrit ligatures. 2. The Devanagari block is missing in the italic shapes in both FreeSerif and FreeSans. In order to use them, AutoFakeSlant has to be specified. The default value is 0.2 if not given. Written shortly, Neal Delmonico uses Charis SIL as the default font and FreeSerif as the Sanskrit font. In order to have it work with all Sanskrit ligatures and italic, the header shouldbe as follows: \usepackage{xltxtra} \usepackage{polyglossia} \setmainfont{Charis SIL} \newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Language=Sanskrit,AutoFakeSlant=0.195]{FreeSerif} Mapping=RomDev is only needed if the text is input in transliteration, if the text is typed directly in UTF-8, it is not needed. For those who need more information: FreeSerif contains the Velthuis glyphs (I hope that the PFB files hand-tuned by Karel Piska were used). Positions of matras were precisely adjusted. Some characters with nuktas require different positions of u and uu matras in order to be readable and the nukta were visible and Steve made it. Consonants ka and pha need different position of e and ai matras. All this is done. FreeSans is derived from Gargi. It seems to me that Gargi was a Marathi font because unlike Hindi, Marathi does not use characters with nuktas. The characters with nuktas were present but there half forms were missing. Thus the font was almost unusable fot Hindi. I know that nuktas are often omitted in Hindi, ja is often used instead of za (some people even pronounce jaruur instead of zaruur), pha is often used instead of fa, qa is almost always replaced with ka. The correct half forms were added to FreeSans. Nowadays fonts often omit the classical kra ligatures. I have asked my Indian friends and they replied that the they would prefare the classical shape. It was therefore made by Steve. And as with FreeSerif, positions of matras were precisely tuned. I forgot to mention positions of anusvaras. They are used in Hindi in the oblique case in plural and with verbs in plural feminine. The situation may be quite complex with some words and the position of anusvaras in all possible cases was tuned in order to make the words readable. Indian typographers use larger spacing preceding punctuation. In Sanskrit only dandas and double dandas are used but nowaday's languages accept also question and exclamation marks. The same spacing is expected (a few years ago I read an article written by an Indian typographer but I am not able to find it now). Majority of Devanagari fonts do not take it into account. Native users thus tend to enter a space preceding punctiatiom marks which leads to incorrect line breaks where punctuation may appear at the beginning of a line. It would be necessary to enter a fixed-width nonbreakable space but it is not usually available on a keyboard. FreeFont uses correct spacing. The same punctuation marks behave properly both in the Latin and Devanagari scripts (both FreeSans and FreeSerif, tested in a longer Hindi text). It was a huge amount of work but now all aspect of typesetting in Devanagari are properly set. Due to Steve's big care it is now the most beautiful Devanagari font. Remember that Unix distributions often come with an older version of GNU FreeFont. If you want to use the current version as distributed with TeX Live 2012, you have to delete the system fonts and follow the post-install actions as given in the TeX Live manual. The new version of the GNU FreeFont will then be available to the system, no applications relying on the existence of the font will be broken (verified by me in four different Linux distributions). > I still haven't got it going. Near as I can tell, this tec file isn't >