Would someone please unsubscribe me. I can't seem to do it myself.<div><br clear="all"> —Mohamed<br>
<br><br><div class="gmail_quote">On 22 June 2011 10:23, <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: dump a tfm to a file (Ulrike Fischer)<br>
2. Re: dump a tfm to a file (Ulrike Fischer)<br>
3. Re: dump a tfm to a file (Taco Hoekwater)<br>
4. Re: dump a tfm to a file (Luis Rivera)<br>
5. Re: dump a tfm to a file (Khaled Hosny)<br>
6. Re: dump a tfm to a file (Ulrike Fischer)<br>
7. Re: dump a tfm to a file (luigi scarso)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jun 2011 18:30:19 +0200<br>
From: Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>><br>
To: <a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <15b67h71makxr$.<a href="mailto:dlg@nililand.de">dlg@nililand.de</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Am Tue, 21 Jun 2011 10:33:26 +0200 schrieb Mojca Miklavec:<br>
<br>
>> I know nothing about tex4ht except that it exists and is annoyingly hard<br>
>> to set up right (which is exactly why that is the only thing I know<br>
>> about it).<br>
<br>
And this from the user of a system which so hard to set up that it<br>
breaks permanently in miktex ;-)<br>
<br>
Actually I don't think that tex4ht is overly complicated, but yes<br>
tex4ht it is not really easy to debug or to get details right or to<br>
expand.<br>
<br>
One central problem is that not much of its "inner working" is<br>
known. Eitan Gurari was always very helpful on c.t.t. If someone<br>
mentioned a bug or a feature request a new beta arrived. But as far<br>
as I know he was the only one who worked with the source and<br>
actually understood what the various pieces do. And while there is<br>
some code documentation it is not helpful as it contains a lot of<br>
personal remarks, e-mail snippets and obviously simply evolved over<br>
time. And this makes it difficult to find a new maintainer, or<br>
someone who can help with problems and insights.<br>
<br>
But on the other side texh4t contains a lot of useful code. I was<br>
quite impressed some days ago when I could convert a document<br>
containing a biblatex bibliography without much problems to an open<br>
office document. And the html generation is really quite powerful<br>
and sophisticated. It would be a pity if one would do all the work<br>
again instead of trying first if it can be reused and adapted.<br>
<br>
<br>
>> But if there is a dedicated format that tex4ht understands,<br>
>> then it should be quite straightforward to create such a file based on<br>
>> the internal metrics representation, especially if it is a human-readable<br>
>> format.<br>
><br>
> It is. See:<br>
> /usr/local/texlive/2011/texmf-dist/tex4ht/ht-fonts/unicode/lm/lm-ec.htf<br>
<br>
tex4ht doesn't use only this htf-files. At first it loads the tfm's<br>
of the fonts mentioned in the dvi (I don't know exactly why).<br>
<br>
<br>
--<br>
Ulrike Fischer<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jun 2011 18:37:50 +0200<br>
From: Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>><br>
To: <a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <m4n3f9412s4a$.<a href="mailto:dlg@nililand.de">dlg@nililand.de</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Am Tue, 21 Jun 2011 10:57:35 +0200 schrieb Khaled Hosny:<br>
<br>
<br>
> Or one can just ditch tex4ht entirely and go with more sane lua based<br>
> solution like the amazing x(h)ml export work that Hans is doing (it can<br>
> even export xii.tex ;) ).<br>
<br>
tex4ht can export xii.tex too. I tried ;-) And while I would<br>
certainly like to try Hans code: it probably doesn't work for latex,<br>
so it would need someone who 1. understand it and 2. can adapt it.<br>
Both not very easy without some good documentation.<br>
<br>
Btw: Do you have time to synch the unstable branch of luaotfload<br>
with the newest context code?<br>
<br>
--<br>
Ulrike Fischer<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 21 Jun 2011 19:42:51 +0200<br>
From: Taco Hoekwater <<a href="mailto:taco@elvenkind.com">taco@elvenkind.com</a>><br>
To: "<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>" <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>>, "General discussion of<br>
LuaTeX." <<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Cc: "<a href="mailto:luatex@tug.org">luatex@tug.org</a>" <<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <<a href="mailto:06A802EF-6FA7-4778-81D7-FEBEA5213813@elvenkind.com">06A802EF-6FA7-4778-81D7-FEBEA5213813@elvenkind.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
<br>
<br>
<br>
On 21 jun. 2011, at 18:30, Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>> wrote:<br>
<br>
> Am Tue, 21 Jun 2011 10:33:26 +0200 schrieb Mojca Miklavec:<br>
><br>
>>> I know nothing about tex4ht except that it exists and is annoyingly hard<br>
>>> to set up right (which is exactly why that is the only thing I know<br>
>>> about it).<br>
><br>
> And this from the user of a system which so hard to set up that it<br>
> breaks permanently in miktex ;-)<br>
><br>
<br>
Actually, that quote was me talking. I don't think Mojca would claim that anything at all is hard to set up ;)<br>
<br>
>> It is. See:<br>
>> /usr/local/texlive/2011/texmf-dist/tex4ht/ht-fonts/unicode/lm/lm-ec.htf<br>
><br>
> tex4ht doesn't use only this htf-files. At first it loads the tfm's<br>
> of the fonts mentioned in the dvi (I don't know exactly why).<br>
<br>
If it really needs TFMs, I do not think it can ever be compatible with luatex (or xetex, for that matter).<br>
<br>
Best wishes,<br>
Taco<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 21 Jun 2011 14:09:04 -0500<br>
From: Luis Rivera <<a href="mailto:jlrn77@gmail.com">jlrn77@gmail.com</a>><br>
To: "General discussion of LuaTeX." <<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <<a href="mailto:BANLkTimorM91Futmw9YRsiiwWw6u6J%2BWQw@mail.gmail.com">BANLkTimorM91Futmw9YRsiiwWw6u6J+WQw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On 21/06/2011, Taco Hoekwater <<a href="mailto:taco@elvenkind.com">taco@elvenkind.com</a>> wrote:<br>
><br>
> On 21 jun. 2011, at 18:30, Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>> wrote:<br>
><br>
>><br>
>> tex4ht doesn't use only this htf-files. At first it loads the tfm's<br>
>> of the fonts mentioned in the dvi (I don't know exactly why).<br>
><br>
> If it really needs TFMs, I do not think it can ever be compatible with<br>
> luatex (or xetex, for that matter).<br>
><br>
<br>
afaik, tex4ht doesn't load the tfms to generate the dvi: that's<br>
required by some tex engine (pdfTeX, afaik) which generates a dvi with<br>
some tailored suited macros (it makes three passes, to ensure the bbl,<br>
idx and other stuff are properly compiled); then, in the second stage,<br>
tex4ht deciphers the dvi with the htf files to generate some xml<br>
files; and in the third stage, t4ht assembles the final html/odt file<br>
with the xmls, the images, and all the other stuff generated by the<br>
previous steps. I collect that from reading the oolatex script, which<br>
actually controls the whole process.<br>
<br>
So, in my not very enlightened opinion, htf files are necessary only<br>
because the tfm files that generate a dvi may have different<br>
encodings, so the resulting dvi files are spaghetti encoded, and there<br>
is some need to ensure that appropriate utf8 sequences are produced<br>
from the messy dvi into the the generated xml files. htf files are<br>
mainly maps from 8 bit encoded fonts into utf8.<br>
<br>
If a TeX engine could read and write files properly UTF8 encoded, the<br>
need for htf files would be bypassed; tex4ht would only have to<br>
translate typesetting instructions (from a target successor of dvi<br>
format) into xml tags, since the encoding would be UTF8 right from the<br>
beginning.<br>
<br>
--<br>
Luis Rivera<br>
O< <a href="http://www.asciiribbon.org/" target="_blank">http://www.asciiribbon.org/</a> campaign<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 21 Jun 2011 23:05:36 +0200<br>
From: Khaled Hosny <<a href="mailto:khaledhosny@eglug.org">khaledhosny@eglug.org</a>><br>
To: <a href="mailto:luatex@nililand.de">luatex@nililand.de</a>, "General discussion of LuaTeX."<br>
<<a href="mailto:luatex@tug.org">luatex@tug.org</a>><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <20110621210536.GA15999@khaled-laptop><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On Tue, Jun 21, 2011 at 06:37:50PM +0200, Ulrike Fischer wrote:<br>
> Am Tue, 21 Jun 2011 10:57:35 +0200 schrieb Khaled Hosny:<br>
><br>
><br>
> > Or one can just ditch tex4ht entirely and go with more sane lua based<br>
> > solution like the amazing x(h)ml export work that Hans is doing (it can<br>
> > even export xii.tex ;) ).<br>
><br>
> tex4ht can export xii.tex too. I tried ;-) And while I would<br>
> certainly like to try Hans code: it probably doesn't work for latex,<br>
> so it would need someone who 1. understand it and 2. can adapt it.<br>
> Both not very easy without some good documentation.<br>
<br>
Hans code is probably deeply tied with ConTeXt, I was only suggesting<br>
that someone would try a similar approach (I don't know much about<br>
tex4ht either, but from where I stand it looks like a big, complex and<br>
fragile hack that is only necessary because TeX can't do better.)<br>
<br>
> Btw: Do you have time to synch the unstable branch of luaotfload<br>
> with the newest context code?<br>
<br>
I don't think so, Hans did some big changes (to make the code even more<br>
separable) and it might require rewriting luaotfload's glue layer, but I<br>
can't afford time for that (I can only do small and interesting hacks :)<br>
for the time being.)<br>
<br>
Regards,<br>
Khaled<br>
<br>
--<br>
Khaled Hosny<br>
Egyptian<br>
Arab<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 22 Jun 2011 10:56:58 +0200<br>
From: Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>><br>
To: <a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <<a href="mailto:h0k1gi80icam.dlg@nililand.de">h0k1gi80icam.dlg@nililand.de</a>><br>
Content-Type: text/plain; charset="iso-8859-15"<br>
<br>
Am Tue, 21 Jun 2011 14:09:04 -0500 schrieb Luis Rivera:<br>
<br>
>>> tex4ht doesn't use only this htf-files. At first it loads the tfm's<br>
>>> of the fonts mentioned in the dvi (I don't know exactly why).<br>
>><br>
>> If it really needs TFMs, I do not think it can ever be compatible with<br>
>> luatex (or xetex, for that matter).<br>
>><br>
><br>
> afaik, tex4ht doesn't load the tfms to generate the dvi: that's<br>
> required by some tex engine (pdfTeX, afaik) which generates a dvi with<br>
> some tailored suited macros (it makes three passes, to ensure the bbl,<br>
> idx and other stuff are properly compiled); then, in the second stage,<br>
> tex4ht deciphers the dvi with the htf files to generate some xml<br>
> files; and in the third stage, t4ht assembles the final html/odt file<br>
> with the xmls, the images, and all the other stuff generated by the<br>
> previous steps. I collect that from reading the oolatex script, which<br>
> actually controls the whole process.<br>
><br>
<br>
<br>
<br>
To avoid some confusion: There is tex4ht as "system", large package<br>
with various files, folders, configuration etc. And there is the<br>
central application tex4ht.exe.<br>
<br>
tex4ht.exe is a dvi-driver. It takes a dvi and generates eg a<br>
html-file. To be able to do this the dvi must contain a lot<br>
\specials. This specials are inserted by tex4ht.sty and various<br>
4ht-files during the previous (lua)latex runs.<br>
<br>
<br>
> So, in my not very enlightened opinion, htf files are necessary only<br>
> because the tfm files that generate a dvi may have different<br>
> encodings, so the resulting dvi files are spaghetti encoded, and there<br>
> is some need to ensure that appropriate utf8 sequences are produced<br>
> from the messy dvi into the the generated xml files. htf files are<br>
> mainly maps from 8 bit encoded fonts into utf8.<br>
><br>
> If a TeX engine could read and write files properly UTF8 encoded, the<br>
> need for htf files would be bypassed; tex4ht would only have to<br>
> translate typesetting instructions (from a target successor of dvi<br>
> format) into xml tags, since the encoding would be UTF8 right from the<br>
> beginning.<br>
<br>
The htf-files don't do only reencoding or mapping. They are used to<br>
control the "look" of the output. E.g.<br>
<br>
'b' '' 98<br>
<br>
will give the expected "b" if the input is char98 (= b). But in<br>
another htf-file you find at position 98 this:<br>
<br>
'B' '4' 98<br>
<br>
and this will give<br>
<br>
<span class="small-caps">B</span><br>
<br>
(The <span> comes from the '4' which is a class number).<br>
<br>
So the htf-files gives you a low-level mapping characters to other<br>
representations (like html entities) and of fonts to font features<br>
in html like small-caps, bold etc.<br>
<br>
<br>
The generation of the dvi works fine with luatex. The problems<br>
starts at the dvi -> html step with tex4ht (if the document uses<br>
system fonts). The dvi contains font names like "file:lm-modern..."<br>
and tex4ht looks (for still unknown reasons) for its tfm and can't<br>
find it.<br>
<br>
For a simple document I got around the problem by using the<br>
low-level command \font\test=Arial and renaming an arbitrary tfm to<br>
arial.tfm. Currently I seem to be able to use ASCII and ???, but<br>
the ? is output to ?. This looks like a 256-barrier ;-(. But<br>
perhaps one can get around it by extending the htf-files.<br>
<br>
<br>
<br>
--<br>
Ulrike Fischer<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 22 Jun 2011 11:23:14 +0200<br>
From: luigi scarso <<a href="mailto:luigi.scarso@gmail.com">luigi.scarso@gmail.com</a>><br>
To: <a href="mailto:luatex@tug.org">luatex@tug.org</a><br>
Subject: Re: [luatex] dump a tfm to a file<br>
Message-ID: <<a href="mailto:BANLkTimi32cT5DQGCT4LMEzizhoe3pvh9g@mail.gmail.com">BANLkTimi32cT5DQGCT4LMEzizhoe3pvh9g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Wed, Jun 22, 2011 at 10:56 AM, Ulrike Fischer <<a href="mailto:luatex@nililand.de">luatex@nililand.de</a>> wrote:<br>
> Am Tue, 21 Jun 2011 14:09:04 -0500 schrieb Luis Rivera:<br>
><br>
>>>> tex4ht doesn't use only this htf-files. At first it loads the tfm's<br>
>>>> of the fonts mentioned in the dvi (I don't know exactly why).<br>
>>><br>
>>> If it really needs TFMs, I do not think it can ever be compatible with<br>
>>> luatex (or xetex, for that matter).<br>
>>><br>
>><br>
>> afaik, tex4ht doesn't load the tfms to generate the dvi: that's<br>
>> required by some tex engine (pdfTeX, afaik) which generates a dvi with<br>
>> some tailored suited macros (it makes three passes, to ensure the bbl,<br>
>> idx and other stuff are properly compiled); then, in the second stage,<br>
>> tex4ht deciphers the dvi with the htf files to generate some xml<br>
>> files; and in the third stage, t4ht assembles the final html/odt file<br>
>> with the xmls, the images, and all the other stuff generated by the<br>
>> previous steps. I collect that from reading the oolatex script, which<br>
>> actually controls the whole process.<br>
>><br>
><br>
><br>
><br>
> To avoid some confusion: There is tex4ht as "system", large package<br>
> with various files, folders, configuration etc. And there is the<br>
> central application tex4ht.exe.<br>
><br>
> tex4ht.exe is a dvi-driver. It takes a dvi and generates eg a<br>
> html-file. To be able to do this the dvi must contain a lot<br>
> \specials. This specials are inserted by tex4ht.sty and various<br>
> 4ht-files during the previous (lua)latex runs.<br>
><br>
><br>
>> So, in my not very enlightened opinion, htf files are necessary only<br>
>> because the tfm files that generate a dvi may have different<br>
>> encodings, so the resulting dvi files are spaghetti encoded, and there<br>
>> is some need to ensure that appropriate utf8 sequences are produced<br>
>> from the messy dvi into the the generated xml files. htf files are<br>
>> mainly maps from 8 bit encoded fonts into utf8.<br>
>><br>
>> If a TeX engine could read and write files properly UTF8 encoded, the<br>
>> need for htf files would be bypassed; tex4ht would only have to<br>
>> translate typesetting instructions (from a target successor of dvi<br>
>> format) into xml tags, since the encoding would be UTF8 right from the<br>
>> beginning.<br>
><br>
> The htf-files don't do only reencoding or mapping. They are used to<br>
> control the "look" of the output. E.g.<br>
><br>
> 'b' '' ? ? 98<br>
><br>
> will give the expected "b" if the input is char98 (= b). But in<br>
> another htf-file you find at position 98 this:<br>
><br>
> 'B' '4' ? ?98<br>
><br>
> and this will give<br>
><br>
> <span class="small-caps">B</span><br>
><br>
> (The <span> ?comes from the '4' which is a class number).<br>
><br>
> So the htf-files gives you a low-level mapping characters to other<br>
> representations (like html entities) and of fonts to font features<br>
> in html like small-caps, bold etc.<br>
><br>
><br>
> The generation of the dvi works fine with luatex. The problems<br>
> starts at the dvi -> html step with tex4ht (if the document uses<br>
> system fonts). The dvi contains font names like "file:lm-modern..."<br>
> and tex4ht looks (for still unknown reasons) for its tfm and can't<br>
> find it.<br>
><br>
> For a simple document I got around the problem by using the<br>
> low-level command \font\test=Arial and renaming an arbitrary tfm to<br>
> arial.tfm. ?Currently I seem to be able to use ASCII and ???, but<br>
> the ? is output to ??. This looks like a 256-barrier ;-(. But<br>
> perhaps one can get around it by extending the htf-files.<br>
With context mkii (texlive 2009, pdftex engine: test.mkii is an utf-8 file)<br>
<br>
%%% test.mkii<br>
\enableregime[utf]<br>
\starttext<br>
goo<br>
???@??<br>
\stoptext<br>
%%%<br>
<br>
$>texexec --dvi test.mkii<br>
$>tex4ht test.dvi<br>
<br>
<br>
----------------------------<br>
tex4ht.c (2009-01-31-07:33 kpathsea)<br>
/opt/TeXLive2009/tl2009/bin/i386-linux/tex4ht test.dvi<br>
(/opt/TeXLive2009/tl2009/texmf-dist/tex4ht/base/unix/tex4ht.env)<br>
(/opt/TeXLive2009/tl2009/texmf-dist/tex4ht/ht-fonts/iso8859/1/charset/unicode.4hf)<br>
(/opt/TeXLive2009/tl2009/texmf-dist/fonts/tfm/hoekwater/context/fmvr8x.tfm)<br>
(/opt/TeXLive2009/tl2009/texmf-dist/tex4ht/ht-fonts/unicode/marvosym/fmvr8x.htf)<br>
(/opt/TeXLive2009/tl2009/texmf-dist/fonts/tfm/public/lm/ec-lmr12.tfm)<br>
(/opt/TeXLive2009/tl2009/texmf-dist/tex4ht/ht-fonts/alias/lm/lm-ec/ec-lm.htf)<br>
Searching `lm-ec.htf' for `ec-lmr12.htf'<br>
(/opt/TeXLive2009/tl2009/texmf-dist/tex4ht/ht-fonts/unicode/lm/lm-ec.htf)<br>
[1 file test.html<br>
]<br>
Execute script `test.lg'<br>
<br>
<br>
test.lg is<br>
----------------------<br>
htfcss: ec-lmbo font-style: oblique;<br>
htfcss: ec-lmbx font-weight: bold;<br>
htfcss: ec-lmbxi font-style:italic; font-weight: bold;<br>
htfcss: ec-lmbxo font-style: oblique; font-weight: bold;<br>
htfcss: ec-lmcsco font-style: oblique;<br>
htfcss: ec-lmri font-style:italic;<br>
htfcss: ec-lmro font-style: oblique;<br>
htfcss: ec-lmss font-family: sans-serif;<br>
htfcss: ec-lmssbo font-family: sans-serif; font-style: oblique;<br>
font-weight: bold;<br>
htfcss: ec-lmssbx font-family: sans-serif; font-weight: bold;<br>
htfcss: ec-lmssdc font-family: sans-serif;<br>
htfcss: ec-lmssdo font-family: sans-serif; font-style: oblique;<br>
htfcss: ec-lmsso font-family: sans-serif; font-style: oblique;<br>
htfcss: ec-lmssq font-family: sans-serif;<br>
htfcss: ec-lmssqbo font-family: sans-serif; font-style: oblique;<br>
font-weight: bold;<br>
htfcss: ec-lmssqbx font-family: sans-serif; font-weight: bold;<br>
htfcss: ec-lmssqo font-family: sans-serif; font-style: oblique;<br>
htfcss: ec-lmtcsc font-family: monospace;<br>
htfcss: ec-lmtcso font-style: oblique; font-family: monospace;<br>
htfcss: ec-lmtk font-family: monospace;<br>
htfcss: ec-lmtko font-style: oblique; font-family: monospace;<br>
htfcss: ec-lmtl font-weight: light; font-family: monospace;<br>
htfcss: ec-lmtlc font-weight: light; font-family: monospace;<br>
htfcss: ec-lmtlco font-weight: light; font-style: oblique;<br>
font-family: monospace;<br>
htfcss: ec-lmtlo font-weight: light; font-style: oblique;<br>
font-family: monospace;<br>
htfcss: ec-lmtt font-family: monospace;<br>
htfcss: ec-lmtti font-family: monospace; font-style:italic;<br>
htfcss: ec-lmtto font-style: oblique; font-family: monospace;<br>
htfcss: ec-lmvtk font-family: monospace;<br>
htfcss: ec-lmvtko font-style: oblique; font-family: monospace;<br>
htfcss: ec-lmvtl font-weight: light; font-family: monospace;<br>
htfcss: ec-lmvtlo font-weight: light; font-style: oblique;<br>
font-family: monospace;<br>
htfcss: ec-lmvtt font-family: monospace;<br>
htfcss: ec-lmvtto font-style: oblique; font-family: monospace;<br>
File: test.html<br>
--- characters ---<br>
Font("ec-lmr","12","12","100")<br>
Font("fmvr8x","","10","120")<br>
------------------<br>
<br>
<br>
The result is<br>
<br>
1<br>
goo €??@cc<br>
<br>
<br>
(where 1 is the pagenumber on the header)<br>
<br>
<br>
<br>
<br>
--<br>
luigi<br>
<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 30, Issue 13<br>
**************************************<br>
</blockquote></div><br></div>