Problems with locales

  • Thread starter Thread starter Mark Gillespie
  • Start date Start date
M

Mark Gillespie

Hi, have been running XPe for a year or so now, and have had an
annoying problem , which I think is caused by the system locale and/or
the codepage conversions. I must admit, my knowledge on codepage
conversions is very limited.

The problem is that when I first deploy my image, non unicode programs
have garbled or non-existant text in the dialogs. Also FBA has some
jibberish # characters instead of real text.

Last time I built out SP1 image, I messed around for a while with
regional settings, locales and font substitution, and set everything
back to English UK, then made our image.

I am now upgrading our project to SP2, and hoped the problem would
disappear with the update (!!!), but alas not. I have removed all the
locale stuff from the SLX, and re-added them. No change. I would
really like my Target Designer project to set the correct locale, so we
don't have to mess around between FBA and imaging.

Does anyone have a CMI script that sets the locale and font subsitution
to English UK (or US), or a way to fix these issues.

Thanks.
 
The garbled text during FBA means the default system font is set to some non
english font. You may see this discussed once or thrice in the newsgroup
archives a couple years ago. This system font is defined by a reg key. The
best fix for this would be for us to resolve the conflict in Feature Pack 1
this year so that multple fonts can't try to claim to be the system font and
causing a collision with the reg key. the threads in the NG probably list
the reg key, you can edit this after the runtime is built by loading the
hive, tweaking it and unloading the hive.

Or, delete the colliding key in the offending non english components in
Target Designer.

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
The garbled text during FBA means the default system font is set to some
non
english font. You may see this discussed once or thrice in the newsgroup
archives a couple years ago. This system font is defined by a reg key.
The
best fix for this would be for us to resolve the conflict in Feature
Pack 1
this year so that multple fonts can't try to claim to be the system font
and
causing a collision with the reg key. the threads in the NG probably list
the reg key, you can edit this after the runtime is built by loading the
hive, tweaking it and unloading the hive.

Or, delete the colliding key in the offending non english components in
Target Designer.
Click to expand...



WooHoo, finally got this problem fixed!! I removed all the fonts, then
added "Lots Of Fonts" and "Lots Of Codepages" from
http://blogs.msdn.com/embedded/archive/2005/04.aspx

Everything now seems fine!!!
 
Back
Top