Follow-up Comment #1, bug #18177 (project gnustep):
Is this the current stable release or unstable(svn trunk)?
If the latter, then I guess it could be a host/locale specific problem
ralated to a recent change to handling mapping of font registry to string
encoding. I thought that the new mapping included all the old mapping values
as a subset, but maybe not.
It would be useful to have a backtrace showing where the problem originates,
and if it's in [XGFontInfo-setupAttributes] you could try enabling debug
logging (start the app with --GNU-Debug=default) and see what it logs for
this (messages of the form 'Found encoding ... for ...').
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18177>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
