As you can see in the image below, when I up-voted an answer that had 99 votes, the typeface didn't shrink in order to show a one-lined 100 number.  I'm using Android 4.4.4 on a Nexus 7 (2012).
121325
In the Android app, the vote count on some questions gets wrapped. Thanks to Doorknob's comment I've found that it doesn't appear to be on just those with double digit negative vote counts or those with vote counts of 100 or more. As you can see in one of the screenshots below, the question has a vote count of 429 but is not getting wrapped. Another with 121 votes is though. Each question I've come across with double digit negative vote counts does get wrapped (3 examples of those below).  Same result in both horizontal and vertical orientations. Not sure if it's different on a larger screen size though (mine screen size is 4.3).  I'm on version 0.1.58  Here are links and screenshots for examples:  Negative Vote Counts            100+ Vote Counts Wrapped          100+ Vote Counts Not Wrapped
82276
asked in July explains why it is not possible for the time being to submit content in posts or comments that contains Unihan characters. It’s a spammer thing, fair enough.  As  makes clear, the workaround for posts is to convert your Unihan text to HTML entities: these are parsed and appear correctly.  However, HTML entities are still HTML and as such are not parsed at all in comments, as . In other words, since Unihan glyphs are banned from both posts and comments and HTML entities are not parsed in comments, it seems to be completely impossible to post text containing Unihan glyphs in comments at all, except on sites where the ban has been manually removed, like Japanese.SE.  This seems like a rather substantial limitation. And in any case, the blanket ban on Unihan is unduly heavy-handed and inflexible (not to mention perplexing to the user, when the only feedback you get is “Body/comments cannot contain that content”).  In , tchrist suggested that the ability to post Unihan glyphs could be made a rep-based privilege; that is, a certain amount of reputation is required to include these glyphs, otherwise it fails. A requirement of, say, 125 rep points would presumably cut off at least 99.99% of spammers, and it would have the added benefit of being able to maintain—and broaden—the restriction indefinitely to mitigate spam, while still allowing legitimate users to post relevant content.  (The feedback message would have to be improved as well, though; something like, “Due to large volumes of spam written in certain non-Latin scripts, you need at least 125 reputation points to be able to include non-Latin text in your post” or words to that effect.)  Can this be implemented?  Alternatively, as pointed out in Normal Human’s reply, since comments already require a certain amount of rep meant to deter absolute newcomers (and, by extension, also spammers), can the ban just be removed from comments and applied only to posts?  (Editing this just to bump it on the front page, to hopefully have some kind of discussion or feedback on the matter.)
109817
I recently came across  answer on . It appears to be written in a font designed to look like hard-to-read, old fashioned handwriting. As such, to make it easier to read, I copy/pasted it into gedit (a text editor that does not support formatting — like Notepad). To my surprise, the strange formatting stayed. Upon further inspection (i.e., Googling the most strange looking characters, noticing the year appears to be written partially normally) I came to the conclusion that they are a set of strange letter-like characters in Unicode.  My question has two parts:   Am I correct about what these characters are? If so, why does Unicode contain extra characters that appear to serve no purpose other than that of fonts?
4798
I have white blank on the posts.    App Version: 1.0.89 Device Manufacturer: Meizu Device Model: m2   OS Version: 5.1 (1464689330)    I can't see the questions and the answers and the comments.  I saw that it's a common issue..  Does it have a fix?   EDIT -  I saw  answer. This answer is ~2 years old. It says that it will fix in the next update.  His version is 1.0.59 - mine is 1.0.89. Huge different.   The problem is still exists!
28019
An issue similar to that described in  and likely to be related.  The comments for a question may vary in size:         Chrome for Android on Nexus 7 running 4.2.2 Jelly Bean. This also occurs on Firefox for Android:
66626
I just updated my iPhone 7 Plus to iOS 13 tonight and noticed that the post menu in the Stack Exchange app became close to unreadable, because the font/text is too large to be properly displayed. Luckily we can still recognize the icons...    (Yes, app development has been frozen for quite a while but the app continues to serve me well.)
71105
What is the typographic reasoning here? Does it make the text look less crowded?
61054
On the full site, there's that helpful Markdown toolbar above the post box:   This is conspicuously missing in the mobile site:   It's difficult just to get a bracket on my iPad. Backticks aren't even available. If there's a view that really needs it, i vote mobile.
100549
Background On mobile precise positioning of the cursor is extremely difficult. When entering a spelling mistake I will usually delete the entire word and retype rather than trying to select the mistake itself. Sometimes deleting an entire sentence and retyping is easier than repositioning the cursor. The Bug When entering a comment on the mobile version of the site if the line is exactly a line long then the space (between words) is not recognised. For example if I type (as a comment on a question, answer comments are a different length)  This seems like a good sentence to test the irritating system[SPACE]  Then the space is not recognised (how ever many spaces I add) and so the first word of the next line is run together with the last word of the first line, so  This seems like a good sentence to test the irritating systemwhich  After the word has fallen onto the next line I can go back and reinsert the space as a work around. However; as I say precise positioning on a phone is extremely difficult Reproducing this bug seems very sensitive to the line being exactly one line long. I had to experiment with long letters (like 'w') and short letters (like 'f') to get it exactly right. My test sentence quoted above is likely to be dependant on my screen size. Results so far: ANDROID Galaxy s3 Standard Android Browser: exhibits bug  - reported by R Tingle &amp; Rory Alsop Dolphine browser: exhibits bug Chrome: no bug Galaxy S2 Standard Android Browser: exhibits bug* Galaxy S1 Standard Android Browser: exhibits bug - reported by yuvi *In the case of the Galaxy S2 the space appears to &quot;hold&quot;, ending up at the end of the line. But on starting the next word the space disappears WINDOWS PHONE Lumia 800 Standard Windows Phone browser: no bug APPLE Ipad Recent Model: exhibits bug - reported by Rory Alsop
83227
I understand that there is an upper limit. But why do you have to type at least 15 characters to post a comment? It is easy to work around it anyway (like adding dots or other useless things).
40591
For example,  when displayed in the Android app doesn't show the ǝ character properly  in the username:    This happens in their profile and on posts.  Android app version 1.0.18 on Samsung Galaxy S3 and Android version 4.1.2.
110624
that multiline messages in chat don't support Markdown (except for fixed-width and quote formatting). But if such a message gets starred the Markdown will be rendered after all:    That is probably usually not a big deal, but I thought it's worth documenting (and very occasionally, a multiline message might rely on Markdown not working such that it becomes unreadable when starred).
42055
Does the Android operating system support installing new fonts?  I am that person who adores calligraphy and improving handwriting, and I am proud to say that my handwriting is now more beautiful than my teachers in almost every language I know! Anyway, can anyone answer that question (about Android fonts), because this will judge if I will buy a ruuning-Android tablet pc or not!
15376
Have a look at   One of the bolds works, and the other one just turns up as ** in the actual post.  This is the string that isn't working: **x**ml n**ib**  Which renders as: xml nib
44376
I wanted to amplify the effect of specifying the font size. So I tried: {\tiny\tiny Super tiny text!} But that doesn't seem to work. I needed suggestions to achieve the same goal.
93104
The problem can be easily found while using the Android app and mobile web. Just find a question with a close vote on it and you will see this:       close 1   is what it says there. Can we fix it so we can have the parentheses around the close vote count so it can look like the way it is supposed to look?:     close (1)
847
There is some weird spacing on the mobile web site:    Additionally, the main font color has changed from black to yellow:    Can this be fixed please?