So your problem is that the web browser you are using fails to display
all the glyphs? That sounds like an issue with that application. I
would think all main web browsers today would have proper font switching
support. That is, if the font they are using does not support a
specific glyph, they
On 03/10/2011 03:14 AM, Andersen, Jan wrote:
> So your problem is that the web browser you are using fails to display
> all the glyphs? That sounds like an issue with that application. I
> would think all main web browsers today would have proper font switching
> support. That is, if the font
"Andersen, Jan" writes:
> So your problem is that the web browser you are using fails to display
> all the glyphs? That sounds like an issue with that application. I
> would think all main web browsers today would have proper font switching
> support. That is, if the font they are using does n
This release fixes a longstanding crash on 64bit sparc, and a nasty bug
in the new XtAsprintf function added in 1.1.0.
Alan Coopersmith (2):
Incorrect cast in XtCvtIntToPixmap could cause bus error on 64-bit
machines
Don't need to use target-specific CFLAGS for makestrs
Cyril Brulebo
> I don't think fontconfig will solve the problem on its own. I think the
> application will actually have to do the job of switching between fonts,
> but fontconfig can provide some information to help the application do a
> better job.
fonctonfig provides the info for higher level libs (pang
"Nicolas Mailhot" writes:
>> I don't think fontconfig will solve the problem on its own. I think the
>> application will actually have to do the job of switching between fonts,
>> but fontconfig can provide some information to help the application do a
>> better job.
>
> fonctonfig provides the
