|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Export to Excel (suggestion) - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
psantaana Member
|
Hello: I would like to export my project to a specific sheet in an Excel file (so I can have 1 excel for several projects). Would it be possible to add this feature in the near future? Thanks... Pablo.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Pablo, Not sure about that. Under File - Export you can export to Excel if you have the Enterprise Edition. Do you perhaps look for that? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
psantaana Member
|
Hi Markus: I have de Proffesional Edition and I can Export to Excel and I am using it very well. May be I didn't explain very well my self. This is what I want:
I hope I can explain myself. Regards... Pablo.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, You are right. The Pro edition does have that feature as well. My bad. Our R&D has to decide about that if the like the idea. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
danics Member
|
Hello! I'm trying this feature, but it seems I'm doing something wrong. A message saying "Invalid cell value or type" pops up. I have two languages (one is a Portuguese Pseudo-Localized, and the other is traditional chinese) and I'm not changing any default option. Any clues? Thank you in advance. Attachment: celltypeerror.png (Downloaded 33 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you upload me your Sisulizer project file (.slp). Click Private Upload button to upload the file. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the file. I found the reason for the error. It seems that the maximum string length in Excel sheet is 0x7FFF. One of your string was longer that this and Sisulizer tried to write too long string. I fixed this such way that if string is longer than the max length Sisulizer cuts the string. The fix is in build 296. The new build will come out next week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
danics Member
|
Thank you, Jaakko. Is it possible to export to another format, without this limitation? Or maybe with your fix would be possible to detect the lines in which the issue happens? Regards
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
If you ext to to TMX or text file there is not length limit. It only applies to Excel and it is because of Excel limitation and not because is Sisulizer. When Sisulizer writes longer than maximum string into Excel Sisulizer cuts the strings and writes a warning to log file. There you can see the location where the long string exists. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
danics Member
|
I followed your suggestion, but I keep getting a huge block of what seems to be XML text. It doesn't appear anyware in Sisulizer, but I'm not able to remove it. What options should I select/deselect?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Altitude.uSupervisor.USupEntityResourceManager.StringsTable contains ServerStrings items that is a string that stores this huge XML data. If you try to select that in Sisulizer Sisulizer freezes for a while (I will fix this). You better remove the XML resource and store it as file and not as string data. If it is a separate resource item Sisulizer will detect it as XML and can properly show it. Now it tries to interpret it a string and because it is very long it causes problems. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
danics Member
|
Thank you for help, Jaakko, it was very helpful. I will contact our R&D department so they can change that. Regards
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:57 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Export to Excel (suggestion) | |
Sisulizer software localization tool - Three simple steps to localize