<div class="gmail_quote">2009/10/7 Lars Hellström <span dir="ltr"><<a href="mailto:Lars.Hellstrom@residenset.net">Lars.Hellstrom@residenset.net</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
No! I can think of some other font tools that would be troubled by this, but fontinst doesn't care how glyphs have been bundled into fonts.<br>
<br>
What /could/ be troublesome is having a PFB with more than 256 glyphs, since you then have to use it with more than one encoding in order to make all the glyphs accessible, but that is a restriction imposed by the DVI driver and PS/PDF itself.<div class="im">
<br></div></blockquote><div>Yes, I can now recall how Minion Pro support package works in a similar way <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
to [a, b, ..., z] and reglyph it to dtprc8a.pfb?<br>
</blockquote>
<br></div>
So now you have two PFBs? That's going the wrong way; what you need is instead a second encoding vector.<div class="im"><br></div></blockquote><div>No, that ways a typo, I meant "reglyph it to dtprc8r using \reglyphfont{dtprc8r}{dtpr8r}".<br>
<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">What you need to do is provide two base fonts that map to the same PFB, but using different encodings to provide different sets of glyphs. I think the following will be the easiest way to get it done (NOTE: I'm just typing this in the e-mail client, so watch out for typos):<br>
</blockquote><div>Thanks, your method worked (<b>\textsc() produce REAL small caps glyphs</b>) but I still have some questions. <br></div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
\transformfont{dtprcjq8t}{\reencodefont{t1cj}{\fromafm{dtpr8a}}}<br>
<br></blockquote><div>Here, is it that you kind of "borrowed" this t1cj.etx (which is seldom used), then \etxtoenc{}{} will be call when processing the 2nd file? <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
\installfont{dtpr8t}{dtpr8r,dtprcjq8t,newlatin}{t1}<br>
{T1}{dtp}{m}{n}{}<br></blockquote><div> Why did you use two fonts for dtpr8t? I though all glyphs necessary for dtpr8t are in dtpr8r?<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
\installfont{dtprc8t}{dtpr8r,dtprcjq8t,newlatin}{t1c}<br>
{T1}{dtp}{m}{sc}{}<br></blockquote><div>** This is the most "magic" thing that I don't understand, apparently t1c.etx is used, but isn't it supposed to be used when creating fake small caps? I checked the resulting pdf, apparently the Smallcaps are the real Asmall, Bsmall in the pfb. How is it possible?<br>
</div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Notice how one uses 8r.enc, the other t1cj.enc (which fontinst should have generated when processing make-dtp2.tex). Together, they give access to more glyphs from dtpr8a.pfb than any single encoding could.<br>
<br>
Now, even if I managed to avoid typos in the above, there is a risk that it will error out at some step while processing t1cj.etx or t1.etx; they're seldom used for reencoding, so there might be a piece of code somewhere that should be conditionalised. In that case, just report back what the error was.<br>
<font color="#888888">
<br></font></blockquote><div>I think I now understand the concept, so if I'm curious enough, I can write my own enc file (like Minion Pro's base-MinionPro-a[a/b/c/d/e].enc, instead of 'hijacking' the seldom used t1cj.etx and let fontinst generate t1cj.enc? Well I think it will require much care, for the moment <b>if I can understand how the t1cj.etx and why t1c.mtx can access REAL smallcaps glyphs, I'll be grateful.</b><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><font color="#888888">
Lars Hellström<br>
<br></font></blockquote><div><br>Many thanks Lars!<br><br>--<br>kmc <br></div></div><br>