Aric Stewart wrote:
> > What value does Mac return for these kind of fonts? Does it take an abs()
> > like in your patch? Does it trancate the value? Does it calculate it somehow
> > (like taking an average of glyphs say a+z and A+Z)? Does it do something
> > different?
> >
>
> Why dos it matter
On 2/21/12 10:17 AM, Dmitry Timoshkov wrote:
Aric Stewart wrote:
>>> what Mac does in that case?
>> The mac handles the fonts without issue
>>>Why do you think that your fix is correct?
>>..windows tmAveCharWidth should never be negative, and yet this logic
>> causes it to be s
Aric Stewart wrote:
> >>> what Mac does in that case?
>
> >> The mac handles the fonts without issue
>
> >>>Why do you think that your fix is correct?
>
> >>..windows tmAveCharWidth should never be negative, and yet this logic
> >> causes it to be so for these fonts. If we want to be able
On 2/21/12 10:03 AM, Dmitry Timoshkov wrote:
Aric Stewart wrote:
So, what Mac does in that case? Why do you think that your fix is correct?
The mac handles the fonts without issue. The issue appears to be that
the windows tmAveCharWidth should never be negative, and yet this logic
causes it
Aric Stewart wrote:
> > So, what Mac does in that case? Why do you think that your fix is correct?
> >
>
> The mac handles the fonts without issue. The issue appears to be that
> the windows tmAveCharWidth should never be negative, and yet this logic
> causes it to be so for these fonts. If we
On 2/21/12 9:39 AM, Dmitry Timoshkov wrote:
Aric Stewart wrote:
Windows response appears to not allow the user to install the fonts at
all. It reports any of the fonts I have which have negative OS/2
xAveCharWidth as invalid fonts when I try to install them.
This blocks out a few of the main
Aric Stewart wrote:
> Windows response appears to not allow the user to install the fonts at
> all. It reports any of the fonts I have which have negative OS/2
> xAveCharWidth as invalid fonts when I try to install them.
>
> This blocks out a few of the main Mac UI fonts.
>
> -aric
>
> On 2
Windows response appears to not allow the user to install the fonts at
all. It reports any of the fonts I have which have negative OS/2
xAveCharWidth as invalid fonts when I try to install them.
This blocks out a few of the main Mac UI fonts.
-aric
On 2/20/12 10:49 PM, Dmitry Timoshkov wrote
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17047
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17046
Your paranoid android
Maarten,
what does the patch fix?
I did leave nChannels equal to what GetMixFormat returns based on the following
reasoning:
- It'll probably suggest a mono format on an old machine that handles mono
only, so leave as is.
- It may suggest 6 channels on a 5:1 card (we had a few such reports on
André Hentschel writes:
> @@ -1,10 +1,9 @@
> EXTRADEFS = -D__WINE__
> MODULE= winefile.exe
> -APPMODE = -mwindows -municode
> +APPMODE = -mwindows -municode -mno-cygwin
You can't do that, winefile wants Unix filesystem calls.
--
Alexandre Julliard
julli...@winehq.org
12 matches
Mail list logo
