|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 |
|
||||||||||||
| Problems with JSP - Bugs and Quirks in Sisulizer - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I fixed it. Will be in the next build. With the current build you can also disable scanning the value attributes. See the picture. Right click the HTML/JSP project node and choose Properties... It however disables all value attributes of INPUT elements. If you have to translate any of them you can't use this options but wait to the next build. Attachment: Input.PNG (Downloaded 71 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
I have tried the new version build 270. It really does everything you said. But!!!! It builds 5 languages for more than 12 hours! I am using the SLMake. When I run the same slp file in the UI I have about 4-7 min for a language. Something really really wrong. I am sending you the slp file in the mail.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lgol27 Member
|
From another point of view I just tried to open the slp file in the application. It took 48 min. Is it possible to speed up the process?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
I have tried the new build 271. It is all the same. It loads 60% pretty fast and then it stalls. It continues to work, because I see that CPU and memory usage change.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Igol, we made some tests here and your project loads in 5 sec on the one and 11 sec on some other machine. Are you running low in memory? 1 GB Ram would be recommended. Do you load the project from some network drive? Do you have the same effect if you load the file locally? We can not test the build because that would need your jsp and html files as well. But while loading of the project already shows very different loading times the problem with building might have the same reason. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
This is a local disk. I have 4GB physical memory and 4 core processor.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lgol27 Member
|
I have created a new project with the same languages and imported the translations from the original project. It loads super-fast. The only difference is that I have a lot of excluded items.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
By the way, when I saw that it works slow, I have removed some languages from the project. So instead of 20 I have 5 now.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
OK, that might be the difference. While we do not have the files you excluded our Sisulizer might skip this excludes. On your system the excludes are honored and there might be a bottle neck. I have to ask R&D how we can solve that Is it possible that you send all files from the project? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
All right. I am sending the files.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lgol27 Member
|
will the rar file be ok?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
sure, but let's wait for R&D's opinion. Perhaps they got some idea from what you found. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lgol27 Member
|
Thank you. You can't imagine how much pressure I have right now about it.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator
|
Please test in this way: 1. Copy your SLP file into another directory where aren't any of your source files (HTML and JSP) 2. Try to open it there Does the opening still take a long time?
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lgol27 Member
|
I took the older version of slp file. I have imported the translation. It looks so far so good.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lgol27 Member
|
Hello all! 1. I have tried the new version 2008 build 272. I have exported to Excel file. I have got the excluded strings in the Excel file. 2. (This was spotted on older builds) I have seen that the file is loaded very slow when it grows in size, like twofold or threefold. It happens when some strings with tags "native" and "prev" in the slp file are dublicatated several hundreds times. This somehow is connected to temporary files on the disk. If I take a "normal" copy of the slp file and I delete the temporary file every time I open Sisulizer the slp file stays in the same size. I am sending files in mail - The bloated slp file, the normal slp file, and the exported excel file.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, About your first question: I compared your Excel file and Sisulizer project file, and I found items mentioned in your email in project (order_search.jsp in folder link_study) as not excluded (rows aren't on Excluded Rows list), and for this reason strings are available in exported Excel file. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 12:55 am | Page: 1 2 |
| 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) > Bugs and Quirks in Sisulizer > Problems with JSP | |
Sisulizer software localization tool - Three simple steps to localize
