On Thursday 30 March 2017 23:53:10 Karl Berry wrote:
Previous (-) line caused that every type3 font was marked as type1.
Marked where, how?
In fm structure (not in output pdf). And then it is checked in check_fm_entry().
- } else + } else if (is_std_t1font(fm))
This alters the logic. Now there is no final fallback case. It looks dangerous.
Previously (-) everything fallback was marked as type1, even those PK fonts (which are type3). Which is wrong. Better fallback mechanism is to introduce new flag for PK/type3 fonts like I did in new patch for \pdfpkscalable.
Now is cmr10 really marked as scalable and included in output PDF only once (for cmr10 and also for cmr10 at 60pt).
But that's not what we want.
Without modification of pdftex.web it is not possible. Changing meaning of scalability of PK fonts needs to fix hasfmentry() usage by new function (e.g. isscalable()) like I did in in patch \pdfpkscalable. Note that without above "+ } else if (is_std_t1font(fm))" line (which I forgot to include into my previous patch) all PK/type3 fonts were ignored by pdftex in check_fm_entry() because they were treated as type1 (which was wrong).
Yes, I understand that idea in same way.
Oh, you did reply, sorry. Lost in my mail.
I'm going to play with PGC files as I think it still could be useful for ability to include any PDF shape into font file...
Fine, but pdftex is no longer the place to do experiments. We must emphasize stability above all with pdftex. I suggest playing in LuaTeX, where you can do all this stuff and a whole lot more at the Lua level ...
I mean to play with PGC files without modification of pdftex sources. Just use what is currently supported by pdftex and see what happens. -- Pali Rohár pali.rohar@gmail.com