|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| Creating a project - again.... - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
jkl Member
|
hi, sorry for getting back to you again regarding this issue - I want to create a project containing .resx files - in the dev folder structure there are both .vbs, .aspx as well as .resx files. When creating the project, I select Create New -> Localize all similar files in a directory. I check the checkbox Localize all similar files first and select *.resx from the dropdown list. I push the Next button and the Select Language window shows up - NOT the dialog where I'm supposed to omit lang specific files such as fi, sv, etc. Pushing the Back button displays the Select Directory window again, but now the Select the file type display .vbs - how come //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Jens, If you use "Localize all similar files in a directory" Sisulizer ignores files it plans to "output". So it will only find the original language files. If it would also find the localized files this would lead to some recursion in the next Scan for Changes. if you go back in the wizard it jumps back to the first file extension it finds. You have to re-select *.resx. You really should consider to localize a single solution file (.sln). This will find the needed .resx from the project and it also will offer you to import existing translations. "Localize all similar files in a directory" was made for platforms which do not have something like project files, e.g. web sites or a bunch of text files. Using "Localize all similar files in a directory" for .NET is a bit like hammering a nail with a pincer while you also have a hammer in your tool case. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
I managed to reproduce the bug your described earlier. I start fixing this. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
great Jaakko - thanks
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jkl Member
|
Markus - the thing is this project relates to ASP.NET and the GUI is using a kind of skin, depending of who the customer is. I found one single .sln file and had it imported but the log says; Project does not contain any resources. //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
Markus - what kind of info does the .sln files contain?
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I'm not a developer. but it should contain the description of all parts making your project. For regular .NET project it is recommend. I have to ask R&D for some enlightenment to ASP.NET :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
that would be great - I'm doing some research on my side as well.... //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jkl Member
|
hi Markus - just tested antother .sln file, not related to ASP and that one worked just fine - everything was imported nicely - this means that you do not need to import the dll nor the resx files if using this single sln - this is really nice.... //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Jens, Instead of .sln you could try a .csproj file. Perhaps that does the trick. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Since Jaakko promised to fix something we should wait what is the outcome of his investigations. If that .sln or .csproj does not work for you now it might be that in the meantime using the pincer ("Localize all similar files in a directory") is an immediate option. But keep in mind that this by design will only find your original files. You can use File - Import to manually import the other languages. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
yes - until now I have imported other languages by using the command Import - as I understand, by using .sln files, you can use Import translation from Localized files instead - correct.... //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
If you would use .sln or .csproj Sisulizer finds all the needed files. It will also look for already translated files and offer to automatically import them (if they are in the right path with the right name). But the import will happen only once when you create the project. Then it is expected that all new translations are entered into Sisulizer and only Sisulizer builds the localized files. So there is no more need to import them again. It is also important to not edit the translations outside Sisulizer. This will lead to confusion. You also can use Project - Add Source... to add more source files to your project. In the file dialog that comes up you can use a multi file select. Perhaps this is also an option. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed three bugs: 1) When adding a dictionary with filter (e.g. *.resx) Sisulizer created several sources instead of one in the case when the root directory did not contains any file matching the filter. 2) Sisulizer did not import existing translations in the above (#1) case 3) When you clicked "Localize all similar ..." check box or click back button in the wizard your current filter selection was replaced with the default value. These fixed are fixed in build 297 that will come out late next week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jkl Member
|
Great - thanks bunches - this is needed for ASP related localization when selecting resx from an archive top level... //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
hi Jaakko - will the fix also affect the Import process in order to use f.x "*.sv.resx" - as it is right now, you have to select one file at a time. //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jkl Member
|
hi - will the 297 build be available today?
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
hi, I have tested the new 297 build and unfortunately I cannot see that the fix has been fully implemented. I still cannot select a file format (*.rex) from a root directory, and get all files from all subdir except the the ones with lang extension. example: from dir C:\PlayPen\WebPortal\... I want to create a project base on all *.resx files residing in all subfolders but omit all resx files with lang extensions e.g. I do not want any *sv.resx files.... this is still not doable in Sisulizer - since this project is based on ASP.NET, I need to use the resx files..... Any feedback on this would be appreciated //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
We don't recommend adding already localized resx files as sources, and for this reason Sisulizer ignores files with standard locales in names. For example when you try add to Sisulizer's project resx file already localized in Sisulizer with option "different", you can get incomplete source. Best
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jkl Member
|
I'm not sure you understand what I mean (or vice versa) - today Sisulizer can omit resx files with lang extensions if you select the files from a folder residing the files - in this case, the application displayes a dialog window asking wheter or not to exclude files with lang extension - BUT if you select .resx files from a top level, where all .resx files are stored in subfolder, Sisulizer picks up all .resx files, regardles of lang extensions or not - in this case no dialog window is displayed where you are able to exclude lang files.... //jens
____________________ //jens |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:31 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Creating a project - again.... | |
Sisulizer software localization tool - Three simple steps to localize
