|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Build only one language - Usage - Three simple steps to localize - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Frede Member
|
Is it not possible to build all files for just a single language at a time. There's the option to build item which does that for a single source. Then there's the option to build all which build all files for all languages. I need to be able to build all files for a specific language. Is this not possible?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Frede Member
|
Oh I think I found it (F6 key). I thought that Build Item was the same thing as right-clicking a node and selecting Build Item, but F6 builds all files. Great!
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
brunis Member
|
How do you get 'Build Item' in context sensitive menu ? i don't see it on any 'sub-node' .. I don't think 'Build Item' does what it should. If i select a single resource file in the left pane and i choose Project > Build Item, it builds all the translation files. 
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Brunis, the menu entries Frede mentioned are only available in the sub-menu for the Delphi platform. But for DotNet selecting the item and then pressing F6 does the same. An item is a source node in the translation tree. In the shot you see a project with two items. You can not build single forms etc. because there can be dependecies between these elements. So only complete items can be build. Best Markus Attachment: build-items.jpg (Downloaded 15 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
brunis Member
|
I see. Since the visual studio importer is broken for my particular project, i've imported every .resx file manually. It would be nice with a context sensitive 'build item' in this case. Like i described before, all the .resx files are being considered the same project and it builds them all This might be the intended behaviour from a menu perspective, but treating a single .resx seperately should still be possible (eg. a context sensitive menu from right clicking a single resource). If you would please consider this functionality. [edit] Also, just building changed items would be useful! [/edit] Last edited on Mon Feb 4th, 2008 05:21 pm by brunis |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
brunis Member
|
I'm sure you can imagine the problem in having to svn commit approx. 5000 .resx files instead of just 1 for every little fix.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Brunis, our CTO has to decide if we can implement that. I already pointed him to this thread. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
We will implement build feature per item in near future (few weeks). Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 03:41 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) > Usage - Three simple steps to localize > Build only one language | |
Sisulizer software localization tool - Three simple steps to localize
