--- Karl Berry <[EMAIL PROTECTED]> wrote: > For fonts that are in cid-x.map, are > dvipdfm_dl14.map entries needed at > all? What if the bkaiu* entries are removed > entirely, does it still > work? It would be easier to implement simply > omitting the entire entry > for anything in cid-x than to omit part of the > entry.
See below. > Also, I notice that the entry in cid-x is > [EMAIL PROTECTED]@ unicode :0:bkai00mp.ttf > > Can it be counted on that "bkaiu" (ie, everything > before the first @) > begins any fontname that should be dealt with > specially by updmap? > Otherwise, I don't know how it could be determined. [EMAIL PROTECTED]@ refers to 4000+ TFM files bkaiu00 -- bkaiuff and bkaiu0100 -- bkaiu10ff defined in Unicode.sfd If @-notation is used, then dvipdfmx combines them into a single font in PDF. On the other hand, if you write (notice :0: is meaningful only for ttc) bkaiu00 unicode bkai00mp.ttf bkaiu01 unicode bkai00mp.ttf [...] bkaiuff unicode bkai00mp.ttf bkaiu0100 unicode bkai00mp.ttf [...] bkaiu10ff unicode bkai00mp.ttf in one of your map file, then these bkai00mp.ttf are multiply embedded into PDF, even though they are subsetted hence each glyph is embeded only once. If you mix @-notation and explicit TFM names, then the explicit references take precedence. There are people who employes this precedence rule instead of creating hundreds of VF's. > Thanks, > k Regards, SMiyata -------------------------------------- Protect Your PC Now ! - 0 yen Security Campaign http://pr.mail.yahoo.co.jp/premium/ _______________________________________________ Cjk maillist - [email protected] https://lists.ffii.org/mailman/listinfo/cjk
