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: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
some bugs and wishes concerning DB translation - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Aug 18th, 2010 08:02 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
Hallo,

here some bugs and wishes concerning DB translation

1) Bug: while DB password being typed in, sisulizer shows an exception by each key stroke

2) Minor bug: the DB translation crashes if the original text field contains following string (just 2 symbols) : "<<"

3) Wish: we use access db with  workgroups and permissions, so the way to connect it is like this:

<path>\mydb.mdb  /Wrkgrp <path>\myworkgroup.mdw /EXCL /User MyUser

and a password of MyUser

It would be great if Sisulizer supports this kind of connection. Now I can choose the db path, but there is no way to give the other parameter to the connection


4) Wish: if in the table the original text field is the primary key, it's impossible to translate because primary key field doesn't appear in the filed list. E.g. if I have Field1 with original text as primary key and Field2, Field3 as translation, I cannot drag the Field2 under Field1 because Filed1 is not in the list. It would be nice to have it corrected.



Sincerely

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 09:02 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: 1) Bug: while DB password being typed in, sisulizer shows an exception by each key stroke

I reproduced this and start fixing it.

2) Minor bug: the DB translation crashes if the original text field contains following string (just 2 symbols) : "<<"
This I could not reproduce. Can you send me a sample DB. Click Private Upload to send the file.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 09:56 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
1) Fixed in build 309

3) Implemented in build 309. See screenshot. Here you can enter additional parameters. The format of parameters must be same as they would be in connection string of ADODB.

Jaakko

Attachment: Untitled.png (Downloaded 18 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 11:32 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
great!

will the following go it we type it into the parameter edit box?
"User ID=MyUser;Jet OLEDB:System database=C:\some directory\MySystemDB.mdw"

build 309? now we have 307, so it's not the next one but the one after? when is it expected approximately?

Thanks a lot for your quick reply

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 11:38 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: build 309? now we have 307, so it's not the next one but the one after? when is it expected approximately?

309 will be the next public build. It will come in few days. 308 is not public because it went to teh partner DVD of next Delphi/C++Builder.

Thank you for the file. However when it tested it Sisulizer did not report any error and could correctly read "<<" row. What is your OS?

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 11:46 am
PM Private Upload Quote Reply
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
XP professional SP3

I've just reproduced it with the db I've send to you. I upload the screenshot now

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 11:50 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
Hi,

Instead of using Private Upload you can attach pictures (e.g. screen shots) to your posts.

Use Private Upload for all other data or screen shots in case they contain secret info.

Markus



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

 Posted: Wed Aug 18th, 2010 09:49 pm
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: 4) Wish: if in the table the original text field is the primary key, it's impossible to translate because primary key field doesn't appear in the filed list. E.g. if I have Field1 with original text as primary key and Field2, Field3 as translation, I cannot drag the Field2 under Field1 because Filed1 is not in the list. It would be nice to have it corrected.

I implemented this too in 309.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 09:59 pm
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: will the following go it we type it into the parameter edit box?
"User ID=MyUser;Jet OLEDB:System database=C:\some directory\MySystemDB.mdw"

Yes

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 18th, 2010 10:38 pm
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
ka_developer wrote: 2) Minor bug: the DB translation crashes if the original text field contains following string (just 2 symbols) : "<<"

The reason I could not reproduce this was that we had already fixed this. The bug was in 307 (and earlier) but is fixed in 309.

309 fixes all the bugs your reported and contains the new features your wished. It will come out early next week.

Jaakko

Back To Top PM Private Upload Quote Reply

Current time is 01:23 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 > some bugs and wishes concerning DB translation



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize