11

I've just noticed viewing a Python answer (since modified: see revision 2) on Stack Overflow that the Android app shows new (incorrectly) highlighted as a keyword which differs from the normal render from the web page.

Example

While it should look more similar to:

enter image description here

Notice no highlighting for new.

| improve this question | |
  • 1
    The app also highlights all the special characters :=[](). etc, whereas the main site doesn't. I wonder if they use a completely different highlighter for the app. – animuson♦ Dec 3 '14 at 19:00
  • @animuson and different colouring for literals etc... however, I was trying to not make it a stylistic question, more a "the language highlighter is not recognising the correct keywords for a language" kind of thing – Jon Clements Dec 3 '14 at 19:03
  • @nicael oops - thanks for edit :) – Jon Clements Dec 3 '14 at 21:03
  • Despite the age of this question, this still seems to be an "issue" (whether a bug or feature is up to you). I've just created an answer which isn't prettified by either FF43 or Chrome47 at all. The Android app performs rather nicely, though. – morido Jan 12 '16 at 12:24
  • @morido in your case, the issue was caused by "no suitable language detected based on the tag" (previously only opencsv). I have fixed it by adding java on the question, and your answer now has syntax highlighting. However, I acknowledged the issue. – Meta Andrew T. Jan 21 '16 at 9:29
  • @AndrewT. Cool, thanks. So there is generally a need to attribute a language tag to a specific question even if other tags (such as "opencsv* which happens to be a Java-only library) already unambiguously identify the language? – morido Jan 21 '16 at 9:35
  • @morido yes, it has to be specified on the tag. As an example, opencsv doesn't have code language, whereas Android has default code language (it's on the very bottom) – Meta Andrew T. Jan 21 '16 at 9:43
  • Related: Should the Android app be adding syntax highlighting for code blocks without code tags? – Meta Andrew T. Jan 26 '16 at 9:49
2

This will be fixed in 1.0.84.

I'm not sure where that color scheme came from but it's been lingering around for almost three years. Updating to match the iOS app and web.

| improve this answer | |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .