unfortunately with Segoe UI I was not able to reproduce the behavior. In turn, when using Arial font, I can observe the effect of two 1 digits being displayed closed together. I was able to verify that in this case the Arial font contains an entry in the kerning table to correct the arrangment of two following 1 glyphs in order to get better looking outputs. In case of Segoe UI, there is no kerning table entry for this glyph combination. So far this confirms my observation. I suppose your version of Segoe UI differs from the used on my machine. Or the resulting kerning data does depend on the specified font size. What size have you configured for the Segoe UI font?
Concerning your other observation. The kerning metrics also affect left aligned text. If you display the string 100 and 110 the last 0 digit jitters slightly. From my point of view, this is the correct behavior since the font data contains corresponding instructions to bring two 1 digits closer. Do you agree?
Anyway, what can you do?
Option 1: Since Embedded Wizard actually does not allow to disable the kerning tables, the simplest option would be to try another font.
Option 2: Trick out the font converter so the kerning data is not taken in account. In Embedded Wizard it is possible to map the involved glyphs to other codes. You configure this in the attribute Ranges. Concrete, instruct Embedded Wizard to import the glyphs '0'-'9' and store them at other code points. For example at the code points 0x1030 .. 0x1039. Following is the setting of the Ranges attribute:
Consequently, to display the digit 1 with such font you have use the code point "\x1031". The string "\x1031\x1031\x1030", in turn, displays the digits 110. Because of the mapping, the kering data for the glyphs is not available anymore. Tne jitter disappears. The problem, which remains is how to convert a regular string containing e.g. the digit "110" in a string containing the mapped code-points?
For this purpose I would iterate over the original string and add 0x1000 to each found glyph in range 0x0030 .. 0x0039 (0-9). To test this approach I have implemented following ConvertDigits() method:
var string str = aString;
var int32 len = str.length;
var int32 inx;
for ( inx = 0; inx < len; inx = inx + 1 )
if (( str[inx] >= '0' ) && ( str[inx] <= '9' ))
str[inx] = (char)((int32)str[inx] + 0x1000 );
Now wherever I assign a string containing digits and I use the special font, I invoke the method. For example, to format and display a number:
var int32 someNumber = ...
// Let the text view display the number
TextView.String = ConvertDigits( string( someNumber ));
I hope the workaround helps you further. Anyway, in the next version we will add a option to disable kerning tables.