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 Page:    1  2  Next Page Last Page  
New Topic Reply Printer Friendly
Janus .net grid control not localizable - 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: Mon Jul 16th, 2007 05:01 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Dear Sisulizer team,

While translating my application, I bumped into a problem. It seems that Sisulizer isn't able to retreive the " layoutstring"  for the grid control of the janus controls suite (http://www.janusys.com). Therefore, we can't localize it in Sisulizer. We can however localize it in VS 2005, but because we also use Sisulizer, we get a "cyclic overwriting situation" (VS 2005 overwrites changes made by Sisulizer, and vice versa).

I think I already pinpointed the problem: the grid control stores its layout in the .resx file using "gridname_DesignTimeLayout.LayoutString". If I rename this .resx "record"  in "gridname.LayoutString", then Sisulizer finds the record (thought this isn't a solution for the problem as the grid doesn't use that record). I've also concluded that Sisulizer is hiding this "LayoutString" by default in its .NET Component section. However, I've not managed to resolve the issue by altering those properties in any way. Moreover, for a different control (a TimeLine control from the same suite) Sisulizer does detect a similair scheme: we can see the record: "TimeLine1_DesignTimeLayout.LayoutString".

I hope you can reproduce and hopefully fix this issue.

Yours sincerely,

Michel van den Berg

 

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jul 17th, 2007 11:08 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

the holiday season also got us. We will look into it but it will take a bit longer at the moment.

Thanks for your patience

Best

Markus



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

 Posted: Tue Jul 17th, 2007 11:59 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

just an quick idea. Can you set the property at runtime for some resource strings, e.g. like:

gridname_DesignTimeLayout.LayoutString = MyResourceString 

?

You then can localize MyResourceString as a regular string in your resources like all other strings. This should work with all strings Sisulizer can not read. Our problem is that some makers of .NET third party controls forget completely about localization and we have a very hard time to fix what they broke. Only a few care for localization at all and support software localization vendors. But with the trick above you should be able to help yourself.

Best

Markus








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

 Posted: Wed Jul 18th, 2007 03:41 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Yeah, I already tried that, and it althought it works, it's still not a real solution. Hopefully, you could provide me a fix soon, as it's really tedious this way. Moreover, we wonder how trustworthy your product is for our future developments; as stated on your website: " .NET: Tested and mapped with Infragistics's NetAdvantace components and Janus components." As the grid is Janus' flagship product, I wonder what exactly it is, you tested.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 18th, 2007 03:54 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

we tested the control at the time of the release of version 1.5. The problem is, that third party tool vendors do not take care for software localization and change their products. We do not get any support, information or feedback from this companies according this. Supporting this tools is a tedious job and needs some time on our side. So please be patient and use the workaround for now.

Best

Markus



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

 Posted: Wed Jul 18th, 2007 04:20 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Ah 1.5 (I didn't know that your product was that old). Perhaps it is wise to remove this "feature" from your feature-list?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 18th, 2007 04:38 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3103
Status: 
Offline
Do you remove features in your software if one customer reports a single quirk where a working and easy to handle workaround is available?

The problem will be solved as all problems of our customers got solved in the past - please just be patient and use the workaround in the meantime.

Best

Markus





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

 Posted: Wed Jul 18th, 2007 04:50 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Sorry, I don't want to start a "war"; I never said you should remove features from your software. What I did say is that you should remove it from you feature-list on your website, because now you are featuring something that you don't have. Perhaps, explicitly say that it's for version 1.5?

Anyhow, for now I'll use the workaround (which I already had in the first place).

Thnx,

Michel van den Berg

Last edited on Wed Jul 18th, 2007 04:51 pm by promontis

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 18th, 2007 05:06 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

yes a war about that is not wise.

Fact is simply that there is an endless list of third party controls changing all the time. We simply can not write test applications for all of available controls and use all properties in this like you do. We would do nothing else, especially if the controls keep changing all the time. We do our best but still we are all just humans. If somebody reports a problem we first try to get a work around, put the issue to the todo list and fix it ASAP. Normally this process is extremly fast. In the moment we have holiday season, promised some features and so it just takes a few days longer. No need to change the what is new in 1.5 list for such short period of time. The support exists and I know at least one customer for sure using it :-)

Best

Markus



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

 Posted: Thu Jul 19th, 2007 12:46 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

Janus.Windows.GridEX.GridEXLayout.LayoutString is excluded by default. This is because it seems not to contain ny localizable data and the content is very complex. It is most like that translator will write invalid data when localzing the complex XML data.

However you can turn it on:

1) Right click your .NEt source fiel in the Sisulizer project tree and choose Components

2) Double click Janus.Windows.GridEX.GridEXLayout.LayoutString

3) Choose properties sheet and select LayoutString

4) Press Del.

Sisulizer removes excluding of LayoutString. Next time you scan the content of LayoutString will appear in SL's sheet.

The above turned on it only on that project. If you want to turn it on on very project choose Tools | Platforms | .NET -> Components and perform the same delete there.

Jaakko

Attachment: untitled.PNG (Downloaded 37 times)



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

 Posted: Thu Jul 19th, 2007 01:03 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
I looked the LayoutString data more carefully and noticed that it contains Caption properties that should be localized. So it contains localizable data after all.

This is why I removed the exclude in 1.5.19

Do you know where I can get the specification of that file format. It is a bit dangerous to let translator to edit that data. Most likely the result will be invalid and application fails to start. If I know the file format I can make special scanning for that data so it will separate the captions. The result would be safe localization of Caption properties.

Jaakko



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

 Posted: Thu Jul 19th, 2007 01:17 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
The format seems to be quite simple. Only Caption element needs to be localized. I added this to todo list.

<?xml version="1.0"?>
<GridEXLayoutData>
  <RootTable>
    <Caption>Products</Caption>
    <Columns Collection="true" ElementName="Column">
      <Column0 ID="ProductID">
        <Caption>ProductID</Caption>
        <DataTypeCode>Int32</DataTypeCode>
        <DataMember>ProductID</DataMember>
        <Key>ProductID</Key>
        <Position>0</Position>
      </Column0>
      <Column1 ID="ProductName">
        <Caption>ProductName</Caption>
        <DataTypeCode>String</DataTypeCode>
        <DataMember>ProductName</DataMember>
        <Key>ProductName</Key>
        <Position>1</Position>
      </Column1>
      <Column2 ID="SupplierID">
        <Caption>SupplierID</Caption>
        <DataTypeCode>Int32</DataTypeCode>
        <DataMember>SupplierID</DataMember>
        <Key>SupplierID</Key>
        <Position>2</Position>
      </Column2>
      <Column3 ID="CategoryID">
        <Caption>CategoryID</Caption>
        <DataTypeCode>Int32</DataTypeCode>
        <DataMember>CategoryID</DataMember>
        <Key>CategoryID</Key>
        <Position>3</Position>
      </Column3>
      <Column4 ID="QuantityPerUnit">
        <Caption>QuantityPerUnit</Caption>
        <DataTypeCode>String</DataTypeCode>
        <DataMember>QuantityPerUnit</DataMember>
        <Key>QuantityPerUnit</Key>
        <Position>4</Position>
      </Column4>
      <Column5 ID="UnitPrice">
        <Caption>UnitPrice</Caption>
        <DataTypeCode>Decimal</DataTypeCode>
        <DataMember>UnitPrice</DataMember>
        <FormatString>c</FormatString>
        <Key>UnitPrice</Key>
        <Position>5</Position>
      </Column5>
      <Column6 ID="UnitsInStock">
        <Caption>UnitsInStock</Caption>
        <DataTypeCode>Int16</DataTypeCode>
        <DataMember>UnitsInStock</DataMember>
        <Key>UnitsInStock</Key>
        <Position>6</Position>
      </Column6>
      <Column7 ID="UnitsOnOrder">
        <Caption>UnitsOnOrder</Caption>
        <DataTypeCode>Int16</DataTypeCode>
        <DataMember>UnitsOnOrder</DataMember>
        <Key>UnitsOnOrder</Key>
        <Position>7</Position>
      </Column7>
      <Column8 ID="ReorderLevel">
        <Caption>ReorderLevel</Caption>
        <DataTypeCode>Int16</DataTypeCode>
        <DataMember>ReorderLevel</DataMember>
        <Key>ReorderLevel</Key>
        <Position>8</Position>
      </Column8>
      <Column9 ID="Discontinued">
        <Caption>Discontinued</Caption>
        <DataTypeCode>Boolean</DataTypeCode>
        <ColumnType>CheckBox</ColumnType>
        <DataMember>Discontinued</DataMember>
        <EditType>CheckBox</EditType>
        <Key>Discontinued</Key>
        <Position>9</Position>
      </Column9>
      <Column10 ID="OnSale">
        <Caption>OnSale</Caption>
        <DataTypeCode>Boolean</DataTypeCode>
        <ColumnType>CheckBox</ColumnType>
        <DataMember>OnSale</DataMember>
        <EditType>CheckBox</EditType>
        <Key>OnSale</Key>
        <Position>10</Position>
      </Column10>
    </Columns>
    <GroupCondition />
  </RootTable>
</GridEXLayoutData>



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

 Posted: Thu Jul 19th, 2007 01:18 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Ah, that would be really great! However, I've not found any documentation about the format. I would have recommended to ask the Janusys Developers yourselve, but I see you already did that! Hopefully, they'll respond quickly! Otherwise, you might try to just capture the text inside <Caption> </Caption> tags?

Michel van den Berg


EDIT: You seemed to respond to quickly :) Nevermind this post!

Last edited on Thu Jul 19th, 2007 01:19 pm by promontis

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 19th, 2007 01:22 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Hi,

Do you have some estimate about when it will be done?

Also, do note that (so it seems) almost the whole suite uses such kind of layoutstrings...

Thnx for the effort!

Michel van den Berg

 

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 19th, 2007 01:28 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
From few days to two weeks. Can be faster but I do not promise.

Jaakko



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

 Posted: Thu Jul 19th, 2007 01:42 pm
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Great! I'll wait for your solution then.

Just thinking out loud: maybe you can improve your product even further by allowing this logic (of how to decomposite a component) to be "scripted" by the user?

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 19th, 2007 01:48 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
promontis wrote: Just thinking out loud: maybe you can improve your product even further by allowing this logic (of how to decomposite a component) to be "scripted" by the user?

This is our plan. In some source you can already parset data using regular expressions. The new build will have very sophisticated text file parser.

Support for nested parser (e.g. XML data inside .NET value or INI data inside RC value) will be implemented in the future versions of Sisulizer.

Jaakko



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

 Posted: Thu Jul 19th, 2007 10:04 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
1.5.19 will contain smart and safe LayoutString scanning for Grid component.

I will implement other later.

Jaakko



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

 Posted: Fri Jul 20th, 2007 06:15 am
PM Private Upload Quote Reply
promontis
Member
 

Joined: Mon Jul 16th, 2007
Location:  
Posts: 10
Status: 
Offline
Great! Thanks for the nice support and looking forward to see future versions of Sisulizer!

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 8th, 2007 03:37 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
1.6.0 is available
http://www.sisulizer.com/downloads.shtml

Jaakko



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

Current time is 07:14 am Page:    1  2  Next Page Last Page    
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Janus .net grid control not localizable



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