|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Converting Multilizer to Sisulizer - Do not translate lost
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Converting Multilizer to Sisulizer - Do not translate lost
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| Converting Multilizer to Sisulizer - Do not translate lost - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
psantaana Member
|
Hi: When I convert a Multilizer 6.2 project to Sisulizer 2008, all the units that were marked as "Do not translate" (showed as white and dimmed in the left tree in Multilizer) are not equally marked in Sisulizer. So I have to mark one by one by hand. The same occurs with the strings. All those strings marked as "Do not translate" in a unit (some strings must be translated and other don't in a single unit) are imported without this state and must be marked manually. Is there any way to import this state all at once in strings and units alike? Thank you… Pablo.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
This is a bit difficult to implement because Sisulizer and Multilizer uses different context values. Sisulizer does can not map Multilizer's context to Sisulizer's context. However if the excluded strings in your Multilizer project are not per context but values we can implmenent that. Can you send me your Multilizer project (.mpr) and your original files (.exe?) that you have included to .mpr. I will check/implment the feature. Send files to support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Jaakko.Salmenius wrote: Can you send me your Multilizer project (.mpr) and your original files (.exe?) that you have included to .mpr. I will check/implment the feature. I've those files, and I'll forward it to you. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
psantaana wrote: Is there any way to import this state all at once in strings and units alike? I implemented this in 279. Now Sisulizer also import Do not translate status of nodes when you open a Multilizer project (.mpr). The new build will be available in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
psantaana Member
|
Hi Jaakko: Thank you, very much. I'm downloading the new version, right now. Regards... Pablo.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
psantaana Member
|
Hi Jaakko: It's me again. Sorry to bother you.  I installed the new version. It worked great with the units: now the "Do not translate" marked units in Multilizer are imported as "Excluded" in Sisulizer. Nevertheless, the also "Do not translate" marked rows are not "Excluded" nor "Do not translate" marked. They just appear as "Not translated" status. Is this correct?  By the way, can you explain me the difference between marking a row/unit as "Do not translate" and "Exclude" (beyond the obvious: that one has a padlock and the other disappears  )? Are these statuses useful when you send the project to the translator? I would like to know the right use of these two options.Thank you for your patience...  Pablo.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Pablo, I’ve still your Multilizer project, so I’ll check statuses issue with new Sisulizer build and let you know about my observation after test. By the way, can you explain me the difference between marking a row/unit as "Do not translate" and "Exclude" Row with “Do not translate” status is not editable (read only) but is still visible in translation sheet. If you translated string before checked it as “Do not translate”, this translation will be used in output file, but you can’t edit it. If you will mark row as “Exclude”. This row will be completely excluded from translation sheet and row will be invisible in sheet. You could use following exclude features: - Exclude by originals: you could to exclude items from the project by the native value. - Exclude by rows: you could to exclude items from the project by the value of the context - Exclude by strings: you could type in “Project” menu > “Excluded strings” dialog window custom strings to exclude from project. The strings can contain wild cards (* and ?). Similar dialog you could to find in General settings where you could specify strings to exclude from all your project. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Excluding rows has the advantage that the Sisulizer project becomes smaller. If you exclude for example complete data types like pictures (which are rarely localized) you may reduce the size of the .slp dramatically. "Do not translate" keeps them inside the slp and - as Janusz said - make them read only. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Sebastien Auvray Member 
|
Hi ! About this 'Exclude feature', which removes items from project sent to translators... I generate .Net resources files from Sisu. Are the excluded items also excluded from the generated resource files, which would force .Net to fallback to default value when setting culture ? Or must I manually copy original translation for each item ? Thanx, Sébastien.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
About this 'Exclude feature', which removes items from project sent to translators... I generate .Net resources files from Sisu. Are the excluded items also excluded from the generated resource files, which would force .Net to fallback to default value when setting culture ? Or must I manually copy original translation for each item ? That depends on your .NET resource source settings. If you open source properties dialog for .NET source (e.g. for .resx file), you can find item named “Items that localized resource files contains” in “Options” tab. This option has 3 different settings: Different - Excluded, not translated item: output .resx file generated by Sisulizer doesn’t contain this item - Excluded, translated item: output .resx file generated by Sisulizer doesn’t contain this item Translated - Excluded, not translated item: output .resx file generated by Sisulizer doesn’t contain this item - Excluded, translated item: output .resx file generated by Sisulizer contains this item and uses original value All - Excluded, not translated item: output .resx file generated by Sisulizer contains this item and uses original value - Excluded, translated item: output .resx file generated by Sisulizer contains this item and uses original value Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, By default .NET makes a fallback if there is no translation. Please remember that there is a difference between (empty) and "". Empty means that an empty translation should be used while if the cell in the editor does not have a translation the fallback is used. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear all, I have the same problem as psantanaa: The "Do not translate" Status of rows is lost on import. Is there now a solution? Thanks, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
The problem most likely is when Sisulizer import Multilizer project file it does not import by context but by value. I can check if I can implement importing of Do not translate status. Can you upload me your Multilizer project file (.mpr) and your Sisulizer project file (.slp) Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear Jaakko, I uploaded the two files. Thank you in advance. Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the file. I have hard time to find a locked/read only item in your Multilizer file. Can you tell me one place where it is. If you can tell me the original string of teh locked row I can pinpoint the item. Can you also send me the .exe file where the locked row belongs. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I foudn it. Multilizer 5.x used NOTRANSLATE element to mark them Do not translate. Can you send me CP_ProfileEditor.exe Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
psantaana wrote: When I convert a Multilizer 6.2 project to Sisulizer 2008, all the units that were marked as "Do not translate" (showed as white and dimmed in the left tree in Multilizer) are not equally marked in Sisulizer. So I have to mark one by one by hand. Can you upload me your Multilizer 6.2 project file (.mpr), Sisulizer project fiel (.slp) and your original file (.exe?) I will implement importing of the "Do not translate" status. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Excellent news! I just uploaded CP_ProfileEditor.exe.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the file. Next build (296) imports "Do not tranlsate flag" from Multilizer 5.x files. Note! This fearture is only when importing from Multilizer 5.x files. If you import from 6.x Sisulizer does not import the flag. I can implement it there too but in order to do that I would need a Multilizer 6 mpr using locked rows. New build will come out in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear Jaakko, I really appreciate your excellent and fast support - thank you! Christine
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:30 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Converting Multilizer to Sisulizer - Do not translate lost | |
Sisulizer software localization tool - Three simple steps to localize
