Although "," and "." correctly output the stop characters, they do so in a way
that's not very Burglish-y. Unfortunately, "," and "." are short-circuited into
the way a RomanInputMethod behaves, so changing the behavior now would change a
whole lot of code.
Since the functionality only affects a few minor words, I'm leaving it in for
1.8. However, I'm filing this bug to remind myself that this needs to be fixed
for 1.9. A quick, general re-thinking of how we manage input is only possible
after we evaluate the _current_ (new) input system, and I'd like users to try
out the new input systems a bit before changing it all again.
Original issue reported on code.google.com by seth.h...@gmail.com on 16 Jun 2010 at 3:20
Original issue reported on code.google.com by
seth.h...@gmail.com
on 16 Jun 2010 at 3:20