|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Missing transl. of already localized resx files in combination with linked resources in sln
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Missing transl. of already localized resx files in combination with linked resources in sln - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Jablonski Member
|
Our simplified case is: a solution in VS2010 contains two projects. If there are normal resx files in project p1 and links to this resources from project p2, the already existing translated resources are missing in Sisulizer. Are linked resources not allowed? If a c# project file is scanned it seems to be ok. Thanks in advance Ralf Jablonski
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
What do you mean by "linked resources"? Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jablonski Member
|
If you select in VS2010 for a project 'Add existing item' from the context menu, then specify the file in the file open box and close the box with 'Add as link' button. Ralf
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Ok. I got it. The problem was that the same source (.sln) contained the same fiel twice. Once in project 1 and another time in project 2. When you import .resx file (as the Project Wizard does when it creates a new project) the imported does not know what is the target of the resx. The current Sisulizer imports the file into the first target that is compatible to it (e.g. node in project 1). Because the importer needs one to one mapping (one to many does not work) the second instance in project 2 does not get imported. I improved importing in build 331. Still Project Wizard does not import the values into project 2 but now you can manually import them. Before imporint you have to select the target node in the project tree (see the screenshot). Once you do that Sisulizer imports data into the Two instead of the default one (One). 331 will be released in few weeks. Ilkka Attachment: Untitled.png (Downloaded 11 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 11:33 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Missing transl. of already localized resx files in combination with linked resources in sln | |
Sisulizer software localization tool - Three simple steps to localize
