QLineEdit, QTextEdit, and derived classes or the Quick TextInput item) and Qt's display controls (e.g. You usually don't have to worry about these features so long as you use Qt's input controls (e.g. Qt tries to take care of all the special features listed above. Common examples are the fl and fi ligatures used in typesetting US and European books. In special contexts, some pairs of characters get replaced by a combined glyph forming a ligature. Some languages such as Vietnamese make extensive use of these marks and some characters can have more than one mark at the same time to clarify pronunciation. Non-spacing or diacritical marks (accents or umlauts in European languages).The exact behavior is defined in the Unicode Technical Annex #9. Arabic and Hebrew are written from right to left, except for numbers and embedded English text which is written left to right. Line breaking can occur either after every character (with exceptions) as in Chinese, Japanese and Korean, or after logical word boundaries as in Thai. Some of the Asian languages are written without spaces between words. Many of these writing systems exhibit special features: On macOS, the following languages are also supported: On Windows, Linux and Unix with FontConfig (client side font support) the following languages are also supported: The list above is supported and will work on all platforms as long as the system has fonts to render these writing systems installed. All scripts in Unicode 6.2 that do not require special processing.Cyrillic languages (Russian, Ukrainian, etc.).All Western languages (using Latin script).All East Asian languages (Chinese, Japanese and Korean).Qt supports most languages in use today, in particular: The built-in font engine is capable of correctly and attractively rendering text that contains characters from a variety of different writing systems at the same time. All input controls and text drawing methods in Qt offer built-in support for all supported languages. Qt tries to make internationalization as painless as possible for developers. But to make a US application usable by Japanese users, or a Korean application usable by German users, will require that the software operate not only in different languages, but use different input techniques, character encodings and presentation conventions. In some cases internationalization is simple, for example, making a US application accessible to Australian or British users may require little more than a few spelling corrections. Kind a slow, but finally, I request a merge on GitHub minutes ago.Īdd Chinese Translation for CloudCompare by jindili Īdd Chinese Translation for the Main Window, Almost All Menu Item and Toolbar(Except some plugins) are translated.Internationalization support for text outputĬompares strings according to a localized collation algorithmĬonverts between numbers and their string representations in various languages OK, I'll go this way, after translate some more phrases ( at least the MainWindow menu and toolbar ), I'll request a merge on Github. I try Override some other translation with the same file name, and it works, the CloudCompare GUI is updated with my translation, Something more I need to do to activate my translation ? I test some simple phrase translations in the MainWindow translation context and release to qm file successfully, then copy to translations folder next to CloudCompare.exe and restart CloudCompare, but can't find new entry appear under menu "Display->Language Translation", I Found the ts files for translation here:Īnd a simple version of Qt Linguist which is small (13.1MB only, no need to install the whole Qt development bundle) and up to date(Released within a month) I would like to Localize a Chinese version,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |