On Mon, Mar 10, 2014 at 9:21 AM, stefano franchi <stefano.fran...@gmail.com> wrote: > On Mon, Mar 10, 2014 at 2:43 AM, Guenter Milde <mi...@users.sf.net> wrote: >> On 2014-03-10, stefano franchi wrote: >>> Question for the LaTeX font experts: >> >>> Is there a *single* font family that contains enough glyphs to cover >>> Latin scrpts plus European diacritics and Greek and Cyrillic and can >>> be used with DVI output? >> >> CM. If you install CM-Super and the CB-Greek fonts or define substitutes. >> >> Actually, as this are more than 280 glyphs, no single 8-bit font file >> could be used. Instead, you must use the "fontenc" package and suitable font >> encodings. This also means you are free to combine font families "at will". >> See the substitutefont package for examples. >> http://www.ctan.org/pkg/substitutefont > > Hi Guenter, > > thanks for the info about cm-super. I had already given a quick look > at your substitutefont package > but I am not sure I can use it with the required setup. > > In particular, it seems fontenc has some serious issues with tex4ht > and should be avoided. > > So I guess the answer to my question is simply: "It can't be done" > Or better: > "Such a wide glyph coverage can only be obtained by either: > 1. using fontenc (and perhaps your substitutefont) and switching > between different sets of more limited fonts, or > 2. having direct access to a wide coverage OTF font either directly > through XeTeX low-level font commands or through the higher level > fontspec package" > > Since neither option seems to be supported out of the box by tex4ht, I > guess my focus should now revert back to the latter.
Just to (provisionally ) close this issue: I just learned that supporting multiscript is indeed one of the biggest open issues on the tex4ht (my ignorance of this system is slowly decreasing, but I have yet to fully understand it). For future reference: 1. An excellent discussion of how to bring current tex4ht to cope with the full range of unicode points is contained in this thread on the tex4ht list: http://tug.org/pipermail/tex4ht/2013q1/000719.html The thread discusses various workarounds (including perl processing of the latex file to carry out unicode substitution) and one of of them apparently allowed a grad student to write a dissertation that included standard European diacritics, Greek, Arabic and Syriac. That's quite a high threshold, in my opinion. 2. Michal Hoftich has provided a proof of concept [1] of an alternative approach that actually looks even more promising in the long term. It relies on luatex and its ability to post-process the tex nodes directly in Lua. As far as I understand it, his approach eliminates the step of tex4ht that relies on DVI files and allows full use of fontspec and, therefore, of standard OTF fonts. I am not sure how much work would be needed to extend his proof of concept to the full range of features we'd like in the Lyx-->Word export, but I'm looking into it. My hope is that the work needed to support the current tex4ht processor will carry over into to a more powerful (font-wise) lua4ht setting. Cheers, Stefano [1] https://github.com/michal-h21/lua4ht > > > Thanks for the help. > > Stefano > > -- > __________________________________________________ > Stefano Franchi > Associate Research Professor > Department of Hispanic Studies Ph: +1 (979) 845-2125 > Texas A&M University Fax: +1 (979) 845-6421 > College Station, Texas, USA > > stef...@tamu.edu > http://stefano.cleinias.org -- __________________________________________________ Stefano Franchi Associate Research Professor Department of Hispanic Studies Ph: +1 (979) 845-2125 Texas A&M University Fax: +1 (979) 845-6421 College Station, Texas, USA stef...@tamu.edu http://stefano.cleinias.org
