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 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > A few questions

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius Page:  First Page Previous Page  1  2   
New Topic Reply Printer Friendly
A few questions - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Thu May 24th, 2007 12:41 pm
PM Private Upload Quote Reply
pipoman
Member
 

Joined: Thu May 10th, 2007
Location: Paris, France
Posts: 11
Status: 
Offline
 I have been "playing" with release 1.5.5 a little bit and I have experienced two problems when switching language at runtime (bad start :? especially for a quick test).

A basic one with TListBox or a TComboBox: Items (string list) are not translated.

It seems that a TcxGrid (ExpressQuantumGrid) cannot be translated. I got an exception "Access violation ... Read of address 000000" when it reaches this component. The other components seem to get updated though. Weird.

If you are interested, here is the tiny test application I have been doing (includes the Sisulizer project file containing 3 languages).
This being said, it seems very promissing!

Attachment: BasicTest.zip (Downloaded 1 time)
Back To Top PM Private Upload Quote Reply

 Posted: Thu May 24th, 2007 01:08 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 I will fix this. Some properties are a bit tricky to translate. Anyway I will test more and send you new units as soon as I get them fixed.

Jaakko



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

 Posted: Fri May 25th, 2007 03:10 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 I fixed. The reason was that some DevExpress components has collection items whose size is zero. TLaTranslator crashed in that situation.

I also implemented TLaModule classes that extend TLaTranslator to translate binary or complex properties such as list items of TListView and TTreeView.

I will send you new classes later today.

Jaakko



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

 Posted: Fri May 25th, 2007 07:43 am
PM Private Upload Quote Reply
pipoman
Member
 

Joined: Thu May 10th, 2007
Location: Paris, France
Posts: 11
Status: 
Offline
 Good to hear. I guess that it must be a tough job to support all third part tools on the market (some can or must do some weird stuff).

Any thought about the other one I mentioned, concerning Items of a TListBox/TComboBox, which are not translated when switching language at runtime?
Back To Top PM Private Upload Quote Reply

 Posted: Fri May 25th, 2007 07:47 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 Here are the new units. Extract them to <sldir>VCL. They fix the problem you reported and implements translation of TListView and TTreeView and TNT controls.

Jaakko

Attachment: LaVcl.zip (Downloaded 2 times)



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

 Posted: Fri May 25th, 2007 07:51 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 pipoman wrote: I guess that it must be a tough job to support all third part tools on the market (some can or must do some weird stuff).

Usually it is not that hard to test 3rd party components. Only if they use binary properties then we have to write some code to read adn write the property.

The hard part is

1) Learn to use the 3rd party component

2) Try to get the source code of the 3rd prty component. Some vendors want to make co-operation, some don't, some don't even reply to email or calls. Without component source code we can not implement scanning of binary properties.

Delphi has very flexible collection and list properties so there should be not need to use binary properties. Unfortunately some 3rd party component go back to Delphi 1 when there was not collection propety and they had to use binary one.

Bacially we want to test all 3rd party component that our client use to make sure than SL can localize them and to premap them so customer do not need to map them.

Jaakko



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

 Posted: Sun Jun 10th, 2007 06:59 pm
PM Private Upload Quote Reply
Everybyte
Member
 

Joined: Sun Jun 10th, 2007
Location:  
Posts: 1
Status: 
Offline
 I experienced similar AV with TRichView component when reading "Tabs" property; below is a quick-fix that may be  useful  with other components

procedure TLaTranslator.ProcessCollection;
var
  i: Integer;
  propInfo: PPropInfo;
  item: TCollectionItem;
  collection: TCollection;
begin
  if (TypeInfo <> nil) and (TypeInfo.Kind <> tkClass) then
    raise Exception.Create('Invalid data');
  if FObj = nil then                                           //fix
    PropInfo := nil                                            //fix
  else                                                              //fix
    propInfo := GetPropInfo(FObj, FName);
Back To Top PM Private Upload Quote Reply

 Posted: Sun Jun 10th, 2007 11:48 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 Thank you for the report. I fixed in 1.5.10. I also mapped TRichView components. It seems like a very nice component.

I wanted to know why FObj is nill so I tried to reproduce but could not. What kind of data you have in the Tabs property? A small sample or just content of TRichView on DFM would help a lot.

You can send it to support (at) sisulizer.fi

Regards,
Jaakko

Last edited on Mon Jun 11th, 2007 12:06 am by Jaakko.Salmenius



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

Current time is 09:01 pm Page:  First Page Previous Page  1  2     
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > A few questions



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