Applications failing with Turkish locale

Generally default uppercase/lowercase implementation in class libraries/frameworks respect active locale’s behavior. Due to difference in handling of letter I & i [1] applications may fail when locale-aware case conversion is not desired such as parsers, generators etc. The general fix for this issue is to use an English locale in case conversion. I’ll give a few example bug reports.

  • A bug in java-gnome bindings generator I reported and its fix.
  • A Turkish locale specific bug in JAXB .
  • A bug I hit in Bazaar that hinders my bundle generation, merge process which only happens in branches with signed commits.
  • A bug in Exaile media player

I guess, I can give more if I google, but I think the above examples are enough to show why applications fail with Turkish locale.

1: http://www.i18nguy.com/unicode/turkish-i18n.html

Addition: I traced Bazaar bug to be really a bug in Python itself, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489740 for how Pardus and Debian fixed Turkish locale issues. Thanks to Jesus Rivero for quick follow up after my request of applying these patches in Gentoo. Hopefully they’ll soon be incorporated in portage.
Further Addition: Fixes are committed to portage by Ali Polatel. See bug #250075.

Advertisements
Posted in Gentoo. 4 Comments »

4 Responses to “Applications failing with Turkish locale”

  1. Tim Kosse Says:

    What a coincidence. I came across a similar problem today and also found that very same page on i18nguy.com

    My problem was that FileZilla did not display all toolbar icons, see http://bugs.pardus.org.tr/show_bug.cgi?id=7669 (page content Turkish)
    For the icons, FileZilla converts some string of the form “ART_SOMETHING” into “something.png”.
    The obvious but wrong way to do it would be to just lowercase the “SOMETHING” part.

    With Turkish locale, calling wxString::MakeLower (which internally calls the locale dependent towlower) on “SOMETHING” does not equal “something”.

    I only wish things like these would be better documented. Something like “This function is locale dependent” including a link to a page with detailed examples should be mentioned in every API documentation.

    Dotless uppercase I and dotted lowercase i are just too alien for most people to even consider possible unless somebody points it out to them.

  2. robbat2 Says:

    I’ve been bugging folk for years about code that wasn’t locale-aware for et_EE and tr_TR

    et_EE – collation order misses a bunch of letters, so that any regex like y/[a-z]/[A-Z]/ does not give the expected replacement on some letters.

  3. Serkan KABA Says:

    Thanks Tim Kosse I reported the issue to FileZilla bug tracker: http://trac.filezilla-project.org/ticket/4014

  4. Serkan KABA Says:

    I added an ebuild for the new release candidate for testing. All the icons apperar in the toolbar now. Thanks.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: