|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Problem with localization of an SQLServer database
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Problem with localization of an SQLServer database
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Problem with localization of an SQLServer database - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Freysi Member
|
I have a table defined as such: GUID varchar(50) Name varchar(256) Description varchar(4096) Language varchar(10) GroupName varchar(50) PrimaryKey(GUID, Language) This table is partially localized already, that is certain rows already have 'de' and 'is' values with the same GUID. When I load this up into Sisulizer, I only see the rows for the 'en' values. Additionally, when I set a value for the Icelandic text (for example) and perform a build I get a violation of primarykey error, as if Sisulizer is attempting to insert an identical row. I'm not sure what I'm doing wrong.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
This seems right and you seem to do it right. I have to test this. Is the order of your fields exactly same as you write above. I mean there are none primary key fields between primary key fields? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Freysi Member
|
The order is as I wrote, yes.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Freysi Member
|
I moved the Language column up so that it is defined right after the GUID column and recreated the Sisulizer project. Somehow it worked after that. I'm not sure if it is a direct result of moving the column or if it was something else.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
The reason was the field order. The was a bug and I fixed it in 1.6.13 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I also improved the field selection. In your case the primary key is a combination of two string fields: GUID and Language. Currently Sisulizer let you select GUID as a localized field. This should not be done. Starting from 1.6.13 Sisulizer show string fields that belong to primary key but does not let user to select them as localizable. Instead they are all shows as possible language field. Only onw of them can be selected as language field. If the name of the field is Language, LangId, Locale or LocaleId Sisulizer automatically selects the fields as Language field. 1.6.13 will come out tomorrow. Jaakko Attachment: untitled.PNG (Downloaded 39 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Freysi Member
|
Thanks 
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Freysi Member
|
I'm having another problem now, possibly related. I am able to see the Icelandic text which was already in the database before, however, none of the German text in the database comes up into Sisulizer. Icelandic was defined as being before German, when I created the Sisulizer project. Also if I change the "Replace project translations with existing translations in database" to "Update only empty translations" or "Always update existing translations", then I receive an access violation when I click on "Scan for Changes". 11:34:32 Scanning "DefaultRMStudio2007v3Freysi" database 11:34:52 Error Access violation at address 009E3CC4 in module 'Sisulizer.exe'. Read of address 00000020 11:34:53 Elapsed time 20 s Last edited on Thu Oct 4th, 2007 09:37 am by Freysi |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
The access violation is realate to the bug I fixed. Possibliy missing German translations too. What is the language code that you use for German? Is it "de"? Icelandic is "is"? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Freysi Member
|
'de' for German 'is' for Icelandic.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Codes are right. I will upload the new version early tomorrow. It should work. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Freysi Member
|
Thanks for the new version. I'm still getting the access violation. This is quite odd. If I set English as the original language and Icelandic as the second, I am able to correctly read up about 81% of the localization data in the DB before the error happens. The German data is then at 0%, seems as though the DB scanning is aborted when the access violation occurs. If I put the German data first with English original, I only get 11% + violation. If I put the Icelandic data as original with English first, it works without a violation. If I put the Icelandic data as original with German first, I get 11% + violation. I'm wondering if it has something to do with the data itself? I don't know, I'm pretty stumped at the moment.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, yes, that sounds defenitly like there is some data in some row causing the problem. Jaakko has to look into it again after he is back from some days off. Perhaps you can see something what is different in the German table at ~11% of the rows? Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Freysi Member
|
I tried scanning through the data to see whether there was any pattern to which rows were not parsed correctly, but could find nothing. I changed all the text in the EN to 'bla', all the IS to 'bla2' and all the DE to 'bla3' and I still have problems using the german. EN original with IS translation is parsed correctly, as is IS-EN, but EN-DE, IS-GE, DE-EN, and DE-IS all fail with an access violation. Even if I put all EN to ' ' and all DE to ' ' it failed the same way. BTW my guids are in this form: '2F11DE18-C528-4751-8DD3-D820C9E606A6'
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hello Freysi, Jaakko has to look into that after he returned to the office on Wednesday. If you have any files you might think could be helpful you should already send them to support_(at)_sisulizer.fi that he can use them right away. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
This must be because the structure of your table. Can you export the SQL of the table to an SQL file and send it to me. support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I changed the database detection logic such way that you do not have to have indexed resource id field any more. Any string or interger field can be a resource id field. The new fearue is in 1.6.16 that will come out in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:51 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Problem with localization of an SQLServer database | |
Sisulizer software localization tool - Three simple steps to localize
