Custom Query (301 matches)
Results (52 - 54 of 301)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #123 | fixed | Derive language settings from the system | ||
| Description |
Currently, Qt relies on the LANG environment variable to detect the country and language of the system locale. This information should be rather taken directly from the system. |
|||
| #132 | fixed | Designer refuses to load ui file produced with QtCreator on Windows | ||
| Description |
I tried to load some ui files that were created on Windows (QtCreator? 1.2.? / Qt 4.5.2). The smaller one could be loaded by the OS/2 version of designer. However, when trying the larger one, I got: "The file <xyz> is not a valid *.ui file". followed by another box claiming: "An error has occurred while reading the ui file at line 1, column 1: Start tag expected." However, the file looks perfectly O.K. to me. |
|||
| #49 | fixed | Detect locale properly | ||
| Description |
String conversion functions depend on the locale. Currently, the locale is derived (as on Linux) from the LC_* and LANG environment variables. However, LANG may absent from the environment on OS/2 systems in which case we should derive the locale from the current code page of the process. The second problem to solve is the ru_RU locale. According to the standard, if the code page number is missing from the locale definition, it's 8859-5 for ru_RU but it's obviously makes no sense on OS/2 where it should be cp866 if not specified explicitly. |
|||
