|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Sisulizer and Delphi - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Barbara Member 
|
Hello, I would like to use Sisulizer for localizing a few Delphi applications. Most of them contain many identical dialogs and messages, that are not shared between applications (for example in form of GUI library) but are compiled into the binaries. I know that some GUI dll could solve my problem, but there is no time for redesign of the already existing software and therefore I have some question to you. I would like to have some possibility to find dialogs/forms that are identical for at least two binaries in a single Sisulizer project, and to mark only them as 'auto translate'. Does Sisulizer already have this feature? I don't want to use the 'standard' auto translate functionality of Sisulizer. So far I know, it translates all occurrences of the text, but it can be 'linguistically dangerous' in our case - the same text can have more than one meaning in some foreign language, it is strongly context-dependent, and therefore the translation should be different. Best regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Barbara, sorry, but while the context of your double dialogs is different Sisulizer does not know why it should handle them special. But nevertheless, the reason for any auto translation should not matter. Your editor has to take special care on any auto-translated row. That is his job before he sets the translation status to complete. Your situation is not different from a regular case. Your editor can use Sisulizer's filter to speed-up that work. If he filters for duplicate rows he sees them all at a glance. While you pay approx. a third for editing than for translation this even saves you money against not using auto-translation at all. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Barbara Member
|
Hello Markus, it is really nice that you wrote me an answer so quickly. Thank you. My problem is unfortunately still open. I probably wrote my question not as clear as it could be and therefore you couldn't understand my intention. I have a few Delphi applications that should be localized from German to English. Most of those applications contain many (!) identical dialogs (i.e. Delphi forms) and messages (in form of resource strings) compiled into the binaries - and only they should be 'auto translated'. All other texts should be omitted, even if their values are the same. I wish to have some possibility to automatically find identical dialogs and messages in a single Sisulizer project, and to mark them as 'candidate for auto translation'. Does Sisulizer already support this functionality? If yes - great! - where can I find it? If not - could you implement it please? You are right Markus when you write, that our translator should care about his job and that he should review all auto translated texts. But if there are many places where the same text appears, but with different meaning, the 'standard' auto translation of Sisulizer helps no more. The feature I already described could help to customize work with Sisulizer depending on the content of localized binaries - either you use full auto translation engine of Sisulizer or you enable the 'unit name based' translation. Best regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Barbara, I have to ask the developers if it is technically possible to add a feature that detects if two dialogs are the same while they are stored in different modules/binaries and handle them like their context would be the same. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Barbara Member
|
Hi Markus, thank you!  Kind regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Barbara, I have some good news for you: The developers like the idea. While it is basically a design glitch in your software it is also a common design glitch some other applications also have :-) The bad news: In the moment the are very busy fixing some urgent problems. I would not expect to see that feature in one of the next builds but hopefully before end of November. Don't nail me on that because it is a bigger change and needs some time to implement and test. Just enjoy if they can make it happen faster. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Barbara Member
|
Hello Markus Thank you all and I cross my finger for the developer team! Best regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
We will implement this feature by the end of the year. Most likely it will come in a month. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Barbara Member
|
Hello Markus, hello Jaakko, I would like to ask if the feature described above is already implemented? If not - when can I expect it? Are you going to release this functionality this year or rather in January/February 2008? If you could give me a precise answer to this question I would be very grateful - and my project leader too I still cross my fingers for the developer team! Kind regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator 
|
It is still under construction. We will release it by end of this year (2007). best regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Barbara Member
|
Hi Ilkka, thank you for the answer! Regards, Barbara
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Barbara Member
|
Hi together, let me first thank you for realising the feature "translate duplicates". Unfortunately we do not feel comfortable with this solution: a) The translator does not have a "compressed" view of the duplicated units. I.e. he cannot decide whether he has tested or reviewed an instance of a unit residing in an other project. b) It does not make much sense to pay the translator for the translation of duplicated units. So we need a reasonable way to count the words correctly. Any ideas? I repeat myself: we don't want to use bpls in out projects as we have some compiler options to handle product variants. As every delphi project contains the vcl and some number of third party components we think that duplicated translation resources are the standard case and the issue is of some importance for the translation software. Thank you in advance, Barbara
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Ilkka.Salmenius Administrator
|
Just to make sure. By default Sisulizer translates all duplicates. There is a more strict option that cheks also the context of a duplicate strings and accept only those which are identical. Have you set that option on? From Tools | General... menu Attachment: Duplicates.PNG (Downloaded 17 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Barbara Member
|
Hi Ilkka, yes, we found the feature. I think, I should give you a more detailed impression of our situation: We have 40 Delphi projects (dlls and exes), 2800 Delphi units, 550 forms. We have used sisulizer (and the translator Trados I think) to make an initial version of a translation. Now, we want to review the translation and I think we should use the visualization features of sisulizer for forms to do the first walkthrough and to add comments for the translator. Imho, the review should be organised delphi unit by delphi unit ---> wish A: It would be helpful to have a view of all strings which reside in one unit (resourcestrings together with form strings). Nevertheless, the main problem for us is that units are duplicated in projects. So every project uses e.g. the consts unit of delphi vcl which contains resourcestrings. And like that there are many other units especially our own code, too. In sum our 40 projects make 3800 unit references into units with translation resources (forms or resourcestrings). So if we step through the stuff, unit by unit, we don't know whether we have possibly reviewed the unit so far inside of an other delphi project. We could do it unique string by unique string, but then we have no translation context. The second consequence of the issue is that our translator tends to count these occurances of duplicates as internal repetitions which we have to pay for (reduced word price). But as it is the same unit in the same version there is no reason to have any effort with duplicated units which would justify a payment. Duplicated units are granted to have to be translated _identically_. ---> wish B: the explorer view of sisulizer should be organised unit by unit and every unique unit should occur only once. This would reduce the feeled project size. We even do not need any confirmation request from sisulizer to copy translations and changes into "instances of the same unit in other delphi projects". (If the delphi compiler doesn't give enough information to realize such an view it would not be a serious problem to provide config files which contain unit lists with form classes or the like, but we would not be able to configure such a view via a click gui.) I hope, this clarifies our problem, Best regards, Barbara Last edited on Thu Mar 27th, 2008 01:25 pm by Barbara |
|||||||||||||
| ||||||||||||||
| Current time is 04:57 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 > Sisulizer and Delphi | |
Sisulizer software localization tool - Three simple steps to localize
