Issues with custom fonts on new Nexus 7?

Solar2D Android
#1

I am testing one of my apps on the new Nexus 7 and using display.newText w/ a custom font.

I am creating a newText, setting it to center reference point, and putting it in the middle of the screen and 100 pixels from the botton.

For some reason on the new Nexus 7 (but not on my android phones, iphone, or ipad) it will cut the text off and put some of it on the bottom line.  

For example, if I am displaying “Shark”, with system native it will display as 

Shark (centrered)

If I use custom font (only on the Nexus 7 I am seeing this, not sure about old one, this is the new one) and display “Shark” I will get;

Shar (centered)

k (centered, justified left side of the above text)

On my HTC Evo 4, iPhone 5, iPad 3 it shows up fine with the custom font.

#2

I have just upgraded my original Nexus 7 to Android 4.3 and am seeing exactly the same behavior. Prior to the upgrade, text displayed correctly.

You can see in the attached image below where level “76” is incorrectly formatted. Prior to the upgrade, text was displaying correctly.

In summary, appears to be an Android 4.3 issue rather than being device related.

#3

I just saw the same thing on 4.3. Annoying…

#4

The same thing happens on my 2012 Nexus 7 after upgrading to 4.3 (with native.systemFont).

I’ve filed a bug report. Case 25233

#5

We will get the engineers to look into this. 

#6

Fixed in build #1177

#7

I have just upgraded my original Nexus 7 to Android 4.3 and am seeing exactly the same behavior. Prior to the upgrade, text displayed correctly.

You can see in the attached image below where level “76” is incorrectly formatted. Prior to the upgrade, text was displaying correctly.

In summary, appears to be an Android 4.3 issue rather than being device related.

#8

I just saw the same thing on 4.3. Annoying…

#9

The same thing happens on my 2012 Nexus 7 after upgrading to 4.3 (with native.systemFont).

I’ve filed a bug report. Case 25233

#10

We will get the engineers to look into this. 

#11

Fixed in build #1177