From: "=?UTF-8?Q?Alfredo_Fern=c3=a1ndez_D=c3=adaz?=" <lswitcher-dev@2rosenthals.com>
Subject: Re: [lswitcher-dev] lSwitcher-2-93-0-RC_1.wpi
To: lSwitcher Developers Mailing List <lswitcher-dev@2rosenthals.com>
References: <list-1323643@2rosenthals.com>
Message-ID: <5FBD1C09.5020703@yahoo.es>
Date: Tue, 24 Nov 2020 15:43:21 +0100
User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:38.0) Gecko/20100101 Firefox/38.0
 SeaMonkey/2.35
MIME-Version: 1.0
In-Reply-To: <list-1323643@2rosenthals.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Length: 2636

On 20/11/23 22:10, Gregg Young wrote:
> On Sun, 22 Nov 2020 14:54:14 +0100 Alfredo Fernández Díaz wrote:
>>
>> Hi
>>
>> On 20/11/22 00:28, Gregg Young wrote:
>>> [...] Hopefully fixed the flaky font loading in dialogues and menus
>>> that use non-codepage 850 codepages. I also at attempted to fix some
>>> bad string spacing/layout in the dialogs.
>>
>> Whatever you did seems to affect my English and Spanish VPC test systems
>> too -- and both use CP850. The 2.92 settings dialog displayed Russian,
>> Spanish and Czech characters just fine with the default system font
>> settings. 2.93 uses an ugly serif font for no reason apparently. See
>> screenshots.
>
> The global page isn't codepage 850. It is codepage 1207

Understood, my bad.

> and the only difference between 2.92 and 2.93 for that page is that the
> Times New Roman MT 30 font is 9 point instead of 10.

Maybe in theory, but I think the screenshots I sent show something different:

"Times New Roman MT 30" is a serif font, but the one displayed in the 2.92 
screenshots is clearly sans-serif (compare with the 2.93 image). Also, I just 
opened a test system, and in the palette font I can select "Times New Roman MT 
30" at 8 or 10, but *not* 9 points.

> While I don't like the
> font it is the only font that ships with OS/2 that has all the required glyphs.

The font in the 2.92 screenshots, the default on ArcaOS, seems to have them 
all. I just tested 2.92 on my working system, though (still running 2.71) and 
I see funny characters, so that one is not present here. Maybe some sort of 
fallback mechanism could be used so the ugly-looking MT 30 (especially as it 
is inconsistent with the rest of the dialog) is only used if the other one is 
not available?

Another alternative might be to resort to using the Unicode font for the 
drop-down list only, since it is the only component where several languages 
are used at the same time and it is actually necessary. I can drop fonts on it 
leaving the rest of the dialog unaffected, so this shouldn't be impossible to 
do programmatically.

>>
>> Also, I don't know whether your font code tweaking should fix the last
>> problem with the PM popup text -- it still looks bad here.
>
> This is unchanged from 2.92.

OK, never mind then.

> I looked at it and am seeing some very weird
> and inconsistent behavior. At times I get 2 different fonts for the top and
> bottom hint lines which shouldn't be possible. I will see if I can figure
>out what is happening. Thanks

FWIW, I see hint lines in 2.92 and 2.93 garbled in all new AOS systems, but 
they display just fine in my aging MCP2(!)

Thanks,
Alfred