Keypad decimal incorrect on some layouts

[Sergio Henrique]

When using the Portuguese (Portugal) keyboard layout, the keypad decimal is
mapped to a point, which is wrong, it should be mapped to a comma. This
happens on all applications (notepad, command line, outlook, etc) except on
Excel... probably because it does checks on it's own instead of
relying on the OS.

If I use the German (Germany) or Portuguese (Brazil) layouts, which both
also use the comma as a decimal deparator, I get the expected behaviour and
all decimal key input is translated to commas
everywhere on the system.

Is there a solution to this problem? I can't find anything about this on the
web.

 

[Pegasus \(MVP\)]

When using the Portuguese (Portugal) keyboard layout, the keypad decimal
is mapped to a point, which is wrong, it should be mapped to a comma. This
happens on all applications (notepad, command line, outlook, etc) except
on Excel... probably because it does checks on it's own instead of
relying on the OS.

If I use the German (Germany) or Portuguese (Brazil) layouts, which both
also use the comma as a decimal deparator, I get the expected behaviour
and all decimal key input is translated to commas
everywhere on the system.

Is there a solution to this problem? I can't find anything about this on
the web.

I am reluctant to load various foreign-language keyboards on
my machine, hence I cannot test your claim. However, if all
else fails then you could use remapkey.exe from the Windows
Resource Kit to place your comma where you want it to be.

 

[Sergio Henrique]

I was actually more worried about the end users of an app I'm developing so
that wouldn't solve my problem. What I've been doing for some time now is to
replace points with commas on places where there's numeric inputs but it's a
rather "dirty" solution and messes it all up on different locales.

I've decided to post here after all this time because I've just realized
other layouts would work properly so this might be a known bug in Microsoft
OS's.

Also, to my knowledge, it's unlikely that testing this would have negative
effects on your system.

 

[Pegasus \(MVP\)]

See below.

I was actually more worried about the end users of an app I'm developing so
that wouldn't solve my problem. What I've been doing for some time now is
to replace points with commas on places where there's numeric inputs but
it's a rather "dirty" solution and messes it all up on different locales.

I've decided to post here after all this time because I've just realized
other layouts would work properly so this might be a known bug in
Microsoft OS's.

In view of the very large number WinXP installations that are
currently in operation, it is very, very unlikely that your problem
is due to a bug. It is far more likely due to a misunderstanding.

Also, to my knowledge, it's unlikely that testing this would have negative
effects on your system.

You are quite correct. However, I already have four different
keyboard layouts installed and I prefer not to add any others.
It gets a little confusing after a while. I might have a go at it
on Monday when I have access to a test machine.

 

[Pegasus \(MVP\)]

When using the Portuguese (Portugal) keyboard layout, the keypad decimal
is mapped to a point, which is wrong, it should be mapped to a comma. This
happens on all applications (notepad, command line, outlook, etc) except
on Excel... probably because it does checks on it's own instead of
relying on the OS.

If I use the German (Germany) or Portuguese (Brazil) layouts, which both
also use the comma as a decimal deparator, I get the expected behaviour
and all decimal key input is translated to commas
everywhere on the system.

Is there a solution to this problem? I can't find anything about this on
the web.

You posted your question in at least three separate newsgroups.
Check the answers you received elsewhere, then have a look at
this link to see the advantage of cross-posting versus multi-posting:
http://www.blakjak.demon.co.uk/mul_crss.htm
Multi-posting is not a good habit because it leads to duplication
of effort.

 

[Sergio Henrique]

You posted your question in at least three separate newsgroups.
Check the answers you received elsewhere, then have a look at
this link to see the advantage of cross-posting versus multi-posting:
http://www.blakjak.demon.co.uk/mul_crss.htm
Multi-posting is not a good habit because it leads to duplication
of effort.

If you look closely enough though, you'll see that I've posted this on 2
newsgroups, one with a regional scope and another with a global scope. It's
2 different languages so multi-posting would have to be used anyway.

You'll also notice that I've waited 2 days for a solution before I posted on
a more "general" newsgroup like this one, hence multi-posting again. Notice
too that there is no single newsgroup where this issue fits perfectly.
There's no "locale/regional settings" or whatever newsgroup.

I do aknowledge your point on the advantages of cross-posting that I was
unaware of. Thanks.