Dmitry Timoshkov wrote:
Then the correct will be change all resources with SUBLANGE_DEFAULT to SUBLANG_NEUTRAL until someone localize them? I can modify this if is the correct.
Actually there was a completely opposite patch committed recently:
2003-01-05 Shachar Shemesh winecode@sun.consumer.org.il Change the SUBLANG_NEUTRAL clause in all winelib applications to SUBLANG_DEFAULT, as they should be.
I vote to revert that patch.
Then perhaps I should explain why I submitted this patch.
The problem was with notepad. If my locale said "he_IL", it would display the menues in Danish. The reason was that, failing to find Hebrew locales, and failing to find LANG_ENGLISH, SUBLANG_DEFAULT locales, it loaded the first one available.
I then proceeded to research what the situation on Windows was, and the categorical answer was that Visual Studio would not let you create resources with SUBLANG_NEUTRAL. SUBLANG_DEFAULT was the only option. It is for that reason that I believe that SUBLANG_NEUTRAL should only be used as a search qualifier, never as an actual resource.
Now, looking at the code searching path I see: /* 2. specified language with neutral sublanguage */ pos = push_language( list, pos, MAKELANGID( PRIMARYLANGID(info->Language), SUBLANG_NEUTRAL ) );
As far as my understanding goes, this should match the LANG_FRENCH with ANY sublang. Why doesn't this rule correctly find LANG_FRENCH, SUBLANG_FRENCH_CANADIAN? The MSDN is a little hazy on the subject of SUBLANG_NEUTRAL. It has always been my understanding that we should be treating SUBLANG_NEUTRAL as a wildcard. Is that wrong?
Shachar