Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
issue witImport text file, with C++ escape character - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Fri Jan 23rd, 2009 09:36 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
When i export ASCII strings, in resource-only DLL.  These DLL has many escape character such as rn...etc

After i exported and translated, escape characters are still there.
When i imported back to the Sisulizer, "Escape" tap, select "C/C++" and click next to finish.  I received an unexpected error occurred in the application.

Here is the stack infomation:

version           : 2.0.279.0
compiled with     : Delphi 7
madExcept version : 3.0h
callstack crc     : $d81f1f23, $0307cf96, $0307cf96
exception number  : 9
exception class   : Exception
exception message : Invalid escape character: A.

main thread ($628):
005483c1 +279 Sisulizer.exe LaString         TLaWideString.CppDecode
0093fb0b +077 Sisulizer.exe TextImportSource StrToWide
0093fccc +168 Sisulizer.exe TextImportSource ProcessRule
0093ff9e +186 Sisulizer.exe TextImportSource TTextImportSource.DoImportScan
00944f99 +105 Sisulizer.exe ImportSource     TImportSource.ImportScan
0095818f +143 Sisulizer.exe Importer         TImporter.Import
0095921c +0e8 Sisulizer.exe Importer         TImporter.Process
009509d2 +04a Sisulizer.exe ProjectImporter  TProjectImporter.ImportToProject
0094f8f8 +008 Sisulizer.exe ProjectImporter  TProjectImporter.Import
009ce321 +011 Sisulizer.exe MainFrm          TMainForm.FileImportMenuClick
004d647e +0a6 Sisulizer.exe Menus            TMenuItem.Click
004d771b +013 Sisulizer.exe Menus            TMenu.DispatchCommand
004e0953 +01f Sisulizer.exe Forms            TCustomForm.WMCommand
004c4bb0 +188 Sisulizer.exe Controls         TControl.WndProc
004c7c0f +157 Sisulizer.exe Controls         TWinControl.WndProc
004de9b1 +421 Sisulizer.exe Forms            TCustomForm.WndProc
00504ae9 +085 Sisulizer.exe TntControls      TWinControlTrap.WindowProc
004c788c +02c Sisulizer.exe Controls         TWinControl.MainWndProc
00475c30 +014 Sisulizer.exe Classes          StdWndProc
7d94af0a +016 user32.dll                     CallWindowProcW
0050474c +048 Sisulizer.exe TntControls      TWinControlTrap.Win32Proc
00475c30 +014 Sisulizer.exe Classes          StdWndProc
7d94ab81 +00a user32.dll                     DispatchMessageA
004e4e13 +083 Sisulizer.exe Forms            TApplication.ProcessMessage
004e4e4a +00a Sisulizer.exe Forms            TApplication.HandleMessage
004e507a +096 Sisulizer.exe Forms            TApplication.Run
00cd090f +03b Sisulizer.exe Sisulizer        initialization

thread $468 (TDummyThread): <suspended>
00732e48 +f8 Sisulizer.exe GIFImage initialization

thread $5b8:
7d4e2866 +00 kernel32.dll            WaitForMultipleObjectsEx
7d94d293 +00 user32.dll              MsgWaitForMultipleObjectsEx
7d94d322 +1a user32.dll              MsgWaitForMultipleObjects
0044d2a5 +0d Sisulizer.exe madExcept CallThreadProcSafe
0044d31d +45 Sisulizer.exe madExcept ThreadExceptFrame
>> created by main thread ($628) at:
4dd695ef +00 gdiplus.dll

thread $764:
7d5066ae +23 kernel32.dll            GetQueuedCompletionStatus
0044d2a5 +0d Sisulizer.exe madExcept CallThreadProcSafe
0044d31d +45 Sisulizer.exe madExcept ThreadExceptFrame
>> created by main thread ($628) at:
7da460d4 +00 RPCRT4.dll

thread $5f0:
7d5066ae +23 kernel32.dll            GetQueuedCompletionStatus
0044d2a5 +0d Sisulizer.exe madExcept CallThreadProcSafe
0044d31d +45 Sisulizer.exe madExcept ThreadExceptFrame
>> created by thread $764 at:
7da460d4 +00 RPCRT4.dll

Last edited on Fri Jan 23rd, 2009 09:37 pm by jlsymantec

Back To Top PM Private Upload Quote Reply

 Posted: Sat Jan 24th, 2009 02:45 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
Hello,

Seem to me that you use text file method for export/import translations. Could you send this file and Sisulizer project (SLP) file on following email address:
support (at) sisulizer.fi
Of course, your files will be used only to reproduce and analyze error mentioned in your post.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jan 26th, 2009 02:34 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
Yes, that is correct. I am using text file to import back to the Sisulizer project.

I am so sorry, could you please tell me step by step on how to send the email to support(at) sisulizer.fi?

when i clicked "No new message" and type in support_(at)_sisulizer.fi, the address is invalided.

i am new to this.
thank you!

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jan 26th, 2009 03:07 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
Hello,

Please use address email from below screenshot.

Best regards,
Janusz

Attachment: screen.png (Downloaded 54 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 3rd, 2009 03:53 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
Thank You so much
I just send you the sample .txt file which is already translated into Japanese. I am also sending you the DLL file that you can import.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 3rd, 2009 03:56 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
Thank You so much
I just send you the sample .txt file which is already translated into Japanese. I am also sending you the DLL file that you can import.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 3rd, 2009 07:15 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
Hello James,

I’ve reproduced your error, but I found “\a” items in following strings of your txt file:
- line 942: 1033\ActaRes.dll.Strings.90.1437
- line 972: 1033\ActaRes.dll.Strings.92.1467
However after removing “\a” items, bug with invalid “\A” escape character still occurred, and for this reason I’ll forward it to our R&D.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 9th, 2009 07:41 am
PM Private Upload Quote Reply
goupil
Member
 

Joined: Wed Dec 10th, 2008
Location:  
Posts: 5
Status: 
Offline
Hello Janusz,
Maybe it will hepl you to know that i have the same problem.
I can't import my .txt file with this exception :
date/time : 2009-02-09, 11:32:00, 906ms
computer name : DSPBUILD6
user name : Administrator
registered owner : EMC / EMC
operating system : Windows XP Service Pack 2 build 2600
system language : French
system up time : 1 hour 48 minutes
program up time : 1 hour 45 minutes
processor : Intel(R) Core(TM)2 Duo CPU T7500 _(at)_ 2.20GHz
physical memory : 615/1123 MB (free/total)
free disk space : (C:) 2,02 GB (D:) 7,08 GB
display mode : 1280x776, 32 bit
process id : $748
allocated memory : 215,57 MB
command line : "D:\Sisulizer 2008\Sisulizer.exe" "D:\SisulizerImport\Localization.slp"
executable : Sisulizer.exe
exec. date/time : 2008-10-20 18:22
version : 2.0.273.0
compiled with : Delphi 7
madExcept version : 3.0h
callstack crc : $d81f1f23, $8700afee, $8700afee
exception number : 20
exception class : Exception
exception message : Caractère de sortie invalide: \I.

main thread ($744):
00523b9d +279 Sisulizer.exe LaString TLaWideString.CppDecode
0092da1f +077 Sisulizer.exe TextImportSource StrToWide
0092dbe0 +168 Sisulizer.exe TextImportSource ProcessRule
0092debf +193 Sisulizer.exe TextImportSource TTextImportSource.DoImportScan
0093299d +105 Sisulizer.exe ImportSource TImportSource.ImportScan
00945823 +143 Sisulizer.exe Importer TImporter.Import
009468b0 +0e8 Sisulizer.exe Importer TImporter.Process
0093e0ca +04a Sisulizer.exe ProjectImporter TProjectImporter.ImportToProject
0093cff0 +008 Sisulizer.exe ProjectImporter TProjectImporter.Import
009ba731 +015 Sisulizer.exe MainFrm TMainForm.FileImportMenuClick
004d6466 +0a6 Sisulizer.exe Menus TMenuItem.Click
004d7703 +013 Sisulizer.exe Menus TMenu.DispatchCommand
004e093b +01f Sisulizer.exe Forms TCustomForm.WMCommand
004c4b98 +188 Sisulizer.exe Controls TControl.WndProc
004c7bf7 +157 Sisulizer.exe Controls TWinControl.WndProc
004de999 +421 Sisulizer.exe Forms TCustomForm.WndProc
00504ad1 +085 Sisulizer.exe TntControls TWinControlTrap.WindowProc
004c7874 +02c Sisulizer.exe Controls TWinControl.MainWndProc
00475c18 +014 Sisulizer.exe Classes StdWndProc
7e41c660 +016 user32.dll CallWindowProcW
00504734 +048 Sisulizer.exe TntControls TWinControlTrap.Win32Proc
00475c18 +014 Sisulizer.exe Classes StdWndProc
7e4196c2 +00a user32.dll DispatchMessageA
004e4dfb +083 Sisulizer.exe Forms TApplication.ProcessMessage
004e4e32 +00a Sisulizer.exe Forms TApplication.HandleMessage
004e5062 +096 Sisulizer.exe Forms TApplication.Run
00cb042b +03b Sisulizer.exe Sisulizer initialization

thread $a4 (TDummyThread):
00731a2c +f8 Sisulizer.exe GIFImage initialization

thread $cc:
7c90e9a9 +0a ntdll.dll NtWaitForMultipleObjects
7c8094dc +00 kernel32.dll WaitForMultipleObjectsEx
7e4195f3 +00 user32.dll MsgWaitForMultipleObjectsEx
7e4196a3 +1a user32.dll MsgWaitForMultipleObjects
0044d2a5 +0d Sisulizer.exe madExcept CallThreadProcSafe
0044d31d +45 Sisulizer.exe madExcept ThreadExceptFrame
>> created by main thread ($744) at:
4ec958ef +00 gdiplus.dll

thread $350:
7c90d85a +a ntdll.dll NtDelayExecution

Do you have an estimate date for the fix of this issue ?

Many thanks.
Denis.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 9th, 2009 08:08 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
Hello Denis,

Could you send on support (at) sisulizer.fi email address your import file? That maybe help us faster fix this issue.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 10th, 2009 09:09 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
thanks, please let me know which build has the fix and keep me post it.

thanks!

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 10th, 2009 10:09 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
please let me know which build has the fix and keep me post it.
Yes, of course. Your issue was forwarded to our developers, and currently I wait on investigation results.
 
Best,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 11th, 2009 05:24 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
I fixed this in 280. The new build will come out next week.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 11th, 2009 06:44 am
PM Private Upload Quote Reply
goupil
Member
 

Joined: Wed Dec 10th, 2008
Location:  
Posts: 5
Status: 
Offline
I just send to the support my project and my .txt import file.

Thanks,
Denis.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 11th, 2009 07:21 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2660
Status: 
Offline
Hello Denis,

Thank you for files. Jaakko already fixed this issue, but anyway I’ll test your file.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 16th, 2009 04:39 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
goupil wrote: I just send to the support my project and my .txt import file.

This was the same bug and it is fixed in build 280. The new build will come out in few days.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 17th, 2009 10:17 pm
PM Private Upload Quote Reply
jlsymantec
Member
 

Joined: Fri Sep 26th, 2008
Location:  
Posts: 50
Status: 
Offline
thank you so much. You guys are the best!!

Back To Top PM Private Upload Quote Reply

Current time is 05:58 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > issue witImport text file, with C++ escape character



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize