I have just finished all the Korean translations for the core s9y package
in the trunk. That includes the main language file, all the plug-ins, and the
Kubrick template which needs a separate language file. They're available
in the SVN trunk now, and should come with subsequent nightly snapshots
and eventually, 0.9 release.
When I started using s9y 3 weeks ago, Korean localization had been
effectively nonexistant. Now I believe it has the become on par with the
German and English versions for the package itself. With the translation
in place, I think s9y can cater to a wider audience - there have been very
few Korean folks using s9y at this moment probably due to the lack of
Korean support.
Serendipity now has full Korean language support
-
Col. Kurtz
- Regular
- Posts: 450
- Joined: Thu May 26, 2005 10:43 am
- Location: Bonn, Germany
- Contact:
-
Col. Kurtz
- Regular
- Posts: 450
- Joined: Thu May 26, 2005 10:43 am
- Location: Bonn, Germany
- Contact:
The name of the language itself is hardcoded, so it's not localized. Since it is
not a localizable string it shows up in English like that. I could attempt to
add additional routine in the plug-in (that language chooser is not a part of
the core plug-ins, btw) to work around the problem, but ideally the s9y's
code itself should be changed to handle localizations of the language names.
P.S. The names are hardcoded in serendipity_config.inc.php under the
$serendipity['languages'] array, so perhaps this needs to become dynamic
to language changes.
not a localizable string it shows up in English like that. I could attempt to
add additional routine in the plug-in (that language chooser is not a part of
the core plug-ins, btw) to work around the problem, but ideally the s9y's
code itself should be changed to handle localizations of the language names.
P.S. The names are hardcoded in serendipity_config.inc.php under the
$serendipity['languages'] array, so perhaps this needs to become dynamic
to language changes.
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
The major problem of "dynamic" language names is that we'd have to either hardcode all possible variations inside the file.
Because parsing all language files is a lot of overhead to perform! We can't open each file and look how the languages are defined there...
Regards,
Garvin
Because parsing all language files is a lot of overhead to perform! We can't open each file and look how the languages are defined there...
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
