I did that sometime ago in my local tree. The problem is that it makes the resources uneditable in the MSVC builtin resource editor (since the included files aren't taken into account). Also I noticed some of the neutral image resources are currently inside the LANG_GERMAN block...
Do our resource files need to be MSVC ResEd compatible? If they do, I'm guessing this is gonna cause issues for many other resource files too, as we know how 'odd' the MS resource editor is.
I don't have a copy of MSVC so I can't test, but does MSVC still allow building and linking of .rc files written in formats other than the MSVC standard? (e.g. by hand) I know this is a constraint in the future for the building of ROS under MSVC.
Well, it's possible to split the resource file into several languages while remaining compatible to VC++'s editor using the TEXTINCLUDE sections. As I see there is quite a lot interest in this, I will try to do this conversion. The problem is: I am not sure, I can do this right for all those languages. So I ask the native speakers to have a look at the different language files after the split to see if it is all correct.
Regards,
Martin