|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Localizing AIR Help - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
EileenP Member 
|
We have been using Sisulizer to translate compiled HTML Help (CHM). But the newest help format is AIR Help, and we are considering switching to that. Has the Sisulizer team given any thought to supporting localization of AIR Help? If so, what is the status? When will it be supported? If/when it is supported, what about this situation: Say we have a help project with 300,000 words that we translated as CHM. Now we've switched to AIR, and we want to translate an updated project, say with 20,000 words changed. Will it be possible to re-use the original translation and only translate 20,000 words? Or would we have to re-translate the entire project? (We could not do that -- too expensive.) We are in the planning stages right now for future projects and updates, so it would be good to have some information about what now formats might be supported in future versions of Sisulizer, and when (approximately). Thanks!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Eileen, Just an general thought about switching between formated text like help files and HTML. Since formated text often contains links and text attributes it is likely that translations can not be re-used without a lot of manual work. The idea of HTML was to store text and format at different places. We all know that modern editors broke this good idea and add a lot of extra information to the HTML - just to make it look nice. Just think of MS Word and all the extensions it adds to a simple HTML file. If you keep the format into it is very common that a new system uses a different syntax for links or text attributes like bold or font size etc. If that happens no translation memory system can find a match. You will need some alignment tool to help the system to find the matches. And this is a lot of manual work. If you ignore the format info, then a system might find matches for the wording. But all the format information will be lost. It is a lot of manual work to add the lost format information to the translation. The situation is different for the strings used in software localization. There you have short strings without format info. So even if you change your platform (and the context link gets lost) it is very likely that you can re-use translations by value. In document localization you do not have a context and the "value" of the strings also differs significant between platforms. This is a general problem. I would recommend not to change the document format without a very good reason. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
EileenP Member
|
Markus, thank you for your reply. I realize that the formatting surrounding the text is quite different in an AIR file compared to a CHM file. If I understand you correctly, we will not be able to reuse the translations of CHM files and apply them to AIR files without a lot of manual work. Good to know! What about translation of a new AIR help project. Does Sisulizer have any plans to support localization of AIR (similar to current support of CHM localization)? Thanks.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, >>I realize that the formatting surrounding the text is quite different in an AIR file compared to a CHM file. If I understand you correctly, we will not be able to reuse the translations of CHM files and apply them to AIR files without a lot of manual work. Good to know!<< Yes, right. And this is not a Sisulizer but a general document localization problem. Never change a working system :-) >>What about translation of a new AIR help project. Does Sisulizer have any plans to support localization of AIR (similar to current support of CHM localization)? In the moment we do not have plans to support that. Air also means to support Flash. if you look to the Flash format you will see that it stores often not sentences or words but single chars. it is graphical oriented and every char can have own attributes and positions. Since that is extremely hard to localize our Air support could not be complete - so we did not put Air to our road map. Sorry for not having better news Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:22 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Localizing AIR Help | |
Sisulizer software localization tool - Three simple steps to localize
