Re: Bug 2430 -- TrueType fonts handling and solution for it

[Paul Sokolovsky <pmiscml@gmail.com>]

Hello Marcin,

Monday, January 21, 2008, 9:53:16 PM, you wrote:

> Dnia Monday, 21 of January 2008, Paul Sokolovsky napisał:
>> Monday, January 21, 2008, 3:08:31 PM, Marcin wrote:

>>   Is such extra level of indirection and multiplexing really required?

> Yes -- it is required. This way we will have it solved once and will not
> have to change it just because XDE or PSDE uses fonts in other way.

  Yes.

>> Or rather, I wish we separated this matter to 2 separate ones:
>>
>> 1. Adopting reusable pattern for solving task of "need to 'register'
>> objects of arbitrary type".
>> 2. See what kind of registration support required for objects of type
>> fonts.

> Feel free to suggest other solution. This one which I summarized was 
> discussed on IRC for quite long time.

>> For 1, I wish we adopted some easy scheme, like, for all packages
>> containing object of type foo, to have in postinstall:
>>
>> [ -x /usr/bin/update-foo ] && /usr/bin/update-foo

> What will be "update-foo" for fonts? Will it be "update-fonts" which Rolf
> and I suggest or will it be "update-fonts-for-opie" 
> + "update-fonts-for-fontconfig" + "update-fonts-for-xde" etc? I have a
> feeling that you try to force us to go second way.

>> Then, for each specific object type, specific package will handle
>> registration

> And thats what our suggestion do. If you install "specific object type"
> (which TrueType/OpenType fonts are) then "specific package" 
> (update-fonts-common + scripts from each system which use TTF) will 
> handle registration of "objects" (fonts) in system.


>> for example among following (but not limiting to) choices:

>> 1. No registration needed at all - no /usr/bin/update-foo, nothing
>> will be done.

> And nothing will see TT/OT font.

  I didn't talk about fonts, I was talking about *generic* scheme
which might be reusable for other (all) kinds of objects and
environments.

>> 2. In simplest case, /usr/bin/update-foo will be a symlink to tool
>> handling registration for specific environment.

> And when user will install other environment then which one will be 
> called?

  That depends on object type.

>> 3. If some objects really need registration with different facilities,
>> multiplex scheme as described can be used.

> If there are scripts only for one environment installed then it is like
> your 2nd point.

  If you think it should be 3rd for fonts, then it must be that way.

> I really do not see a problem where you are trying to find one.

  I'm usually trying to generalize a solution if its worth that IMHO,
and for OE, a rather large system, having best practices of general
solutions is worthy aim IMHO. Still, everything is at right time, so
if you think what I've written above is not relevant to current issue
at hand, let's skip it.

  The described as above font handling is +1 from me.



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com