|
|||
|
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) > Usage - Three simple steps to localize > Difference between the built in translation memory and the tmx file
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Difference between the built in translation memory and the tmx file - Usage - Three simple steps to localize - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
miber Member
|
hello Sisulizer, Im reviewing your application for the company im working on. Wh have mixed development environments, Delphi and Visual Studio (C++ and C#). I have tested a couple of scenarios with your application (professional) and it seems promising. Some questions though: Why use the built in translation memory?, seems one have much more control with exporting/importing tmx files, which can be source controlled. I have tested to recreate sisulizer projects by adding the Exe + drc and the importing the tmx-file and it works nice. Do you have some recommendations for work flow and usage, i mean for instance, is it ok to work like this: 1. Developer implements stuff and sends a translation project to the translator. (tmx file is source controlled) 2. At the same time the translator works, the developer continue implementing stuff. 3. The developer gets the translation. Starts with recreating a sisulizer proj from exe + drc + tmx file. then merges the changes from the translator. Finalizing with a update of the tmx source controlled file (export). Best regards /Mikael
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Mikael, it is pretty easy. a) You scan your project or binary with Sisulizer b) You create a translation package and give it to your translator. He uses the free translation edition c) You continue your coding d) The translator sends back his translations e) You import them back into your project f) You compile a new binary of your product g) now you use Project - Scan for Changes. Sisulizer finds all new and changed strings. All strings who are the same are automatically re-used. No need to export and import them to a TMX. h) You create a translation package and give it to your translator. You can either export only changed and new rows or all rows and your translator can filter for new and changed rows. Take a look at http://www.sisulizer.com/swf/sisulizer-scanforchanges.shtml to see an animation of the great Scan for Changes feature of Sisulizer. TMX and TM are only needed if you want to transfer translations between two independend projects (Product A + B) where Scan for Changes can not be used. TM is also useful as a sort of a backup. With Sisulizer it is very easy. Other products might have more complicated processes to do the same or have at least fancy names like translation leverage. Btw: The Sisulizer project file .slp has the structure of a XML file. It can be part of your source control. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
miber Member
|
Hi Markus, Thanks for quick reply, yes its actually very easy. It works soo smoothly one wonder whats the catch? :-). My main concern here is the source control and back up of the translations. Soo i guess your recommendation is to source control the slp file? One question more, although i think its not a major issue. How about if the translator resizes captions for instance (to fit longer strings) or move controls, is there any possibility to catch that in the original source code? Thinking about using this software for some years, translators can move around things so theres no resemblance anymore to the original code. Best Regards /Mikael
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Mikael, >>Thanks for quick reply, yes its actually very easy. It works soo smoothly one >>wonder whats the catch? :-). why make it more complicated than it needs to be. You are already busy learning APIs and namespaces and a localization tool should not add extra problems to your workload. >>My main concern here is the source control and back up of the translations. Soo i >>guess your recommendation is to source control the slp file? Yes. That is a good idea. And from time to time you could write to the build in TM and also back up the database files. >>One question more, although i think its not a major issue. How about if the >>translator resizes captions for instance (to fit longer strings) or move controls, is >>there any possibility to catch that in the original source code? Thinking about using >>this software for some years, translators can move around things so theres no >>resemblance anymore to the original code. It is a golden rule that Sisulizer does not change the source code. So there is no way to import the positions of the moved controls to the original. But if you get used a little bit to localization you will find some strategies to avoid the need to move or size controls in Sisulizer. One of the is to place labels above input fields instead of above. This article gives you some hints: http://www.sisulizer.com/support/developers-corner/preparing-delphi.shtml. The article is for Delphi but it should give you the idea. In Sisulizer I do the German translation for Sisulizer itself. German is well know to have long sentences. Neverthless Sisulizer is organized in such way that strings to long are very rare. If I find one of the rare places I do not move or size the controls but let the developers know about the missing room. Sometimes they ask me to find shortened wording if the dialog would become ugly. This way the developers have full control over the look of the dialogs. This is just one possible strategy. It works because our developers followed their own hints in the article :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
miber Member
|
Thanks for quick answers! I like your product, couldnt imagine there was something like it. previously i have been working with applications using ini-files, and now the code gear ETM/ITM, which i dont like as it mixes code and translations and always forces a rebuild of the duplicated dfm-files whenever anything changes (language change or not). I will continue testing your product and see if we can use it also for our Visual studio projects.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
>>I will continue testing your product and see if we can use it also for our Visual >>studio projects. You will be able to use it with Visual Studio! If not we want to see a post here in the forum so we can help you :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
miber Member
|
Hello again, one question came up. I have amde an exchange project to a translator, and there i select which forms should be included for the translator. But does this have to be selected again for each new excahnge? or could i save the exchange configuration in some way?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
miber Member
|
Also,.... Do i have to exclude those rows that shouldnt be visible to the translator? Now i have set them to "Do not translate" and thats fine, translator can not do anything with them, but still he see's them and the amount can be confusing, better to only show those items that should be translated.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Mikael, you can filter the "do not translate" rows our if you use the Exchange Expert. Please look at the screenshot. Best Markus Attachment: donottranslate.jpg (Downloaded 16 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
miber Member
|
Hello, yes i know about the filter and it works soo that you can set editable or not, but i would also like to exclude as much as possible (not visible) for the translator. Also i woulf like to save the exchange configuration.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Mikael, I see. I asked the developers if it is possible to save the settings. Perhaps you make a feature request in the section: "Wish list for software localization tool". Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
miber Member
|
Hi Markus, Ok, thank you Regards /Mikael
|
|||||||||||||
| ||||||||||||||
| Current time is 02:37 am | |
| 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) > Usage - Three simple steps to localize > Difference between the built in translation memory and the tmx file | |
Sisulizer software localization tool - Three simple steps to localize
