Apologies in advance if this isn’t playing by the rules.
Back in November, we discovered a bug (presumably in the Win32 subsystem) in
the implementation of LoadString. We entered a support request, and were
told that ‘a bug was fired’ and that ‘the bug ID is 1475.’
The bug is somewhat amusing, if not entirely on topic. If you have string
resources in more than one language, LoadString does not respect the thread
locale properly. If the thread locale is Japanese and the UserDefaultLocale
is English, it correctly retrieves Japanese strings. But if the User locale
is Japanese, it retrieves English! This makes multi-language resource files
less than useful.
Anyway, the material question is this: is there any way to find out if this
bug will be fixed in a service pack? Or any more about its detailed nature?
I’ve “bugged” the original support engineer, but it isn’t clear that his job
extends to extracting this intelligence.
Thanks in advance,
Benson Margulies
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com