|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer doesn't import new translations
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer doesn't import new translations
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| Sisulizer doesn't import new translations - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Chris B Member
|
I have a main slp project with 6 different translations. I received slps from translators with new translations, imported them, compiled out chms and the chms in the foreign languages looked good. I updated to Build 309 yesterday. I noticed some small errors that I needed to correct in the original chm so after I did that I scanned for changes and compiled a new chm in Swedish. There were 230+ "not translated" strings! When I compared the newly compiled Swedish chm with the first, there were many topics that were in English, that were previously in Swedish. So I somehow lost my changes. I then tried to import the Swedish only slp into the main project. I tried once and somethings were imported but many "not translated" strings remained. I tried one more time, making sure the Import settings were OK. But this time Sisulizer says "no translations imported"?! So now I can't seem to get back/reimport my lost translations even though they are clearly translated in the Swedish-only slp. I wonder how/when/why they disappeared, if the build 309 is to blame, and why I can't even import them now? I will upload my current main project file and the Swedish one.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Chris, Before you upload any files please load this blog article: http://www.the-localization-tool.com/?p=1689 I think that will solve your issue. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Chris B Member
|
I was already using build 307 when I imported the first time, and why would upgrading to 309 simply delete previously translated strings?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Have you checked your segmentation settings before your retried to import? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Chris B Member
|
I read the article and still don't know what I am supposed to do? I have an existing project where lots of translations disappeared. If I turn ON segemenation I get even more Not translated strings (Should be 0, was 230 after I updated and now up to over 800 when I change segemenation.) What do I do with an existing project?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Chris B Member
|
Before I upgraded yesterday I had build 307 and all the translations were fine. I upgraded to 309 and lost 230+ translations. I have tried to import today one before reading the article and nothing happened. Sisulizer won't recognize the changes. After reading the article and switching ON segmentation I imported again and lost even more translations. Can you give me a concrete suggestion? Before "upgrading" (which shouldnt cause such issues where translations simply disappear.) the project was fine. I didn't want to import new files.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Either the segmentation setting was different while you made the scan for changes or your changes to the original chm changed the context in a way that Sisulizer could not make the matches. In any case you should also have unused items. Make a copy of your slp. Don't remove unused items and change the segmentation settings. Then do scan for changes. If it was just the segmentation settings then your translations should be restored. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Chris B Member
|
I actually made a copy of the slp yesterday before I made any changes to the original chm. Looking at that file now, the Edit source settings are set to "Do not use segmentation." Whether I change this or not, and rescan, my translations are not restored.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Chris B Member
|
So, let's assuming I am ready to lose 2 days' work. I have my slp with missing translations in 6 different languages AND I have 6 seperate slps with all the strings translated in the different languages. What then? How can I get Sisu to see the translated strings when I import?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
That sounds like your structure of the chm has changed. Did you recently update your tool to create your chm files? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Do you have the CHM at the time you created the SLP/SLE you gave your translators. You should first import the translations you got from them. The structure and the segmentation should be the same. Do not use Scan for Changes and also do not build the project since it also does a Scan for Changes. After you imported all strings to the old SLP - now with all translations - you should retry Scan for Changes to update the project to the changes in your new CHM. Btw: have you checked for unused items? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Chris, I recommend you read also this http://www.the-localization-tool.com/?p=1096 article. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Chris B wrote: I will upload my current main project file and the Swedish one. Chris, upload these files. I'll have a look at this. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Chris B Member
|
Hi guys, Monday mornig and back ready to deal with this again. I uploaded those files on Friday. If you haven't gotten them I can do it again. There are a few different problems here: 1)I lost 200+ translations first. When I change the segmentation settings mentioned in the build 309 article, I ending up losing 500+ or 800+ translations, depending on whether segmentation is on or off. So that doesnt help me. 2) I should point out that BEFORE I "upgraded" to build 309, all the translations were fine. I only tried to import the original translations again as a method of getting them back, but I should NOT need to do this. When i checked the compiled chms files that Sisulizer produces, the all the 200+ strings ARE translated in the original but NOT in the build 309 version. 3) Yes, I did make some changes to the source chm, but this is AFTER this issue (they are unrelated.) After scanning for changes here my originally translated strings are still missing but were NOT missing previously. My biggest issue is that I cannot simply lose 200+ strings just by upgrading?! The article is fine, but if something like that can happen the user needs to be told when installing. I am totally stuck now.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, No, we haven't gotten these files. Could you upload it again? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Chris B Member
|
I have uploaded them now.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Thanks, we received your files. Unfortunately, I came down with ugly flu , but nevertheless I'll try check it.Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sorry for delay, but yesterday I felt very bad. I performed today some tests and below are results: Your main project (with 20207 items, 112 not translated items) do not use segmentation, while Swedish project (with 17260 items, 2 not translated items) use segmentation. For this reason I changed segmentation settings in main project for your both sources from "Do not use segmentation" to "Use segmentation also with rows that contains sub tags". Then I rescanned project, and removed unused items. After these operations I've got 19809 items and 341 not translated items in your project. Next, I imported (not changed) Swedish project with "By context first then by value" import method and overwrite method as "Always". After import, in main project remained only 5 not translated items, but these items doesn't exist in Swedish file (probably this is result of updates in sources). Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I have the same results with the changed segmentation rules in the master project. Perhaps it is needed to say that, since the project covers two sources, the setting has to be done for both of them seperatly. Segmentation does really make the difference in documentation localization. It is often a cause of trouble between two translation memory tools having different ruls. And different rules is very common. Every tool has its own philosophy. In software localization it is not very much needed since there is in almost every situation (except e.g. list box contents) a unique context. Online help on the other hand is document localization and there isn't a trustable context for every sentence. The links between original and translation have to be done by value of the original segment of a string. If the original segment get changed the link is broken. In Sisulizer's import wizard you find some important option that allows to use a context nevertheless in case the structure of the file was unchanged since originally scanning it. Optionally it also checks if the value is also the same (highly recomennded) - which makes the perfect link. This is a huge advantage above traditional translation memeroy tools. For edited documents only the by value can be used - remember, that is the best method a document localization tool can offer you. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Below you see the option that allows to use the context while importing documents which do not have a unique id for every element. If you have e.g. two <p> tags in an HTML document and you add another <p> before these the context of the two changes. Old <p>one</p> // ID p(1) <p>two</p> // ID p(2) New <p>new</p> // ID p(1) <p>one</p> // ID p(2) <p>two</p> // ID p(3) If you would trust just to the context a big mess would be the result. Here the value comes into play. If the old p(1) content does not match the new p(1) after Scan for Changes Sisulizer knows the context must be changed and by value (one) has to be used instead. In software localization each resource also stores the id with the value. In HTML all you have is the tag's type and the order of the tags. Markus Attachment: 0041.jpg (Downloaded 18 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:33 am | 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 > Sisulizer doesn't import new translations | |
Sisulizer software localization tool - Three simple steps to localize
