ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: texfont: installed font only works with pdftex
Date: Tue, 08 Aug 2006 23:26:19 +0200	[thread overview]
Message-ID: <44D9017B.7020600@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608082122340.24466@rabat.Mathematik.Uni-Marburg.DE>

[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]


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 'raw') it should not interfere with the other 
> mapfiles (created by texfont) which are for ec-raw-bgj* and 
> texnansi-raw-bgj* (with 'raw'), or am I mistaken? Anyway xdvi complains 
> about texnansi-raw-bgj* (see example below which I had already included 
> in one of my previous mails).

There are two problems that I can see. There is only one that you
can fix, and there is another problem that is a base texfont
issue.


The fixable problem first:

If there is a virtual font, then dvi processors will recursively
break it down into its constituents (those are the *-raw-* font
metrics). Eventually, when there are no longer virtual fonts to
resolve, it looks for the 'base' fonts in its map file.

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).

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.

Using the attached map file fragment, I can create a postscript file
that has fi ligatures of your example in texnansi encoding using
dvips. I have no xdvi here to try it, but that should work as well.



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.


Taco

[-- Attachment #2: texnansi-bgj.map --]
[-- Type: text/plain, Size: 301 bytes --]

texnansi-raw-bgjb ElegantGaramondBT-Bold    "TeXnANSIEncoding ReEncodeFont" <texnansi.enc <bgjb.pfb
texnansi-raw-bgjr ElegantGaramondBT-Roman   "TeXnANSIEncoding ReEncodeFont" <texnansi.enc <bgjr.pfb
texnansi-raw-bgjri ElegantGaramondBT-Italic "TeXnANSIEncoding ReEncodeFont" <texnansi.enc <bgjri.pfb

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-08-08 21:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06  8:07 texfont produces faked ligatures with ec encoding Andreas Schneider
2006-08-06  9:52 ` Taco Hoekwater
2006-08-06 15:00   ` Andreas Schneider
2006-08-06 16:53 ` Thomas A. Schmitz
     [not found]   ` <Pine.LNX.4.64.0608062211300.31615@rabat.Mathematik.Uni-Marburg.DE>
2006-08-06 21:00     ` Thomas A. Schmitz
2006-08-07  7:59       ` Andreas Schneider
2006-08-07  8:29         ` Andreas Schneider
2006-08-07  8:42           ` Taco Hoekwater
2006-08-07 12:34             ` texfont: installed font only works with pdftex Andreas Schneider
2006-08-07 13:25           ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-08  7:14             ` texfont: font only works with pdftex Andreas Schneider
2006-08-08  8:05               ` Hans Hagen
2006-08-08  8:33                 ` texfont: installed " Andreas Schneider
2006-08-08  8:56                   ` Taco Hoekwater
2006-08-08 19:27                     ` Andreas Schneider
2006-08-08 21:26                       ` Taco Hoekwater [this message]
2006-08-08 21:46                         ` Hans Hagen
2006-08-08 21:57                           ` Taco Hoekwater
2006-08-09  5:29                             ` Thomas A. Schmitz
2006-08-09 10:21                               ` Hans Hagen
2006-08-09 11:33                                 ` Taco Hoekwater
2006-08-09 13:58                               ` Taco Hoekwater
2006-08-09 14:14                                 ` Hans Hagen
2006-08-09 14:29                                 ` Thomas A. Schmitz
2006-08-09 14:52                                   ` Hans Hagen
2006-08-09 15:44                                     ` Thomas A. Schmitz
2006-08-08 21:50                         ` Hans Hagen
2006-08-11  9:34                         ` Andreas Schneider
2006-08-11  9:59                           ` Taco Hoekwater
2006-08-11 10:33                             ` Andreas Schneider
2006-08-06 21:42     ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-06 23:22     ` Mojca Miklavec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44D9017B.7020600@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).