Extended characters in a theme file do not display properly in a viewport

[Terry The Great]

Why is it that an extended character appearing in a theme file (WPS, FMS or SBS) and intended by the user to be displayed in a viewport does not display properly even when the proper codepage is invoked?

As an example, when this coding is used (the CFG file states that the primary font is 12-Adobe-Helvetica-Bold):

   %V(1,1,30,12,1)
   %al%s%it

and the extended character is part of an ID3v1 track name and the proper codepage is invoked, this character will display properly.

However, when this coding follows:

   %V(1,14,30,12,1)
   %ac%s½

then the ½ character is not displayed, instead a box outlined in dots appears.

Note: the ½ character was chosen as an example. I may not necessarily want to display that particular extended character. I tried all of the codepage options.

[gevaerts]

Which encoding is the theme file itself saved in?

[bluebrother]

then the ½ character is not displayed, instead a box outlined in dots appears.

Does the font used actually support that character? Try unifont, it has the biggest coverage.

[[Saint]]

Does the font used actually support that character?

It must do. OP mentioned that the glyph is displayed when present in metadata.

I would guess that the encoding of the theme file itself is the issue here.


[Saint]

[bluebrother]

It must do. OP mentioned that the glyph is displayed when present in metadata.

Ah, right. Missed that