Hiya Elli,
I see 4 obvious ways out to the problem. You may feel uncomfortable with all of
them but they could help you get a conceptual grip on how to deal with the
situation as a thought exercise.
1) Install FontForge (open source and free to use), open up the font in
question, and through a
Barney Carroll wrote:
I am incredibly pretentious ;)
You think you really have to tell us that, having already written :
there are no credible user personas who fire up Windows and Mac to make sure
their experience of a site has bitmap parity
???! :-)
Philip Taylor
Philip TAYLOR wrote:
Barney Carroll wrote:
I am incredibly pretentious ;)
You think you really have to tell us that, having already written :
there are no credible user personas who fire up Windows and Mac to
make sure their experience of a site has bitmap parity
???! :-)
I just though
On 12/24/2011 3:20 PM, david wrote:
Philip TAYLOR wrote:
Barney Carroll wrote:
I am incredibly pretentious ;)
You think you really have to tell us that, having already written :
there are no credible user personas who fire up Windows and Mac to
make sure their experience of a site has bit
> Hiya Elli,
>
> I see 4 obvious ways out to the problem. You may feel uncomfortable with all
> of
> them but they could help you get a conceptual grip on how to deal with the
> situation as a thought exercise
> 4) Accept that font-rendering APIs will always differ, and that there is only
>
> That's nice. How dose that help OP? And if the OP is not concerned about it,
> now... just why did she write about it in the first place? In my estimation
> the
> font in question remains a real-world problem and ignoring that issue for a
> reason that happens to be convenient at the moment
