|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer looses database fields configuration
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer looses database fields configuration
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Sisulizer looses database fields configuration - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Matthew Member
|
We created a Sisulizer project with the 271 build of Sisulizer. One Subproject was a connection to a SQL-Database on a server. Some fields in some tables have a scheme like this: Name_DE, Name_EN, Name_FR. The Name_DE field holds some text in German (our original language), Name_EN and Name_FR the English and French translations. The initial assignement of the fields was very cumbersome due to the following reasons: Every table that includes a string is presented in the configuration menu for the database and has to be exluded from the configuration by clicking with the mouse or if we choose to include some of the fields we had to drag the Name_EN and Name_FR under the Name_DE. I had to exclude some hundred tables and only include about 20. This was really a tedious work (especially since the Dialog in which this has to be done cannot be resized!). After I did this once, I thought I would never have to do this again. But after our first change of the database, Sisuzlizer lost the complete configuration! So I have to do this work again? Is there a possibility to configure the fields and tables by means of a script or any other automated way?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Matthew Member
|
Furthermore: If I try to repair the configuration (with Sisulizer build 274) this configuration is accepted by Sisulizer without an error but is not stored, i.e. when I look into the properties of the database project the configuration is lost. I can not repair this project!
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Matthew Member
|
Meanwhile I made some experiments with Sisulizer build 274: During the database field configuration there is no need to disable tables without translatable fields, this is a great improvement. The configuration even works but cannot be changed. When reentering the configuration all previous inputs are lost. This bug can reproduced with a new project: Configure a sql database project by dragging localized fields (e.g. Name_EN) as child fields of the original fields (e.g. Name_DE), accept the configuration and leave the configuration mode. When reentering the configuration mode, all changes are lost, that is the child fields are again in the same flat hierarchy level as the original fields.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Matthew, in the moment we are exhibiting at the Tech-Ed EMEA in Barcelona and do not have access to a SQL-Server test system. Perhaps there is one helpful hint you could try until we have the ability to get further into it. The Sisulizer project file is a XML file. It might be faster if you add your database with all fields, save you .slp and then try to adapt the .slp (a XML file) e.g. in Notepad. I've not tested that from here while I've not database server on my laptop. But it might worth a try for a quick solution. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Matthew Member
|
Hi Markus, thanks a lot for this tip! By changing the content of the project file I'm able to retain my previous changes and it is really a piece of cake to configure the database fields in the xml-code. I am really happy with this solution. As far as I'm concerned you don't need to reproduce my configuration error. Although I have some questions concerning the necessary xml attributes: A Part of the xml file looks like this: May I remove the table ="dbo.ManuProcessStepClasses" and the field "DIN" which have no translations? May I remove the xml-attribute id="ParentId" in the first table? Does the attribute 'method="dlField"' indicate a translatebale table? Please feel free to answer any time you like, I am not in a hurry any more. Thanks again and good success at the Tech-Ed, Matthew
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Matthew Member
|
The copied xml-code didn't show in the previous message, so I type it here:
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Matthew Member
|
As xml-code won't show at all, I try to type it without the brakets: table name="dbo.ManuProcesses" method="dlField" id="ParentId" field name="DIN"/ field name="ImageHash"/ field name="Name_DE" field name="Name_EN" lang="en"/ field name="Name_FR" lang="fr"/ /field field name="Number"/ /table table name="dbo.ManuProcessStepClasses"/
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Matthew, we do not recommend to edit the XML in general. Sometimes it is just the faster way if you need to change many entries in a batch with search and replace. And sometimes it is a nice workaround if the editor denies something that should be possible. Here at support we do not have a documentation for the .slp where I find out what you changes you ask for may cause. Perhaps you make a copy of the .slp and find out if SL is going to like it. But my advice would be to not stress the system too much until we find the reason why the editor could not save the needed settings :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 12:46 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer looses database fields configuration | |
Sisulizer software localization tool - Three simple steps to localize
