MODx CMF

In modx0.9.6.2 uf8 languages files are named ".utf8" Except Russian.UTF8

Details

  • Type: Sub-task Sub-task
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 0.9.6.2, 0.9.6.3, Evolution-1.0.0-rc1, Evolution-1.0.0-rc2, Evolution-1.0.0
  • Fix Version/s: Evolution-1.1.0
  • Component/s: None
  • Environment:
    Modx0.9.6.2

Activity

Hide
Max Paprikas added a comment - 30/Jul/09 8:54 AM

Will be renamed after russian community create instruction how to upgrade from old versions.
And MODX-1024 will be fixed of course.

Show
Max Paprikas added a comment - 30/Jul/09 8:54 AM Will be renamed after russian community create instruction how to upgrade from old versions. And MODX-1024 will be fixed of course.
Hide
Ryan Thrash added a comment - 05/Aug/09 8:35 PM

If we're going to rename the languages, I think it should be done based on ISO standards including language and culture, e.g., pt-PT vs pt-BR ... or zh-Hans-CN (simplified chinese in script). See the RFC 4646 for more info:
http://tools.ietf.org/html/draft-ietf-ltru-registry-14

(It basically combines ISO 639-1 codes, region codes, and script styles)

This needs further discussion

Show
Ryan Thrash added a comment - 05/Aug/09 8:35 PM If we're going to rename the languages, I think it should be done based on ISO standards including language and culture, e.g., pt-PT vs pt-BR ... or zh-Hans-CN (simplified chinese in script). See the RFC 4646 for more info: http://tools.ietf.org/html/draft-ietf-ltru-registry-14 (It basically combines ISO 639-1 codes, region codes, and script styles) This needs further discussion
Hide
Max Paprikas added a comment - 05/Aug/09 8:47 PM

Definitely needs as soon as possible. (if we want to resolve this for 1.0.1)

Show
Max Paprikas added a comment - 05/Aug/09 8:47 PM Definitely needs as soon as possible. (if we want to resolve this for 1.0.1)
Hide
Ryan Thrash added a comment - 17/Aug/09 1:36 AM

Could we not just update the upgrade script for this case. In setup.sql:

UPDATE `{PREFIX}system_settings` SET
  `setting_value`='russian-utf8'
  WHERE `setting_name`='manager_language' AND `setting_value`='russian-UTF8';


UPDATE `{PREFIX}user_settings` SET
  `setting_value`='russian-utf8'
  WHERE `setting_name`='manager_language' AND `setting_value`='russian-UTF8';
Show
Ryan Thrash added a comment - 17/Aug/09 1:36 AM Could we not just update the upgrade script for this case. In setup.sql:
UPDATE `{PREFIX}system_settings` SET
  `setting_value`='russian-utf8'
  WHERE `setting_name`='manager_language' AND `setting_value`='russian-UTF8';


UPDATE `{PREFIX}user_settings` SET
  `setting_value`='russian-utf8'
  WHERE `setting_name`='manager_language' AND `setting_value`='russian-UTF8';
Hide
Max Paprikas added a comment - 18/Aug/09 3:01 PM

The problem is that some people (I think) use Windows for webserver.
As you know, windows don't recognize different case in the file name.
If user will make upgrade, and copy new files with overwriting, files will be overwritten, but they still will be uppercase.

Now, if we want to make autodetection (MODX-1071) work properly with russian, need to change case. (or add more checks into installer. that's a bad idea)

Show
Max Paprikas added a comment - 18/Aug/09 3:01 PM The problem is that some people (I think) use Windows for webserver. As you know, windows don't recognize different case in the file name. If user will make upgrade, and copy new files with overwriting, files will be overwritten, but they still will be uppercase. Now, if we want to make autodetection (MODX-1071) work properly with russian, need to change case. (or add more checks into installer. that's a bad idea)
Hide
Max Paprikas added a comment - 18/Aug/09 3:05 PM

I like this way:
ru_ru-utf8
en_us-utf8
or en_US-utf8

Show
Max Paprikas added a comment - 18/Aug/09 3:05 PM I like this way: ru_ru-utf8 en_us-utf8 or en_US-utf8

People

Dates

  • Created:
    01/Oct/08 3:22 PM
    Updated:
    05/Nov/09 12:40 AM