Thanks, But I have another problem. This solution is not very robust. The supposed behaviour is that, if I input \`A, it should pick up the glyph from the T1, if I input \`\pounds, it should pick the accent from TS1. However, without \UndeclareTextCommand \` form T1 this won't be the real behaviour. \`\pounds will put a ligature in position 000 above \pounds. But if I undeclare \` form T1, and declare the default to TS1, the \`\pounds works correctly, but \`A will produced the accented A rather than the glyph in T1. So I redeclare all the TextComposite commands in T1. This time \`A work correctly but \`\pounds does not work at all. The output says, ... can only be used in preamble..., and no more clue for the problem.
What I do now is keep the T1 untouched, and declare something like \lowergrave in TS1 and declare it the default. But this mean one has to remember when to use \` and when to use \lowergrave otherwise s/he won't get the right glyphs. In most cases, this is not a problem, since such \`\pounds is not usual among texts. But I wonder is there any more robust way to do this. On 17 Feb 2010, at 08:29, Achim Blumensath wrote: > Hello, > > Yan Zhou wrote: >> I work around this problem by stick to the T1 encoding, but removed >> all accents (000-012), and moved them to the empty slots in TS1 >> encoding. And then declare new names for them in the TS1 encoding. >> >> Is there any better way to solve this problem? > > No, not until there is a TeX engine supporting fonts with more that 256 > glyphs. > > Achim > -- > ________________________________________________________________________ > | \_____/ | > Achim Blumensath \O/ \___/\ | > TU Darmstadt =o= \ /\ \| > www.mathematik.tu-darmstadt.de/~blumensath /"\ o----| > ____________________________________________________________________\___| > _______________________________________________ > Minionpro-devel mailing list > Minionpro-devel@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/minionpro-devel _______________________________________________ Minionpro-devel mailing list Minionpro-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/minionpro-devel
