|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2 3 4   |
|
|||||||||||||||
| Release 282 doesn't find textfields in database - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Matthew Member
|
If I invoke 'Scan for changes' on my existing Sisulizer database project or if I create a new database project for my sql database some fields are not shown. We use a pattern like 'Name_DE', 'Name_EN', Name_FR' for our translatable database fields. Most of the tables are recognized and I can choose the '_DE' field as the original language field. But in three tables (out of about 50 translatable tables), the '_DE' field is not shown in the database items list whereas the '_EN' and '_FR' fields are available. What do you need to reproduce the error?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Matthew, Is this related to this: http://www.sisulizer.net/reply.php?topic_id=1382 ? What database do you use? Do I understand it right that in most (47) tables the new feature works works but in 3 it fails. Can you see a difference in the table structure of these 3 tables? If you can not find an issue then you could make a dump of 4 tables (the 3 wrong and one where it works), plus your .slp and upload them using the Private Upload button right above the post. Depending on the database you use it can take a while to look into that. Please keep in mind that we exhibit in San Jose and Tokyo this week: http://www.sisulizer.com/software-localization-news.shtml#sisulizerlive2009 Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Please also check upper/lowercase... name_FR might be != Name_DE. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
This topic has the same database as http://www.sisulizer.net/reply.php?topic_id=1382. Thats the relation between those two topics. Seeing one is a question how to use the new feature and one looks like a bug, I thought it wiser to separater those two topics. Or is it easier for you to maintain one big topic? As for the database: We use the Microsoft SQL-Database (a standard SQLExpress edition will suffice). I try to make this as small as possible while retaining the error. I'll send you the backup of this small faulty one as soon as possible. Is this ok with you?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Yes. Because of the conferences we take part we might not be able to get a result for it before late next week. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Attached is a backup of a reduced version of our database. To reproduce the error(s) you should restore a new database from the attached file and create a new database project in Sisulizer using this database. The errors / questions I have are: - How does the automatic analysing of the _DE, _EN, _FR pattern work (I just don't know how to invoke it)? - In the tables 'Clients', 'MasterMachineTypes', 'MasterMachine', and 'MasterRawMaterialTypes' the ..._DE fields are not recognized by Sisuzlizer
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, While I do not have the specific database server needed to reproduce that I forwarded it to our database specialist. I hoped your dump would be in some readable SQL script (like MySQL creates) so I could use it with my server. But your data is in binary format. To my knowledge the detection of the _XX field sets is happening automatically while you create a Sisulizer project from it. If it worked with your other tables it should also work with these you send. I hope to have some answer to this end of next week. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Vielen Dank für die jeweils sehr schnelle Antworten. Anbei habe ich die Datenbank noch einmal als Skript angefügt.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
OK, This time also the Private Upload button worked better for you. The new upload is linked to the topic. Thank you for that. I'll give your script later a try. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
OK, Perhaps you can make some test. I could not use your script with my server but I found one difference between the tables using Name_XX. Sometimes the fields are in a row and sometimes they are split like: [Name_DE] [nvarchar](100) NULL, [ModificationDate] [datetime] NOT NULL, [ExternallyManaged] [bit] NOT NULL, [Guid] [uniqueidentifier] NOT NULL, [Obsolete] [bit] NOT NULL, [Name_FR] [nvarchar](100) NULL, [Name_EN] [nvarchar](100) NULL, Can you please make a test if Sisulizer would group them if the structure would be like this: [ModificationDate] [datetime] NOT NULL, [ExternallyManaged] [bit] NOT NULL, [Guid] [uniqueidentifier] NOT NULL, [Obsolete] [bit] NOT NULL, [Name_DE] [nvarchar](100) NULL, [Name_FR] [nvarchar](100) NULL, [Name_EN] [nvarchar](100) NULL, ? My guess is, that the database wizard has a problem to group them if they are not in a row. If it is that I hope you can change the order of the fields. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hi Markus, I already tried this field order change to no avail. I also tried the other way round, that is, to create a new database with some odd order of the translation fields to enforce this error but in that case it didn't occur.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
OK, then it must be something I don't see and we can not fix without the help of our R&D. I already opened a case. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Short feedback. Build 284 will solve the problem Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
There is one remark I got from R&D I need to share: There is one problem in your database. There is no original data in the Name_xx field. One of those fields must be set as original (e.g. Name_EN). This original field then must have values. Otherwise Sisulizer will not scan the field. The screenshot shows the empty fields. So you need the new build 284 coming in the next days plus data in the Name_xx field used as original language. Sisulizer will fill the translations to the other Name_xx fields so these should be empty. Markus Attachment: Untitled.png (Downloaded 88 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Thanks a lot!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Hello, I tested the new Sisulizer version 285 but the same errors remain in the mentioned tables ('Clients', 'MasterMachines', 'MasterMachineTypes', and 'MasterRawMaterialTypes'). I created a new project and all other fields with the pattern (_DE, _EN, _FR) were recognized (Thank you very much for this new feature!). Only these four tables didn't work. The field with the '_DE' extension wasn't even available in the sisulizer field list. What is even more cumbersome is another error: The new version 285 (the same with 281) won't read all of my data entries. In my newly created project only about 5 percent of the entries are recognized when scanning the database. When updating my old project none of the changes in the database is recognized at all. As the content of our database didn't change much since I sent you the backupfile from our sqlexpress-database you should be able to reproduce the error. If not, I can send you another backup. As we need to do the translation very fast, I ask you to send me an older version (e.g. 275) of sisulizer as with this version a translation was possible. Thanks in advance, Matthew
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hello, I tested the new Sisulizer version 285 but the same errors remain in the mentioned tables ('Clients', 'MasterMachines', 'MasterMachineTypes', and 'MasterRawMaterialTypes'). I created a new project and all other fields with the pattern (_DE, _EN, _FR) were recognized (Thank you very much for this new feature!). Only these four tables didn't work. The field with the '_DE' extension wasn't even available in the sisulizer field list. What is even more cumbersome is another error: The new version 285 (the same with 281) won't read all of my data entries. In my newly created project only about 5 percent of the entries are recognized when scanning the database. When updating my old project none of the changes in the database is recognized at all. As the content of our database didn't change much since I sent you the backupfile from our sqlexpress-database you should be able to reproduce the error. If not, I can send you another backup. As we need to do the translation very fast, I ask you to send me an older version (e.g. 275) of sisulizer as with this version a translation was possible. Thanks in advance, Matthew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Matthew, We’ll continue investigation on this issue. I sent to you PM with download (275 build) information. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Matthew Member
|
Hello Janusz, thanks a lot. Now I am able to do my translation with an older version of sisulizer.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Matthew Member
|
Have you been able to reproduce the errrors? I really need the corrected version.
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:49 am | Page: 1 2 3 4 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Release 282 doesn't find textfields in database | |
Sisulizer software localization tool - Three simple steps to localize
