Re: [Minionpro-devel] Add more glyphs to the encoding

[Yan Zhou]

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

Re: [Minionpro-devel] Add more glyphs to the encoding

[Achim Blumensath]

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|
\___|


signature.asc
Description: Digital signature
___
Minionpro-devel mailing list
Minionpro-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/minionpro-devel

[Minionpro-devel] Add more glyphs to the encoding

[Yan Zhou]

Inspired by the excellent MinionPro project, I wrote my own scripts to add more 
Pro fonts to my LaTeX system. Given Garamond Premier Pro as an example, there 
are lots ligatures and accented glyphs. I tend o keep all accented glyphs in T1 
encoding but also include those ligatures. There is no enough slots in the 
encoding. Even I choose OT1 or LY1, if I want to add these rich accented 
glyphs, the slots is still not enough.

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?

Cheers,
Yan
___
Minionpro-devel mailing list
Minionpro-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/minionpro-devel