|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > multi-line sections of a Helptext
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > multi-line sections of a Helptext
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| multi-line sections of a Helptext - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Gs Member
|
Hi, re. translation of Helpsource (H&M). I wonder, has treatment of multi-line sections in a helptext(xml) been changed lately in Sisulizer? We had our English helptext translated into Japanese. After building the translated .Chm, it turned out that several multi-line sections were displaying only the first line of such a multi-line item, despite the fact they had undisputably been translated in Sisulizer. Furthermore, after rescanning the source, multi-line sections that had been *split up* into subsections (attached picture, upper part) before, are now *together* in a single section (att, lower part). Though this probably means that the translation of such sections will now be complete, it also means that existing translations for the formerly separate parts are now lost! (or rather, Sislulizer regards them as 'Unused' which means effectively that they're lost..) I would like to know what may be the cause, and how I can handle this situation best?? TIA Gerard Attachment: multiline translations.JPG (Downloaded 23 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Please check Project - Edit Source - <your source> - Segmentation - Break each sentence of a paragraph into segments. It might be switched off accidently. Also check Tools - General Settings - Segmentation - Use segmentation with the following platforms. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, From build 307 Sisulizer doesn't use segmentation for rows with sub-tags, even if segmentation is enabled for selected source. It was implemented, because in some cases, changes in internal structure of sub-tags triggered on/off segmentation for sub-items in these rows. However, our R&D implemented in build 309 an option that forces Sisulizer to use segmentation even in the cases when there is formatting elements. See the screenshot. So with next build, Sisulizer schould revert all missed items in your project after checking this new option. Best regards, Janusz Attachment: Untitled.png (Downloaded 23 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Gs Member
|
Hi Janusz, Thank you! I was doubting myself already, because I don't think I changed the setting in the first place, and now, even after changing it explicitly ON, I couldn't get the segmentation back. So I await the next build eagerly and anxiously! When is it due? Gerard
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Gerard, Probably, it will come out this week, but only R&D knows details  .Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Gerard, One advice: Don't remove unused items from your project to until you update Sisulizer to next build - it probably simplify retrieving of your missed translations. Don't worry, if you already removed unused items, because probably your missed translations have been saved to Translation Memory (if you use default Sisulizer's settings) - you can find some additional info about in this http://www.the-localization-tool.com/?p=1587 article on our blog. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:40 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > multi-line sections of a Helptext | |
Sisulizer software localization tool - Three simple steps to localize
