Emojis Won't Scale Beyond 16Px Font-Size on iOS 7

Emojis won't scale beyond 16px font-size on IOS 7

If this is still interesting for anyone (I forgot that this was still open) then the "solution" was to set the meta tag for iPhones to:

<meta name="viewport" content="width=320"/>

This ensures that the iPhone scales the content up to fit the 640 pixels (or more) the screen has, and the emojis with 16px size will now be twice as big. However, this will only scale them up to a reasonable size. It still doesn't fix it for the people wanting to control the font-size completely.

Drawing scaled emoji icons on iOS

The emoji icons are stored as PNG files in /System/Library/PrivateFrameworks/WebCore.framework (I found this info on the net, but I can't confirm since I don't own a jailbroken iPhone). I don't think it is possible to scale them without loosing quality.

Emoji shrink on mobile safari ( and UIWebView )

It works for me when I set the font to Apple Color Emoji like this:

font-family: 'AppleColorEmoji';

But in my opinion the icons don't look good at huge sizes.

Increase the font size of emoji characters in a UITextView in iOS 5.x

Have you tried setting the UITextView's font to AppleColorEmoji as well? On iOS, it seems that AppleColorEmoji is the only font that will draw scaled-up emoji. Use any other font, and the emoji never get larger than about 20x20 pixels, as you've noticed.

I did my tests using this handy free app called Fonts!, which is a nice way of getting quick feedback on the actual device itself.

I note that the Game Center app seems to be able to mix an interesting font with scaled-up emoji, so clearly it IS possible to do better than the (rather pedestrian) emoji font! I don't know whether this is something special in its code, though, or something special about the font it uses, which looks like a custom one.

HTTP proxy server

Take a look at micro_proxy. It implements all the basic features of an HTTP/HTTPS proxy, in only 260 lines of C code.

Another very simple implementation can be found at Proxy.

Choosing a simple web application framework

rails is a good choice - it is simple for simple things, while allowing more complex things to be possible (always a good sign). There is a little bit of learning curve initially, but that's true of all frameworks.

If you're happier in Java, you could also look at Groovy + Grails, a very similar framework with a Java slant (groovy is kind of like a cross between java and ruby, and you can mix and match Java and Groovy classes in the same project).

---

Related Topics