I tested the following file ============================================ \let\normalfont\font \def\font#1=#2 {% \message{Adding mapline: +#2 <#2.pfb}% \pdfmapline{+#2 <#2.pfb}\normalfont#1=#2 } \pdfoutput=1 \font\f=cmx10 at 100pt \f Hello \bye ============================================ and it seems to be ok. What error did you get? The \pdfmapfile primitive is very simple. It simply scans a <balanced text> and calls a C-subroutine to process it. Thanh On Thu, May 27, 2004 at 11:10:06PM +0200, Hans Hagen wrote:

At 10:16 27/05/2004, Nagy Bence wrote:

...

...

I uploaded pdftex-1.20a-rc4 to pdftex.sarovar.org/src. This version fixes the problem with finding fonts in included pdf, as discussed before. I also did some (heavy) cleaning up in the code handling fonts, so expect the unexpected.

I wrote a small macro to handling the maplines from my tex file, I want to get the mapline in the form "fontname

\let\normalfont\font \def\font#1=#2 {% \message{Adding mapline: +#2 <#2.pfb}% \pdfmapline{+#2 <#2.pfb}\normalfont#1=#2 }

it seems that the map line parser looks over the } and wants a \relax; a bug?

% interface=en

\starttext

\ifx\normalfont\undefined \let\normalfont\font \fi

\font\xxxx=cmr10 at 100pt

\def\font#1=#2 % {\message{Adding mapline: +#2 <#2.pfb}% \pdfmapline{+#2 <#2.pfb}\relax \normalfont#1=#2 }

\font\test=cmr10 at 100pt

\test oeps

\stoptext

On Mon, May 31, 2004 at 12:26:57PM +0200, Nagy Bence wrote:

...

============================================ \let\normalfont\font \def\font#1=#2 {% \message{Adding mapline: +#2 <#2.pfb}% \pdfmapline{+#2 <#2.pfb}\normalfont#1=#2 }

\pdfoutput=1 \font\f=cmx10 at 100pt \f Hello \bye ============================================

and it seems to be ok. What error did you get?

I think cmx10 exists somewhere in your map files, so pdfTeX loads it.

I didn't have cmx10 in my map files -- in fact the reason I renamed cmr10 to cmx10 is to make sure I don't have it anywhere. What platform are you using? Thanh