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  3  Next Page Last Page  
New Topic Reply Printer Friendly
Problem to localize DB - 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 May 4th, 2007 09:42 am
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi,

I'm trying to localize a datatable with a uniqueidentifier as primary key. Unfortunately that doesn't work. Is there a way you could add this functionality?

Best regards,
Andrew

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 4th, 2007 11:30 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

I think you want to localize the database using the "Row Database Localization Method" -> http://www.sisulizer.com/localization/software/server-desktop-database.shtml

You have a unique key so Sisulizer can not add a localized copy of the row with the same unique key. The database integrity will not allow that.
Because of that Sisulizer needs a combined index of your unique id plus a language code. Simply add some field to your table for a language code and select it in the project wizard as language id field. Please also search the online help for Database Localization and read about Prepare table structure for localization in the Row Localization part. I hope this helps.

Best

Markus



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

 Posted: Fri May 4th, 2007 11:58 am
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi Markus,

Actually our primary key is a real one and not a combination of two columns.
Example:

CREATE TABLE [dbo].[TestDataDesc](
    [tesOid] [uniqueidentifier] NOT NULL,
    [tesfmdOid] [uniqueidentifier] NOT NULL,
    [tesculOid] [nvarchar](17) NOT NULL,
    [tesLabel] [nvarchar](255) NOT NULL,
    [tesDescription] [nvarchar](255) NOT NULL,
    [mutperOid] [uniqueidentifier] NOT NULL,
    constraint PK_TestDataDesc primary key  (fddOid),
    constraint FK_TestData_TestDataDesc foreign key (tesfmdOid)
    references TestData (fmdOid),

--> tesculOid is our Culture-Field
--> tesOid our primary key
--> tesfmdOid is a foreign key

Since we have a foreign key on the table, we don't need to use a combination of the primary key and the culture field.

Is there a way to handle this case ?

Expected behaviour:

- tesLabel, tesDescription --> as localized fields
- for a new translation a new row gets generated and the tesOid will generate
  maybe by a storedprocedure or a function (in our case the NEWID-function of SQL
  Server)
- all the other values remain unchanged (copy of the old data)

Best regards

Andrew

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 4th, 2007 01:19 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3103
Status: 
Offline
Hello Andrew,

I see... In the moment this is not impemented. Would be a fifth way to localize databases for Sisulizer ;-)

Perhaps our developers have some solution.

Best

Markus



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

 Posted: Fri May 4th, 2007 01:37 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi,

Okay... Let's hope Jaakko has a idea!

Looking forward to hearing good news from japan!
Thanks for your excellent support!

Best regards
Andrew

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 4th, 2007 01:47 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

I think he will have. But our developers have to decide from technical view if this is easy to implement or a major change to the existing code.

Best

Markus



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

 Posted: Sun May 6th, 2007 09:51 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

I have some question to your database model. If new IDs are created for the new rows and the foreign key is a duplicate - how are you going to find the translations in the database?

Sample:

Old row has ID 1 and foreign key has 20. The translated row has ID 100 and the foreign key is a duplicate, so he is also 20. If you now search for the foreign key 20 - which one is the original and which one the translation? I think you will need an additional language identifier field in any case.

Best

Markus




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

 Posted: Sun May 6th, 2007 12:27 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

Just to make sure that I got your right. Your system works like this:

Let's have an example that your original language is English. You add a new row to the table:

1, 1, en, Name, What is your name?

The you add a Finnish row

2, 1, fi, Nimi, Mikä sinun nimesi on?

And finally Japanese row

3, 1, ja, 名前, あなたの名前は何ですか?

So each line has a unique single column primary key. The tesfmdOid column is a foreign key to this table. It points to the original row. Both Finnish and Japanese rows point to the original English row.

When you use the table you use the SELECT comand that finds the correct row based on the value in the tesfmdOid field.

Am I right?

Best regards,
Jaakko



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

 Posted: Mon May 7th, 2007 10:47 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3103
Status: 
Offline
Markus.Kreisel wrote
Old row has ID 1 and foreign key has 20. The translated row has ID 100 and the foreign key is a duplicate, so he is also 20. If you now search for the foreign key 20 - which one is the original and which one the translation? I think you will need an additional language identifier field in any case.


Sorry Andrew,

I just saw, that you already have such field: tesculOid
So you can already query for tesfmdOid + tesculOid to find the translation.
Can't you change tesculOid into some Sisulizer language id field compatible type?

Best

Markus



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

 Posted: Mon May 7th, 2007 10:51 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

I implemented this kind of row localization method to 1.5.4

I have some questions:

1) How to you generate the row ids for localized row. Can they just start where the original ended. Or should there be sa separate pool for them.  When I implementedc this localization I added Minimun localization row id value to the database source dialog. By default it is 0 so SL continues at the last row id. If you set it some other SL never uses row id smaller that that.

2) I see that you use SQL Server. Is it right?

Best regards,

Jaakko



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

 Posted: Mon May 7th, 2007 02:42 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi,

oh, a lot of new posts.
(Sorry for my missing responses)

okay, let's see...

- The foreign key points to an other table, which acts like a lookup table. It's an
   unique identifier (SQL Server Function: NEWID or Guid.NewGuid() in C#).

   Example: You have a Project with different Labels(Names) for different languages.
                   So, the foreign key points to the project. With this table we just
                   separate all the culture specific stuff

   --> So don't be concerned about this value (just leave it for the new row as it is)

- "tesculOid" is so far as I know a Sisulizer compatible type, like "de" or "de-CH"
  --> Sisulizer already shows the table as expected

- SQL Server is my preferred database Server

The new Sisulizer function in one sentence:
When I add a new translation, Sisulizer should generate a new "Guid" as primary key for the row, use the entered string as translation and leave all the other rows as they are....

Since I assume you don't want to add such a special functionality to your product, I would suggest that I can enter the name of a function or stored procedure that Sisulizer uses to generate the primary key (every customer can handle this like he wants)

Sorry, If my response sounds rude, it's not by intention.
I'm really surprised by your great support.

Or in German:
Herzlichen Dank für Ihren sehr guten Support und ausgesprochen rasche Bearbeitung. Ich hoffe mein Anliegen in Englisch verständlich dargelegt zu haben, ansonsten kontaktieren Sie mich bitte einfach.

Best regards,
Andrew





Back To Top PM Private Upload Quote Reply

 Posted: Mon May 7th, 2007 11:26 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

I got your point. It should work now. I will test this few days and then include to build.

Thank you for good idea.

Jaakko



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

 Posted: Tue May 8th, 2007 12:51 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi,

Thank you very much!

I'm really looking forward to getting the new release!
Do you already know the release date?

Best,
André


Back To Top PM Private Upload Quote Reply

 Posted: Tue May 8th, 2007 02:02 pm
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

Everything works except calling the stored procedure. I try the get it working tomorrow and then I need a day or two testing so if should be ready early next week.

Jaakko



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

 Posted: Wed May 23rd, 2007 02:57 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi Jaakko,

anything new about this issue?

Best regards,
Andrew

Back To Top PM Private Upload Quote Reply

 Posted: Wed May 23rd, 2007 03:03 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

Jaakko already left the office in Tokyo but I know for sure that the new build is scheduled for tomorrow. The database issues you mentioned are in - I saw the strings while localizing Sisulizer 1.5.5 into German :-)

We had some urgent bug fixes we needed to put into this build.

Best

Markus



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

 Posted: Wed May 23rd, 2007 03:05 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Great!

Thanks.

Back To Top PM Private Upload Quote Reply

 Posted: Wed May 23rd, 2007 03:05 pm
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Great!

Thanks.

Back To Top PM Private Upload Quote Reply

 Posted: Thu May 24th, 2007 08:47 am
PM Private Upload Quote Reply
André Bitzer
Member
 

Joined: Thu Nov 2nd, 2006
Location: Sursee, Switzerland
Posts: 60
Status: 
Offline
Hi,

First of all, thanks for the new release.

Unfortunately, I still have problems to localize my db.
Problems:
1. How can I specify the ID field?
    --> If I select the field and open the context menu, I do not see the Id "Field  
          option" --> see Attachment


2. If I open the properties dialog for my Db and open the context menu with no other "click" the "right" context menu appears, but if I choose the "Id Field" option, a exception occurs. --> see Attachment

Best regards,
Andrew
 

Attachment: Question.zip (Downloaded 2 times)

Back To Top PM Private Upload Quote Reply

 Posted: Thu May 24th, 2007 10:38 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

Sorry about the wrong information. This new row localization does not yet work for SQL Server. I am still waiting for the SQL component fix. As soon as I get it I will implement nre row localziation for SQL Server

Jaakko



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

Current time is 07:13 am Page:    1  2  3  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 > Problem to localize DB



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