[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Font encoding vs. string encoding
From: |
Sir Raorn |
Subject: |
Font encoding vs. string encoding |
Date: |
Wed, 17 Apr 2002 12:05:49 +0400 |
User-agent: |
Mutt/1.3.28i |
Going back to my problem with mostCompatibleEcoding, I've
looked into helvR12k.pcf
(-rfx-helvetica-medium-r-normal--12-120-75-75-p-67-koi8-r,
according to fonts.dir) and I saw, that CHARSET_ENCODING
really set to "1". This is surely font's bug.
I think best solution is not to use hardcoded mappings from
reg-enc to NSEcoding, but congurable dictionary like the
folowing:
{
"iso8859-1" = "NSISOLatin1StringEncoding";
"iso8859-2" = "NSISOLatin2StringEncoding";
...
"big5-1" = "NSBIG5StringEncoding";
"iso10646-1" = "NSUnicodeStringEncoding";
...
"koi8-r" = "NSKOI8RStringEncoding";
}
It can be a file named for example Font.aliases and located in
$GNUSTEP_ROOT/Libraries/Resources/Fonts. And of course it can
be overriden by user's config just like DefaultKeyBindings.dict
I can take care of it this weekend. Waiting for your comments
and suggestions.
--
Regards, Sir Raorn.
AIF5-RIPN, Binec System Administrator.
pgpK3aTxxd2g3.pgp
Description: PGP signature
- Font encoding vs. string encoding,
Sir Raorn <=