|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Some font not localizable? - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
starr Member
|
It seems that Sisulizer ignores or does not recognize some font. You can reproduce the issue with 7zip's binaries. You can get it from sourceforge, then create a project using Sisulizer. The fonts of all dialogs are not shown, thus not localizable. Please inspect into it. Thanks. PS: I'm eager to see the upcoming release of Sisulizer 2008.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I downloaded and installed the application. Then I made a SL project of it's files. I was able to scan font rows on each dialogs. Just to make sure. By default the font type is excluded. You have to unexclude it. Have you done that? Could you tell which EXE or DLL file and which dialog had problems. Attachment: Fonts.PNG (Downloaded 38 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
starr Member
|
Thanks for the reply. I can take back the fonts now. However, I remember they were not excluded by default in previous builds, were they?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator
|
Yes they were. But the font needed to be translated so seldom that we put them excluded by default.
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
starr Member
|
I'm afraid I can't agree with you, sir. The localization between western languages maybe seldom needs the change of font, however, for eastern languages and middle eastern languages at least, it is almost always needed as the default (English/Latin) font does not include the target characters such as Chinese, Arabian. Thus I think it better to determine the exclusion by target language. Furthermore, the "excluded types" seem to have conflict in concept with the filter pane. That's to say, if I tick the font in the filter pane, the corresponding font setting should also be changed in "excluded types" protperties and vice versa. If not it will cause the same confusion as I reported. As you can see, if the font is initially excluded, there then does not exist the meaning for the filter pane as you can never see the font any more.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator
|
Yes, it is confusing that if the font data type is excluded it is still visible on the filter panel. I will change it that way that the check box is disabled (grayed). I will think abot the default value of font data types in different languages.
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
starr wrote: I'm afraid I can't agree with you, sir. The localization between western languages maybe seldom needs the change of font, however, for eastern languages and middle eastern languages at least, it is almost always needed as the default (English/Latin) font does not include the target characters such as Chinese, Arabian. Thus I think it better to determine the exclusion by target language. This depends on the platform. If you use VCL (Delphi or C++Builder) the font data also contains Charset property. In this case it is enough that charset is set to match the charset of target language. You do not have to change the font name but Windows is on run time choosing the right font. So if you run the application that had original MS Sans Serif the Japanese version still has MS Sans Serif but TFont.Charset is set (Sisulizer set this automatically) to CHARSET_JAPANESE. When you run Japanese application on Japanese computer Windows will actually use MS Micho. In this case it is actually wrong approach to ever try to localize the font becase MS Micho is the default Japanase font so the automatic conversion on run time ususally is better because XP and Vista might do it different way. The same is true for other Asian languages. My recommendation is not to localize font at all if you localize VCL applications. The automatic TFont.Charset done by Sisulizer is enough. For old Visual C++ font localization is need just as you told. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
banxian Member
|
font "MS Shell Dlg" in VC dialog resource items (or other Win32sdk applications) may have one of these behavior: display as same as DEFAULT_GUI_FONT (dynamic cast by MFC code self) display as same as default font in display properties -> Appearance (application use standard API like "DialogBoxParam", application don't check and replace font for every controls in dialog, dialog must have DIALOGEX type n DS_FIXEDSYS style n dialog haven't create as an page in comctrl's wizard dialog) in some conditions it cast to Microsoft Reference Sans Serif in some conditions it cast to Microsoft Sans Serif at last, it usually display as MS Sans Serif DEFAULT_GUI_FONT changed in different locale settings, it often cause an logic unit to pixel mismatch as design time layout, for eg, control text Must clipped in chinese or other language use fix width font as DEFAULT_GUI_FONT. sorry for my terrible grammar, I always use more than 3 verb words in an sentence. I think the second "as design" condition is a bit strictly. Programmers/coders/codetypers may simple wish there application looks as same in different end users' desktop, but in fact they can't control the codes not in their control as developer. Last edited on Sun Jul 6th, 2008 12:13 pm by banxian |
|||||||||||||
| ||||||||||||||
| Current time is 04:50 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Some font not localizable? | |
Sisulizer software localization tool - Three simple steps to localize
