|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 3 4   |
|
|||||||||||||||
| Release 282 doesn't find textfields in database - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Matthew Member
|
Hello, are the errors still under investigation?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Yes. We have a long waiting list in support plus it is holiday time. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Any news? We still are not able to use any Sisulizer version newer than 278.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Any news? We still are not able to use any Sisulizer version newer than 278.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hello, today I tested the Sisulizer version 303 with the described scenario. Now Sisulizer recognized all but one field correcty. But my data are not all read. Only about 3000 out of 11000 strings are loaded from the database. We use a Microsoft SQL Server (SQL Express on the local computers). What do you need to reproduce the error?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Can you please upload a SQL script that creates the database incl. the data rows. Please zip the script and use the private upload button. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
As additional information to the uploaded script: In the table 'CostElementDefinition' the texts 'CategoryDisplayName_DE' , _EN and _FR are not recognized as translatable columns. All other entities (_DE, _EN, _FR) are correctly recognized. As for the more severe bug: From the first two tables all data in the table 'Accuracies' are updated but none is updated in the table 'CalculationMethods'. As I said: from 11000 translatable strings only 3000 are loaded and updated. If you need the data also, I could send you a backup from our database. You only have to install MSSQL-Express (free edition).
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Have you been able to reproduce the error? Is there any possibility to circumvent the error concerning the missing data?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hello, can you please give me an estimation when or if you are able to look after the described error?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, I just asked our R&D today about the status. It is not forgotten. We are just pretty busy at the moment. Sorry for any delay an inconvenience. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Today, I checked the new Sisulizer version 305, it delivers the same errors as described in my last posts. This time, I attached a screenshot of the errors when scanning the database. Maybe it helps for you to reproduce the error. If you don't have time to fix this error, I thought of another possibility to solve this problem: We could read the database content with a little tool / srcipt and save it in a file. Sisulizer could translate this file and we could update the database via a script. What file format would you recommend for such a solution? Attachment: Sisu305_DbError.png (Downloaded 68 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, Sorry for the delay in fixing your issue. Database problems are always a bit harder to fix since we need to reproduce your database situation etc. Our R&D promised to take care after we released V2010 - which was this weekend. So there is hope now :-) If you want to go for a workaround I would recommend the XML format since it is UTF-8 by design and might protect you from code page problems. If you want to go the perfect way I would recommend the XLIFF format. This is a standard format used to exchange translations between localization tools and applications. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Thank you very much for your reply. This helped a lot. We can wait a little while for your developpers to resolve the problem but now we have an alternative if they have other priorities.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Hello, Over a year ago I convinced my boss to change our localization tool from Catalyst to Sisulizer because I was really enthusiastic about Sisulizer because it did what I would expect from a localization tool (coming from one that didn't). The problem with Catalyst was not so much that it had bugs but that no one would fix them. We told the people at the hotline the bugs of their tool but for over a year not a single one was fixed. You at the other hand had a very quick response to our problems. Every single issue we had was addressed in less than a week often after less than 3 days. This was awesome! All issues but one, the one in this thread. I would like to understand, why it is almost a year now that I gave you all the means to reproduce this error but nothing happened. Don't get me wrong, I am really thrilled about your program and I recommend it to other programmers in my network when it comes to translating recources. But not for translating database contents and that is a pity because as far as I can see it is a minor bug that would be easy for you to fix but it prevents us from using Sisulizer as we would like to.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, We are very sorry that we lost your case from our support radar. I gave it another push and I hope this time it will see some progress. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, We made some first tests and we now found that we need the backup of your database to reproduce that. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. Thanks in advance Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hi Markus, are the files I sent you sufficient? Do you need anything else to reproduce the error?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Hi Markus, can you give me a rough guess when the problem might be solved?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, Sorry, I have no guess. But I remind our R&D about it again. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I fixed this bug in build 307. The problem was the localized fields we not consecutive in the table. This is why Sisulizer failed to detect them. I fixed the detecting logic such way that localized fields do not have to be consecutive. New build will come out on Friday. Jaakko
|
||||||||||||||||
| |||||||||||||||||
| Current time is 09:28 pm | Page: 1 2 3 4 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database | |
Sisulizer software localization tool - Three simple steps to localize
