|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Truncation of text in .Net resources not shown by Sisulizer
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Truncation of text in .Net resources not shown by Sisulizer
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Truncation of text in .Net resources not shown by Sisulizer - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Olivier_ho Member
|
Hi, I'm currently evaluating Sisulizer for becoming our localization tool. During my tests, I encoutered a crucial problem : I have no truncation in a localized dialog in Sisulizer, but when running the software, the text is truncated. This is a .Net development, localized in the .resx file. I attached an image of both views (In Sisulizer, and in the software). Is it a bug, or is there a mean to make the .Net dialog box editor really WYSIWYG ? Thanks for any help on that matter - it is a very important element of our choice. Olivier Houdas. Attachment: PbSisu-truncation.gif (Downloaded 26 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi olivier, can you please send the .resx showing the problem and the source code it uses (e.g .cs or .vb) to support (at) sisulizer.fi (not .com). Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Olivier_ho Member
|
OK, done. I attached the whole C# .Net code. Note that Passolo shows the dialog as it's displayed later by the software, though (which tends to indicate it's not a localized-software-code-related issue).
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
We will take a look. If a competitor can do it - we also can :-) While there is one important difference. Sisulizer does all the rendering with own routines. This means, that your translator does not need the .NET runtimes to be installed on his machine and still has WYSIWYG for .NET dialogs and menus. This can avoid a lot of trouble! Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Olivier_ho Member
|
Well, I did need to install the .Net SDK in order to generate the localized .Net DLLs, though, when translating from compiled code. So now that I installed it, is there a means to use .Net runtimes/components, to get an alternate rendering of dialog boxes ?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Olivier, no, Sisulizer does not use the .NET runtime to render your dialogs. It has its own painting routines. This means, that you translator does not need to install .NET runtimes (what can be time consuming if he comes back to you to support him with that. A translators machine might be differently equiped than the machines of your target group) and still has WYSIWYG. There might be little flaws in the WYSIWYG depending on the project. But if we (or our customers) find them we work hard to eleminate them to have always true WYSIWYG. We hope to address your issue soon. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi Olivier, Can you take two screenshots where "Locator settings" dialog is show in English in - Visual Studio - Run time It seems that labelUse is rendered using two spaces between each word and I have not managed to figure out why. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
No need to send any screenshots. I figured out the reason. It is not the font issue or spacing. It is text rendering. .NET 1.0 and 1.1 used different text rendering that .NET 2.0 and later. This is why the same text on Label shows little bit different in .NET 2.0 and later than .NET 1.x. Sisulizer's visual editor is using similar text rendering as .NET 2.0 and later. This is why text .NET application using .NET 1.x is rendered little bit short. We will implement .NET 1.x compatible text rendering to visual editor. However this is not an easy job and we can not make it for the next build. Anyway it will come during one or two months. If you can compile your application for .NET 2.0 (e.g. use Visual Studio 2005) the visual editor of the current Sisulizer will render text correctly. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:48 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Truncation of text in .Net resources not shown by Sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
