Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Harikalar Kutusu Friend
    #160456

    I know it is not a JA issue but those who need to live with it have lots of extra work…

    There is a known bug in CSS (in fact in unicode). See here for example: http://stackoverflow.com/questions/3777443/css-text-transform-not-working-properly-for-turkish-characters

    Just for you to understand the implications: sıkılmak (being bored) becomes SİKİLMEK (being f**ked)

    What is the point to use “text-transform=uppercase” so extensively? If someone wants to show it uppercase, so he/she does it writing it in uppercase! Is there anything that I miss here?

    I spend at least an hour to get rid of those definitions when using your templates and add-ons. If a module gets updated, just once again !

    Sorry for the rant, but I though you should know…

    Sherlock Friend
    #377691

    Dear bozden,

    I am sorry but I am not much clear on the issue,Do you mind explaining it in more details ?

    Harikalar Kutusu Friend
    #377773

    <em>@dathq 222812 wrote:</em><blockquote>Dear bozden,

    I am sorry but I am not much clear on the issue,Do you mind explaining it in more details ?</blockquote>

    I don’t know how I can be more clear :confused:

    The CSS files of the templates and extensions have too many “text-transform=uppercase” directives.

    And current implementations of CSS cannot convert some Turkish characters:

    Special characters in Turkish:

    small: ı i

    capital: I İ

    But the conversion done by “text-transform:uppercase” is as follows (same applies for “capitalize” if first letter) :

    capital: İ I (quite the opposite)

    or in some browsers/language settings:

    capital: I I (both same)

    And this can make awkward changes in meaning of words. There are also issues in other languages like Dutch.

    This is true for any browser implementation, independent of language selection (not tried all combinations thou)…

    We, those who design websites in Turkish, have to search all CSS files and inline CSS to get rid of the “text-transform:uppercase” definitions.

    Of course you are not responsible from this bug 🙂 This is not your problem, but I thought that you should know.

    Please make use of this “feature” less…

    Sherlock Friend
    #377858

    Dear bozden,

    Now I am quite clear on the issue,I will inform the issue to our designer and I hope this would help them improve their works in the near future .:)

    Harikalar Kutusu Friend
    #377926

    Thanks 🙂

    Keep up the good work…

Viewing 5 posts - 1 through 5 (of 5 total)

This topic contains 5 replies, has 2 voices, and was last updated by  Harikalar Kutusu 13 years, 8 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum