|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| HTML Help tags - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
lagucw Member
|
(Firstly a minor issue - when creating a new HTML Help project, and browsing to select source file, CHM files do not show with "All supported files" or even "HTML Help file" selected. It has to set to "All files", select the CHM file, then select "HTML Help file".) My main problem is this - we have our English Help files created and mainitained by an external Technical Author. He also has a method for getting them translated by extracting text into Word, sending it to a translator, then somehow creating a new CHM file from this Word document. We want to bring the translation side of this process in-house using Sisulizer. However, when I create a project using the English CHM, and then import from the translated CHM, I lose about 20% of the translations. This appears to be because the HTML tags are different in the translated files (see sample of decompiled English and Danish files). Is there any way to ignore the tags so that I can import the translated text either into my project file, or into Translation Memory? Regards, Chris Attachment: 1 - HTML Files.jpg (Downloaded 10 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Sisulizer use tags syntax for creation string’s context, Sisulizer doesn’t import items with different context (in your case with different tags structure). Sisulizer for import from already localized files use always “By context” method and you can’t change it. Changing import method e.g. to “By value” is possible if you import translations from other Sisulizer project. MS Word is very bad localization and HTML editing tool. I think for HTML editing even Notepad is better, because WinWord completely change tag syntax without user knowledge. I think your translator should change his localization tool (maybe on Sisulizer?) Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
lagucw Member
|
Thanks, Janusz. It looks like we'll have to accept that when we transfer it over to Sisulizer, we will initially lose some of the translations. However, once we have done that, future translations will be done in Sisulizer and should carry forwards OK. Regarding the external Technical Authour and his translation method - yes, it seems that Word is a very cumbersome way to do it, which doesn't work very well! It also takes a long time and costs us a lot of money, hence the desire to handle it ourselves using Sisulizer! Thanks & regards, Chris
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:29 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > HTML Help tags | |
Sisulizer software localization tool - Three simple steps to localize
