Bug 10273 – Auto-capitalization somewhat broken

Bug 10273 - Auto-capitalization somewhat broken


Summary:	Auto-capitalization somewhat broken

Status:	RESOLVED DUPLICATE of bug 10310

Product:	Desktop platform
Component:	Input method framework
Version:	5.0:(10.2010.19-1)
Platform:	N900 Maemo

Importance:	Low normal with 5 votes (vote)
Target Milestone:	---
Assigned To:	Joaquim Rocha
QA Contact:	input-method-framework-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-05-25 21:07 UTC by Aleksandar Mancic
Modified:	2010-05-28 20:38 UTC (History)
CC List:	7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Aleksandar Mancic (reporter) 2010-05-25 21:07:15 UTC

Can't seem to find the exact category so I filled it under general...

SOFTWARE VERSION:
10.2010.19-1

EXACT STEPS LEADING TO PROBLEM: 
1. Enable Auto-capitalization in Settings / Text input
2. Type a dot in Conversations (or any other application that uses native text
input) and add a space afterward.
3. Continue typing and try to de-capitalize the next letter by pressing shift.

EXPECTED OUTCOME:
It will automatically capitalize the next letter, but there is no way to
prevent it. In previous versions one could press (or hold) shift to get a small
letter instead of auto-capitalized one, this method does not work anymore. It
makes text entry painful when entering a text that contains a dot but should
not be followed by a capitalized letter, i.e. well - i.e.

Also, auto-capitalization don't get turned on on a new line as it was in
previous versions.

ACTUAL OUTCOME:
The following letter will be auto-capitalized no matter if you press shift or
not.

REPRODUCIBILITY:
always

Comment 1 Neil 2010-05-25 21:24:24 UTC

I can confirm this happens on UK FW too.

Comment 2 Wichall 2010-05-26 02:07:17 UTC

also experiencing the same issue (uk fw)

Comment 3 Ian Cullinan 2010-05-26 02:18:40 UTC

It occurs to me that this sort of thing would be a lot less confusing in
general if there was some sort of visual indication of what "mode" the keyboard
is in (shift, blue/Fn/symbol or normal) - this would also make using shift/Fn
lock easier.

Comment 4 Nick A 2010-05-26 02:54:12 UTC

*** This bug has been confirmed by popular vote. ***

Comment 5 Mike Trim 2010-05-26 09:53:29 UTC

(In reply to comment #3)
> It occurs to me that this sort of thing would be a lot less confusing in
> general if there was some sort of visual indication of what "mode" the keyboard
> is in (shift, blue/Fn/symbol or normal) - this would also make using shift/Fn
> lock easier.
> 

See bug 6646 (Show Status for Physical Keyboard).

Comment 6 doug.o.hoffman 2010-05-27 01:23:59 UTC

I can also confirm this change in behavior, on US 10.2010.19-1 (fresh firmware
+ eMMC flash).

In addition to after a period-space sequence, this problem occurs for the
initial character in a text box. Only workarounds I've come with up are:
- Type character twice, arrow left (twice with word completion enabled),
backspace, arrow right, go crazy.
- Disable auto-capitalization
- Don't enter text

Comment 7 Andre Klapper maemo.org

2010-05-28 20:33:39 UTC

Summary in bug 10310 described the issue better and is now the place for this.
Marking as duplicate which unfortunately does not automatically transfer your
votes on this. Please vote for bug 10310 if you're still interested in this.

*** This bug has been marked as a duplicate of bug 10310 ***