Seeing strange fonts on your Xbox One? Here's why.

Microsoft has recently begun ramping up development on the upcoming fall update for Xbox One, which is set to deliver a wave of new features across the console. Among these changes is a reworked user interface influenced heavily by the company's "Fluent Design System," delivering a system-wide overhaul aiming to deliver new texture and depth the experience as a whole.

As the update approaches its final release, a select subset of users can now get hands-on with an in-progress version of the operating system, via the Xbox Insider Program. However, as new features begin to appear, you may have noticed some strange fonts throughout the Xbox One dashboard. And as ugly as they may seem, these play a role in development across the Xbox OS.

What causes strange fonts in Xbox Preview builds?

In Xbox Preview builds, Microsoft adopts a technique known as "pseudo-localization," to test foreign characters and how they interact with the user interface. By exchanging various characters and symbols for similar counterparts, this allows developers to test how different types of text are displayed and prepare for localization, without going to the effort of translating into multiple languages. Essentially, this is a fake form of translation used in the development process, before actual translations begin.

How pseudo-localization works is relatively straightforward and achieved by finding characters from foreign languages and exchanging them with similar characters in English text. Although its implementation can vary, Microsoft uses a pseudo-localization language that's relatively easy to read at a glance.

Why use pseudo-localization in Xbox Preview builds?

Although a universal font is used across a majority of the Xbox One OS, due to the nature of different alphabets, variations in text can be expected with different languages. Whereas a new section of the dashboard may look great with a traditional English alphabet, when switching to a language with vastly different characters, the flow of a design can change.

If switching to different alphabets, text can expand and contract, depending on the type and number of characters used. And with the addition of Arabic and Hebrew in the fall update (the first right-to-left languages for the OS) text direction is another factor to consider. All of these can result in drastic changes in vertical and horizontal positioning, which can lead to truncated text and other visual errors to hinder the user experience.

Here's an example of strings produced through pseudo-localization, similar to those seen as a part of in-progress versions of the Xbox One OS. As shown, text can vary between the two display types, with several different traits to consider.

This is how text may look in an Xbox Preview build, following pseudo-localizationTћïƨ ïƨ ћôω ƭèжƭ ₥ᥠlôôƙ ïñ áñ Xβôж ÞřèƲïèω βúïℓδ, ƒôℓℓôωïñϱ ƥƨèúδô-ℓôçáℓïƺáƭïôñ

By emulating these changes through pseudo-localization, formatting errors can be quickly spotted and corrected. This helps to find and solve glaring issues earlier in development and prevents potential delays when the true translation process is underway. Furthermore, this can all be tested by an English speaker.

Pseudo-localization also ensures unwanted English text isn't hard-coded into the source code, to prevent strings from not altering between language switches. This makes it clear that English resources are being loaded due to your language preferences, rather being a fixed aspect of the OS.

When an Xbox update finally rolls out to the public traces of pseudo-localization are removed from the OS. However, as an Xbox Insider, these are one of the several byproducts of development you'll see in preview builds. With the need to test localization, this is something that can't be disabled but provides a peek behind the curtain at Xbox development.

For more information on the upcoming Xbox One fall update, make sure to take a look at our complete breakdown of changes so far.

Matt Brown is Windows Central's Senior Editor, Xbox & PC, at Future. Following over seven years of professional consumer technology and gaming coverage, he’s focused on the world of Microsoft's gaming efforts. You can follow him on Twitter @mattjbrown.

  • Noticed this on the Xbox app W10, since it was first released. Glad to know the answer finally.
  • I've seen it even on my W10 phone I believe, they should have been more clear as to why this was. I reported it as a bug so many times..
  • It's been common practice for a few years, if you are using insisider builds you should know to expect this or do a bit of research to figure out what it was.
  • This was not common knowledge at least back then, and it was discussed all over insider forums. Research doesn't help when NOBODY KNOWS.
  • Another reason for this is to make sure no English text is hard-coded in source code.
    By making all strings used in binaries (code and embedded resources) pseudo-English, it makes sure the localized version is loaded from a language-specific resource file, even when tested in English. This prevents cases where the language-specific resources file exists and contains the localized text, but the program does not load it and rely on some internal non-localized resource instead.
    So, while testing, at some point these need to start being reported as they might expose a resources handling bug. Microsoft should specify in the release notes if such strings are expected, or should get reported.
  • Yes, this is the real reason for pseudo localization.
  • Ah, thanks for clarifying! Made sure to clear this up a little in the main text. Appreciate it!
  • Important to note as well that just pseudo-English doesn't help much with text expanding and contracting. As the text still contains the same number of characters and their glyphs widths might be a bit different but not by much.
    Typically this can only be tested by translating to some other languages. If I remember correctly, Microsoft primarily uses german to test longer sentences as it is more verbose than English to express the same thing, and Japanese for condensed sentences but taller characters (technically, CJK character's baseline, ascent and descent are different from latin characters).
  • This makes more sense now, I just always thought it was the font cache catching up with itself sort of oh a website stores data to make things load faster I know its not the same but thats how i saw it in my head. Thanks for clearing it up.
  • Regardless of the weird fonts, XBox have a beautiful fluid UI. Hope the desktop UI gonna be like that soon or not to soon...idk...☺
  • Agreed. The new Xbox UI is the nicest one MS is currently offering on any device. I hope to eventually see that level of polish on desktop. My guess is we'll start to see a lot more of Fluent Design being implemented by the time RS4 rolls around.
  • Good to know, I keep to trying to take screenshots and report bugs of every weird font.
    I shall stop!! Thanks
  • Really... You lot will believe anything!!! It used to be called a bug.... Must be the same 'localization' that showed up on Windows 10 Mobile ONLY on the Windows Update screen. This took MS nearly 5 builds before it was 'fixed'... This thread did make me chuckle though. Almost as much as a 'Warditorial'.....