IssueTracker

It should have been fixed together with small letter. Google fix it!

i've added this to internal [deleted issue].

Any timeframes for the fix?

This character is called a schwa.  Someone said that in honeycomb it is fixed so perhaps the icecream sandwich release which merges honeycomb with gingerbread will fix it

2.3.4 only fixed lower-case character, but not the upper case

Adding my vote- we need this letter!

[Comment deleted]

It is shame that google closes case Without fixing them. The issue is not fixed in ANY version!  I have just checked it on ICS 4.0.3!

It's fixed in the Cyrillic Azeri alphabet, but that has been deprecated since the early 1990's.  If you download MultiLing Keyboard he has it fixed and while it would be nice to have the native LatinIME support an Azeri keyboard, unfortunately I don't think they will ever.  

I do not need to type it in keyboard, so MultiLing will not help me to display website which use "Ə" say for example www.musavat.com

Please fix capital "Ə" for ICS. That is the only reason I uograded my S2 to ICS and then downgraded back to GB.

It is very sad that this issue is not fixed yet
http://code.google.com/p/android/issues/detail?id=53206

This is sort of fixed in later versions, but the problem is that they didn't use U+018F but instead U+04D8 which is the capital Ə from the Azerbaijani Cyrillic alphabet.  This creates a problem with contacts and documents that were created on another device using the correct character, but it won't render properly on the Android.

This is just a partial fix. Glyph added but just for cyrillic, not for latin. No one uses Azerbaijani Cyrillic alphabet, that's why nothing changed for Android users. There is just a simple thing to do, just add latin schwa code for the glyph.

This is still not working on Kitkat!

Still an issue in kitkat 4.4

Duplicate of issue 36919914. Mods, please reopen 10159.

10159 was the lower-case letter. this is the upper-case letter.

Will you ever fix this issue? You do realize that most Azerbaijan websites render incorrectly because of this? Wherever there is a capital letter U+018F, it is either not displayed or displayed as a square. And this letter is on most of the azeri websites. Because of this very serious issue I hesitate to recommend android to my friends in Azerbaijan.

Yup still not working in latest Android release.

Yea, I can confirm the capital "Ə" is  not working on KitKat 4.4.3 too.

We are tracking this issue and hope to have a fix before long. I know it's been a while, sorry about that. Thanks for your feedback.

Thanks for tracking the issue but this shouldnt be a difficult fix. I havent looked at the code but we are talking about a single unicode character.

Can we get some explanation about what is so hard about fixing it, that you have been dragging this issue since 2011? From my perspectives it seems like it would take 10 minutes of work to fix this.

We rolled this into a much larger font fix that ended up taking longer than we expected. It is now fixed in our internal builds.

What does rolling into a larger font mean? This was fixed before and why was it rolled back in first place? Looks like bad code management is in place.

Sorry, my wording wasn't as clear as it should have been. We didn't make a separate change for just this one glyph (which, I agree, would have been fairly simple), but batched it up with a lot of other fixes and coverage expansion. I didn't mean to imply that it was fixed before.

Thanks for elaborating this. Let's hope it WILL BE fixed irreversibly this time.

Is there any specific timing for this fix?  Also will it be back ported into older versions of Android and not just KitKat?  We have a Business Intelligence app on the Google Play store and critical customers are being impacted by this.  Lastly is there a suggested work around that can be done at the app level safely?  Packaging font, etc?

@36 mmile - Google will only push critical security fixes to old versions of Android and even then it is upto the manufacturers and carriers to actually make the updates and send them to their devices. In reality, it's unlikely this will get to any version of Android before L (presuming that's got the fix in). You might get it on older versions if you use a custom rom that specifically cherry picks this fix, but that would likely be exceptional. For suggested workarounds, please ask via a website like StackOverflow.  

Simply outrageous!

We have just tested this with the latest Android L preview release and it still remains an issue.  Will it at least get rolled into L when it is released?

@39 we have no visibility of the code in the upcoming L release until it is fully released. You could try raising an issue at https://code.google.com/p/android-developer-preview/

I've replicated the issue on Android Developer Preview.

https://code.google.com/p/android-developer-preview/issues/detail?id=1483

I submitted this at the above link and is now registered as issue 36906330 (https://code.google.com/p/android-developer-preview/issues/detail?id=1485). I encourage everyone to star the issue so that they know that others are waiting on the resolution to this problem.

This is fixed in Android Lollipop.

Hopefully it is fixed after 4 years

I can confirm that this indeed has been fixed on 5.0.x AOSP Releases.

It is not only NOT fixed it is totally broken in Lollipop 5.1.1. Nexus 7 (1st edition). Are you guys following ANY development framework at all?

Hey objectto...@gmail.com which device did you check it?

I confirmed it on a Nexus 4 running the 5.0.1 AOSP release.  That doesn't mean you aren't correct, but perhaps the fix did not properly get merged into all branches?  Are you running the Google AOSP or a custom AOSP like cyanogenmod?  there shouldn't be any difference.  Also, you need to check to see if the upper case Ə is visible.  That will narrow down whether it's a keyboard issue or if it's keyboard and the UTF character not being visible.

do me a favor and long-press the 'e' and tell me what you get.  If I had to guess I would bet they just screwed up the keyboard layout but the character isn't fixed.  I'm glad there are developers that are working on this, but sometimes I can tell they don't have native speakers checking their work because they miss things like putting the proper keyboard layout in.

sorry, I meant that I think the character probably IS fixed... i'll wait to hear what you get with that long press.

They do not need to have native speakers, they just need to google it!

[Comment deleted]

[Comment deleted]

I agree, that the keyboard is an issue of lazy coding, but if you look at the OP bug report, this bug is for the missing Ə and not the keyboard layout problem.  Yes, it seems like a small difference, but the keyboard layout needs to be a different bug report.  

So did you confirm whether you can see the capital Ə on the screen?

I can confirm character ə is visible with long press e. However issue is different now. Azerbaijani layout on the Google keyboard itself is not switching. You can see from the above attached file, choosing Azerbaijani keyboard does not change the layout, it still shows English letters. With long press you can get all Azerbaijani letters, but İ guess it can not be called a solution...

I can also confirm capital Ə is visible with long press E.

Right, then the status of this bug is correctly closed.  Someone needs to open a new bug report (i'd be willing to bet there is already one) and report the separate issue of the keyboard layout for Azerbaijani is incorrect.  Whoever does it should also note that the spacebar should not read "Azərbaycan" but instead "Azərbaycanca" or "Azərbaycan dili" since the first is a country name.  The second means "In Azerbaijani" and the third means "Azerbaijani Language".

Well-well the original issue was raised because the letter was not visible on the keyboard and on the text before it it was visible. Now it is still not visible on the keyboard or was 5.0.1 AOSP release but broken again in v.5.1.1 release.
It is up to PM to raise a sub-ticket or not. To me I would not mark this a resolved because a new bug means the importance of new bug will be lower than this one. Although I agree a new bug also needs to be logged as a different issue.

If there are problems with the Azerbaijani keyboard, please open new bugs/issues. Thanks. I am only in charge of fonts. Different people are in charge of keyboards.

Thanks roozbeh@google.com I have reported it at https://code.google.com/p/android/issues/detail?id=175366