[developers] [spr30362] bug using climxm
Andreas Fuchs
afuchs at franz.com
Tue Oct 10 15:16:28 CEST 2006
Hello Berthold,
Berthold Crysmann wrote:
>> thanks for your mail.
>>
>> Actually, my standard locale is en_GB.UTF-8. I have tried that now
>> --- with partial success.
>>
> 0. Opening the input widget for the first time, I get the following
> error message:
>
> Warning: Missing charsets: ISO10646-1, GB2312.1980-0, KSC5601.1987-0,
> creating fontset for
>
>
-alias-fixed-medium-r-normal--10-100-75-75-c-50-jisx0201.1976-0,-alias-fixed-medium-r-normal--10-100-75-75-c-100-jisx0208.1983-0,-adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso8859-1,
I have good news: The attached patch (to use, replace patch.lisp with it
and compile & load it before running your application) removes that
error message, along with these changes:
* Allows display/editing of Korean (and other international) characters
in climxm.
If a font is available for the required registry/encoding, it will be
loaded and available for text fields.
* Gets the correct string value from text fields containing
international characters.
* Allows the locale to be set via (setf excl:*locale* ...) or via
-locale on the command line. This makes the previous LET workaround
unnecessary.
It is still required that you use an allegro- and libc-compatible locale
specification. I'll work on the compatibility check next. In any case, I
recommend using a UTF-8 locale.
Good luck,
Andreas.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch-fonts.lisp
URL: <http://lists.delph-in.net/archives/developers/attachments/20061010/550dafce/attachment.ksh>
More information about the developers
mailing list