Closed Bug 825091 Opened 12 years ago Closed 11 years ago

Uppercase theta and epsilon characters are missing

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-basecamp:-, b2g18+ affected, b2g18-v1.0.1 affected)

VERIFIED FIXED
blocking-basecamp -
Tracking Status
b2g18 + affected
b2g18-v1.0.1 --- affected

People

(Reporter: dsubramanian, Unassigned)

References

()

Details

(Whiteboard: visual design, qa-verified, yedo, testrun 5.1, inarirun1, leorun1,leorun3)

Attachments

(1 file)

Environment : Unagi phone, v1.0 build ID 20121217070202

Set the keyboard to English, Portugese brazilian and Spanish. Install Keyboard app UI on the device. Select Input type "text" and hold on "O" for options to be displayed.

Repro steps:

1) Install Keyboard application UI from http://bit.ly/UgIMN4 on to the device
2) Click on the app "UI tests" from home screen
3) Select "Keyboard" test from the "UI tests" list
4) Click On the input type = text
5) Tap on Cap Button 
6) Hold on "O" 
7) Special characters are displayed

Expected:
 "O" displayed

Actual:
User able to see the spl characters for "O"
In addition to special characters of "O", special characters of "E" has issues too!
blocking-b2g: --- → shira?
blocking-basecamp: --- → ?
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Triage: BB-, tracking-b2g18+ - polish
blocking-basecamp: ? → -
tracking-b2g18: --- → +
Keywords: polish
Verified on Unagi device Build ID: 20130104070203
v1.o
This is a problem with characters missing from the default font. Open this testcase in the browser to see the same problem:
http://people.mozilla.com/~mleibovic/test/chartest.html

This isn't a problem on desktop Firefox.
Component: Gaia::Keyboard → General
QA Contact: wachen
Summary: [Keyboard] Uppercase special character for "O" does not bring up all the spl characters → Uppercase theta and epsilon characters are missing
UCID: owd-2878
https://moztrap.mozilla.org/results/case/63428/
Whiteboard: testrun 2
setting blocking-b2g=tef? as these keyboards affect v1.0 market.
blocking-b2g: shira? → tef?
blocking-b2g: tef? → tef+
Assignee: nobody → rlu
To fix this issue, what we need is: 
 1. Update MozTT font to include the missing symbols.

or
 2. Remove the symbols from the alternative char menu.

I have talked to Patryk about solution #1 in work week. 

Dear Patryk,

May I know if we could have any updates for the font files?
Thanks.
Flags: needinfo?(padamczyk)
I am going to take this bug, we're talking to font vendor now to expand the font to include GREEK
Assignee: rlu → padamczyk
Flags: needinfo?(padamczyk)
:patryk,
what's the ETA on this?
Keywords: polish
Whiteboard: testrun 2 → visual design UX-P1 yedo
Whiteboard: visual design UX-P1 yedo → visual design UX-P1 yedo font
Patryk told me this can be moved off the tef+ list.
blocking-b2g: tef+ → shira?
blocking-b2g: shira? → shira+
Whiteboard: visual design UX-P1 yedo font → visual design UX-P1 yedo font [triaged: 01/22]
Because shira should support more European languages, we shira+ this one.
:patryk, do you mind updating the latest on this bug? thanks
Not all the spl character for letters "O" and "E" are displayed. 

This issue is still found on Unagi device Build ID: 20130125070201 using the december 5th kernel v 1.0.0-Prerelease.
Special build for Test Run 3 [unagi only] - 1/25/13
Gecko:  http://hg.mozilla.org/releases/mozilla-b2g18/rev/94a2d6fcdfde
Gaia:   6369dbf33b622faf4b4d176fed30b77c5c319dfc
Test Suite Name: KEYBOARD
UCID: OWD-2684
Whiteboard: visual design UX-P1 yedo font [triaged: 01/22] → visual design UX-P1 yedo font [triaged: 01/22] testrun 3
Want to make sure everyone knows that Shira is targeting 2/15 code freeze. 
Shira+ bugs needs more attention for unassigned, needinfo?,  review?
Full regression test is planned on 2/6. Need to have shira+ bugs landed by the end of 2/5 to be covered in full regression testing. Thanks
Build ID: 20130130070201
Kernel: Dec 5
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/4593f3e765eb
Gaia   f7f5a0cd17e3d04308cc5850b254947e127122b9
Test suite:Keyboard
Ucid:2878

Some of the spl characters for  letter "O" are still missing
Whiteboard: visual design UX-P1 yedo font [triaged: 01/22] testrun 3 → visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4
In addition to the above comment:

Special characters are missing for both uppercase and lower case "O"
hi Patryk, please update the status once you have the time frame for the fix.
On comment 13, it moved off tef+ per your comment. I wonder what's the background on this? hope to understand that if we could live with this bug in TEF with English/Spanish/Portuguese, can we live with this bug with extra languages added in shira (below). Thanks 

Croatian (hr), Czech (cs), English (en-US), German (de), Hungarian (hu), Polish (pl), Romanian (ro)
Flags: needinfo?(padamczyk)
We are in the process of getting the further work to include Greek and Cyrillic approved by our legal/finance departments. We want to target v.1.1 for the fix. I will update the bug on the status once we have approvals.
Flags: needinfo?(padamczyk)
Whiteboard: visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4 → visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4, yedo
Kev, it does not seem like this bug is possible to be fixed for v1.0.1. do you think this will be a 100% blocker for v1.0.1 target markets?
Flags: needinfo?(kev)
We don't think this is a blocker, but we've reached out to l10n drivers to verify.
blocking-b2g: shira+ → shira?
Is it only Ó and É or all accented letters are impacted?

If U or A are also wrong, this means we have bugs in the TEF version, because we have strings using them in Spanish:

http://transvision.mozfr.org/?sourcelocale=en-US&locale=es-ES&repo=gaia&search_type=strings&recherche=%C3%9A
http://transvision.mozfr.org/?sourcelocale=en-US&locale=es-ES&repo=gaia&search_type=strings&recherche=%C3%81

Comment 19 mentions that lowercase o is also impacted, this is a very common letter in Spanish words:
http://transvision.mozfr.org/?sourcelocale=en-US&locale=es-ES&repo=gaia&search_type=strings&recherche=%C3%B3

uppercase Ó is only used in one string in Spanish and uppercase É in one string in Portuguese.

For other locales mentioned, I can spot Ö in German:
http://transvision.mozfr.org/?sourcelocale=en-US&locale=de&repo=gaia&search_type=strings&recherche=%C3%96

Č is also common in Czech an other Slavic languages in case this accented uppercase letter is impacted too:
http://transvision.mozfr.org/?sourcelocale=en-US&locale=cs&repo=gaia&search_type=strings&recherche=%C4%8C
Since we have a shira deadline of Friday let's get this confirmed - QA can you respond to which characters are problems and also wait to hear from l10n drivers.
Keywords: qawanted
QA Contact: nhirata.bugzilla
We did reply, both here and in email.
(In reply to Pascal Chevrel:pascalc from comment #24)
This only affects uppercase theta and epsilon.
Removing qawanted and needsmoreinfo as all the requested information has been given.

Comment 27 Patryk Adamczyk [:patryk] UX 2013-02-13 10:06:10 PST
This only affects uppercase theta and epsilon.
Flags: needinfo?(kev)
Keywords: qawanted
As we understand it then, this doesn't affect shira markets and we'll push leo? there may need to be another bug filed on removing affected locales from v1.0.1 altogether - Stas is that something you can do?
blocking-b2g: shira? → leo?
Flags: needinfo?(stas)
We're going to have a call with kev early next week to drill down on 1.0.1 state in terms of locale support.

At this point, neither I nor stas can make confirmative statements on which of our fonts support which code points.
Flags: needinfo?(stas)
Blocking- for now. Once it's determined that this affects locales in markets we're shipping in, please renominate.
blocking-b2g: leo? → -
Whiteboard: visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4, yedo → visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4, yedo,testrun 5.1
Whiteboard: visual design, uxbranch, landed in uxbranch, qa-verified, testrun 4, yedo,testrun 5.1 → visual design, uxbranch, landed in uxbranch, qa-verified, yedo,testrun 5.1
Whiteboard: visual design, uxbranch, landed in uxbranch, qa-verified, yedo,testrun 5.1 → visual design, uxbranch, landed in uxbranch, qa-verified, yedo, testrun 5.1
blocking-b2g: - → leo?
blocking-b2g: leo? → ---
Mass edit to set tracking-b2g18+ for these UX bugs that were called out for v1.1
Whiteboard: visual design, uxbranch, landed in uxbranch, qa-verified, yedo, testrun 5.1 → visual design, qa-verified, yedo, testrun 5.1
This issue is reproducible on the Inari device.

Inari Build ID: 20130418070206
Kernel Date: Feb 21
http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0c76ef5f8677
Gaia: 64d5096e1746bd4b08bc1bf69844d164ac961970

UCID: owd-2864
Link to failed test case:https://moztrap.mozilla.org/runtests/run/1105/env/316/?pagenumber=1&pagesize=100&sortfield=order&sortdirection=asc&filter-id=6451&filter-suite=253

Set the keyboard to English, Portugese brazilian and Spanish. Select Input type "text" and hold on "E" for options to be displayed.
Whiteboard: visual design, qa-verified, yedo, testrun 5.1 → visual design, qa-verified, yedo, testrun 5.1, inarirun1
Whiteboard: visual design, qa-verified, yedo, testrun 5.1, inarirun1 → visual design, qa-verified, yedo, testrun 5.1, inarirun1, leorun1
This issue is reproducible on the Leo device.

Leo Build ID: 20130610070206
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/8e3f39363c54
Gaia: ce3b99781d182ad550a325206990c249b0dbcf0e
Platform Version: 18.0

UCID: owd-2684
https://moztrap.mozilla.org/runtests/run/1475/env/314/?&pagenumber=1&pagesize=50&sortfield=order&sortdirection=asc&filter-id=6455&filter-suite=253

Set the keyboard to English, Portugese brazilian and Spanish. Select Input type "text" and hold on "O" for options to be displayed.
Whiteboard: visual design, qa-verified, yedo, testrun 5.1, inarirun1, leorun1 → visual design, qa-verified, yedo, testrun 5.1, inarirun1, leorun1,leorun3
Bug 897009 should fix this, Eric please verify.
Assignee: padamczyk → nobody
Depends on: 897009
Flags: needinfo?(epang)
Hi Deepa,  I want to verify that this is fixed but I'm not sure how to install the Keyboard Application UI.  I used the link but I'm not sure how to install it on the device.  Can you help?  Thanks!
Flags: needinfo?(dsubramanian)
Hi Eric,

You should be able to verify this issue by clicking on a normal input field, like in SMS message field or contacts app.
That UI Test app in Comment 0 is just a util. app that provides all different kinds of <input> element.

Please let me know if you have any questions.
Thanks.
Thanks Rudy!

Tested on device and appears to be fixed
Unagi phone, v1.1 build ID 2013090041201

Naoki, can I make this as verified fixed?
Flags: needinfo?(epang) → needinfo?(nhirata.bugzilla)
verified : 
Gaia   aa4180e9286d385fa6b62d236f30fb24cd8b93e9
SourceStamp 218d4334d29e
BuildID 20130909114657
Version 26.0a1
Buri
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(nhirata.bugzilla)
Resolution: --- → FIXED
Note : Checked all the characters/keys for mojibake/missing characters.
Status: RESOLVED → VERIFIED
Flags: needinfo?(epang)
Flags: needinfo?(epang)
Flags: needinfo?(dsubramanian)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: