On Mon, Jul 23, 2007 at 07:55:46AM -0000, Michal Suchanek wrote:
> It think it is possible to add the current locale to the configuration
> file if it is an utf-8 locale.
Yes, it's possible. But in my opinion requires quite some amount of
work.
> However, I do not know what the format of the file is so I am not sure
> if this can be done safely.
The format is rather simple, just:
/SupportedUnicodeLocales = <list>
where list is a comma-separated list of all locales.
> Another option is to start scim in en_US locale if the current locale is
> not supported. This would be suboptimal if scim translation for the
> current locale exists, though.
This may not work. The locale of the application using scim is
important, too.
> Another option is to make a default config file the locales for which
> scim is translated, and use en_US otherwise.
How do you know which locales have scim translated when scim is using
the translations provided by language packs that come from Launchpad?
On Mon, Jul 23, 2007 at 07:55:46AM -0000, Michal Suchanek wrote:
> It think it is possible to add the current locale to the configuration
> file if it is an utf-8 locale.
Yes, it's possible. But in my opinion requires quite some amount of
work.
> However, I do not know what the format of the file is so I am not sure
> if this can be done safely.
The format is rather simple, just: nicodeLocales = <list>
/SupportedU
where list is a comma-separated list of all locales.
> Another option is to start scim in en_US locale if the current locale is
> not supported. This would be suboptimal if scim translation for the
> current locale exists, though.
This may not work. The locale of the application using scim is
important, too.
> Another option is to make a default config file the locales for which
> scim is translated, and use en_US otherwise.
How do you know which locales have scim translated when scim is using
the translations provided by language packs that come from Launchpad?
Ming
2007.07.23