Follow-up Comment #8, bug #14577 (project wesnoth):
i am aware of that, though there are still things that i consider unclear
here:
a) two versions of Wes with *exactly the same* cairo DLL shouldn't produce
*completely different* font rendering results (compare screens from v1.6.1 vs
v1.7.6... the difference is big enough, and the cairo used in them is ==, both
by version and byte-wise),
b) so IMHO it's not cairo to blame here - as you can clearly see on
screenshots from v1.6.1, it WAS possible to render these fonts properly (at
least MOST of them, leaving the game playable) WITH cairo on w98+KE,
c) i can't provide any details about other platforms - the (almost) sole
reason for installing XP on my box was having it Wes compatible - i haven't
ever seen this bug on XP, though i'm not the guy who submitted this item;
sadly, he haven't supplied any details about his sys,
d) you can safely close this one if you're convinced that wesnoth font
routines are 100% percent correct and compatible, and the submitter of this
bug is a lone case /though it's strange - if he used 1.7.6, he should either
have almost no correct text with w98, so it seems to me he have used one of
the _supported_ versions of Win/ - it doesn't mean that much to me, and it
seems that there aren't enough reports ATM to do anything sensible here;
still, i haven't checked Wes font routines so far, but just in case i decide
to try checking them and _if_ i'm able to find a (clean enough) code solution
for this one, would you be interested in taking a look at it, or do you think
that it's a pure nonsense, with the idea to find a way of supporting
unsupported /and possibly obsolete/ OS silly enough by itself?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?14577>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
