Hi!
On Fri, 11 Aug 2006, Taco Hoekwater wrote:
> Andreas Schneider wrote:
>> Thanks a lot, with that it works now (with the texnansi encoding)! These
>> facts should be mentioned in the docs.
>
> The next version of texfont will create a dvips and dvipdfmx map file
> as well as a pdftex one, makin
Andreas Schneider wrote:
> Thanks a lot, with that it works now (with the texnansi encoding)! These
> facts should be mentioned in the docs.
The next version of texfont will create a dvips and dvipdfmx map file
as well as a pdftex one, making life a bit easier.
> But gv gives an error when I t
On Tue, 8 Aug 2006, Taco Hoekwater wrote:
> This process works in a similar fashion for all programs like
> pdftex, dvipdfmx, dvips, and xdvi, but texfont only creates a
> map file for pdftex. Unf, the pdftex map file cannot be used by
> dvips, so for dvips you have to create your own (like you did
On Aug 9, 2006, at 4:52 PM, Hans Hagen wrote:
> i see, interesting; before we do that, can you check if we can/need to
> do the same with texnansi, qx, etc ?
>
> Hans
texnansi is OK, in my experience, and qx as well. t5 also has some
LIGKERN instructions at the beginning, but doesn't have f-li
Thomas A. Schmitz wrote:
> And for the LIGKERN: yes, I asked about them on the tex-fonts list a
> while ago, and nobody considered them a problem. IMHO, they're
> totally useless or even worse, but I received the same ol' answers:
> can't change that, it's legacy etc. I think Mojca knows some
On Aug 9, 2006, at 3:58 PM, Taco Hoekwater wrote:
>> I've experimented with afm2pl, and as I wrote in an earlier mail: the
>> beginning of EC.enc with its additional LIGKERN instructions confuses
>> it so it will not include default ligatures.
>
> As it turns out, this is the same for afm2tfm. An
Taco Hoekwater wrote:
> because of a line in /opt/tex/teTeX/texmf/aliases :-/
>
>
ah, the dreadful aliases file ... in tex live they're gone ; let's hope
that this aliases fiel does not contain anything related to context tex
files (patterns for instance)
>
> Either way, it seems that this LIG
Thomas A. Schmitz wrote:
> On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote:
>
>
>>>how does -afmpl perform? i always suspected afm2tfm not to take non
>>>existing ligs into account
>>
>>Just as bad (here, at least). I'll get back to you about this
>>tomorrow,
>>it is too late for me to do s
Hans Hagen wrote:
>>
>
> well, we can consider to let texfont use a ec-fixed encoding for
> afm2tfm and the regular ec encoding for the rest
>
> --afmencoding=ec-fixed
>
> or so
or fix afm2pl.
>
> for a while afm2pl was the default, but then it suddenly defaulted to
> latex default (em) spac
Thomas A. Schmitz wrote:
> On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote:
>
>
>>> how does -afmpl perform? i always suspected afm2tfm not to take non
>>> existing ligs into account
>>>
>> Just as bad (here, at least). I'll get back to you about this
>> tomorrow,
>> it is too late fo
On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote:
>> how does -afmpl perform? i always suspected afm2tfm not to take non
>> existing ligs into account
>
> Just as bad (here, at least). I'll get back to you about this
> tomorrow,
> it is too late for me to do serious work.
>
I've experimented
Hans Hagen wrote:
> Taco Hoekwater wrote:
>
>>The second problem:
>>
>>texfont simply does not 'do' EC correctly (at least not on my machine).
>>There are simply no fi ligatures, not in pdftex either. I will
>>investigate this further.
>
> how does -afmpl perform? i always suspected afm2tfm not t
Taco Hoekwater wrote:
>
>
> When you create a map file for dvips for a texfont-installed
> font family, it needs to have those *-raw-* entries that will
> map the fonts to the real postscript font files on your harddisk,
> and those were missing from your bgj.map.
the reason why i create the map
Taco Hoekwater wrote:
>
> The second problem:
>
> texfont simply does not 'do' EC correctly (at least not on my machine).
> There are simply no fi ligatures, not in pdftex either. I will
> investigate this further.
how does -afmpl perform? i always suspected afm2tfm not to take non
existing ligs i
Hi Andreas,
Andreas Schneider wrote:
On Tue, 8 Aug 2006, Taco Hoekwater wrote:
Somehow you yourself (and not texfont!) have created a font map
file called bgj.map for dvips, and that file is wrong.
Hmm, I have created it just for LaTeX. Since it contains only entries
for ec-bgj* (without
On Tue, 8 Aug 2006, Taco Hoekwater wrote:
Somehow you yourself (and not texfont!) have created a font map
file called bgj.map for dvips, and that file is wrong.
Hmm, I have created it just for LaTeX. Since it contains only entries for
ec-bgj* (without 'raw') it should not interfere with the ot
Andreas Schneider wrote:
> On Tue, 8 Aug 2006, Hans Hagen wrote:
>
>>if the problem is in a font not having glyphs, you can consider making a
>>special encoding vector + enco-* file; not that complex since one can
>>start with an existing one
>
>
> The problem is that it does work with pdfte
On Tue, 8 Aug 2006, Hans Hagen wrote:
> if the problem is in a font not having glyphs, you can consider making a
> special encoding vector + enco-* file; not that complex since one can
> start with an existing one
The problem is that it does work with pdftex (tex -> pdf via
texexec --pdf), but i
On Mon, 7 Aug 2006, Taco Hoekwater wrote:
Andreas Schneider wrote:
but xdvi gives error messages like [...]
My guess is that you have to copy the final file you used
to the folder where dvips (and xdvi, which looks in the same
place normally) looks for encoding files.
I created a symlink in
19 matches
Mail list logo
