12/30/2023 0 Comments Qt linguist macJust double-click on this program and follow the on-screen instructions. There you should find an installation program for Xcode. If you have a Mac with DVD drive and MacOS X system disk, you can start the installation by inserting the disk and opening the "Extras" folder on the disk. Now, let's start with the software installation process. Step 4: Installation of the C++ development toolsĪfter having downloaded the basic C++ development tools in the previous step the next step is to install the tools on your system, unless the download automatically started an installation. That, download and installation of Xcode should start automatically. Have to enter a valid iTunes / App Store account and password, but after The App Store page for Xcode, you can get Xcode by clicking on the "install" button. The Mac App store application and display the page for XCode. I haven't talked to any persons-who-are-translators yet, I don't know whether they track such things.Current version of MacOS X 10.6 (Snow Leopard) or higher this will start I think this is a bug in translation, not in the executable source, and QTBUG tracker for the component L10N (translations) is apparently not the right place. I will take it up on the mail list for translators. It really baffles me, but that might explain how some translator-person was fooled into thinking it was correctly translated. Decoding it by hand as UTF-8, I think the 4 bytes that should be just two bytes for U+00e7 (Latin small letter c with cedilla) definitely code for U+00c3 and U+0083 (the same wrong glyphs that you see either using Linguist or viewing the raw blob in a browser.) But I still don't understand how a browser to the source (not the raw blob) shows the correct glyph. ts file is XML and says at the top it is UTF-8 encoded. I used od (the octal dump tool) to inspect the file. qm file shipped with the version of Qt I am using (since the snapshot of the translations may not have been modified yet to keep up with any changes to Qt executables?) I think I am using the latest commit of qt_pt.ts, from gitorious the qt/qt repository (isn't that the snapshot?) Instead, maybe I should be using the stable. But I'm wondering whether it is about precomposed versus decomposed, see "here". I'm thinking that OSX uses UTF-8 and the translated strings are proper UTF-8. In a Firefox browser, the translation string for 'Preferences' appears one way (the correct way?.) Then open the 'raw blob' and it appears another way (as it does on OSX, with extra glyphs.) I think I could workaround by providing my own translation (in context MAC_APPLICATION_MENU) that is used ahead of the translator using Qt's qt_pt.qm file.īrowse to gitorious qt/qtranslations/translations/qt_pt.ts. But I'm not sure whether its a bug in the Qt library code or in the translations (which are provided by third parties.) I think it probably affects other strings in the qt_pt.ts file (not just for the Mac app menu.) I don't think it is a problem with the way I have configured my OSX, but it could be. Has anyone seen this, or can explain any ways to properly fix it? (I am not an expert at unicode issues.) For example, in Portuguese, it appears something like 'Prefer ncias' (where * represents a glyph), but I think the '' should display as one glyph (an 'e' with a 'hat' over it.) If you use git to doOn OSX, some languages, some items in the app menu are garbled (don't display with the proper glyphs.) For example, in Portuguese and French, the 'Preferences' item is garbled. The rest of this thread is of dubious value. What works is to git clone the qttranslations repository, and copy. For unknown reasons, that causes problems with Unicode strings. I had cut and pasted a qt_pt.ts file, from gitorious website to a file on my PC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |