|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| sql-database configuration - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Matthew Member
|
Hello, we have a sql database with some tables containing fields that should be translated. We have for example a table named 'Accuracies' that includes the fields 'Name_DE', 'Name_EN', and 'Name_FR'. When I configured these fields for the first time I dragged the EN and FR fields below the DE field and assigned the languages 'German', 'English' and 'French' respectively. This worked fine (also it was quite cumbersome, for we habe quite some fields to translate). Afterwards we added new tables to the database including new fields for translation. To add these new fields in the Sisulizer project I clicked in the properties of the database on the button 'Connect' and got the tab page 'Items' where I could see all relevant database fields. But my original configuration was lost, the fields Name_DE, Name_EN, and Name_FR from the above example were not structured anymore and the language assignment was lost. What did I do wrong? I have read, that Sisulizer is able to scan a database automatically if the fields have the scheme 'Name', 'Name_EN', and 'Name_FR'. Is there a change for expanding this feature for our scheme ('Name_DE', ...)? Thanks in advance, Matthew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Matthew wrote: To add these new fields in the Sisulizer project I clicked in the properties of the database on the button 'Connect' and got the tab page 'Items' where I could see all relevant database fields. But my original configuration was lost, the fields Name_DE, Name_EN, and Name_FR from the above example were not structured anymore and the language assignment was lost. What did I do wrong? This was a bug and it has been fixed in build 282. The new build will come out in few days. If you use build 281 or earlier the selections will be lost if you open Properties dialog and press Connect button. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hello Jaako, thanks for your fast reply and for the fast bug fix. As for my second question, whether an automatic database structure scan could also work with the pattern (Name_DE, Name_EN, ...), shall I post this in the wish list forum? Matthew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Matthew wrote: As for my second question, whether an automatic database structure scan could also work with the pattern (Name_DE, Name_EN, ...), shall I post this in the wish list forum? I was just working on that case. Sisulizer could not detect the pattersn because there were not neutral field (e.g. Name) but all fields were language depend (e.g Name_??). I will fix this too. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Fixed in 282. If you have only language depend field names Sisulizer will show a dialog that lets you to choose what is the original language. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:26 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > sql-database configuration | |
Sisulizer software localization tool - Three simple steps to localize
