Re: How do you avoid extra languages?
- From: "KM" <konstmor@xxxxxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2007 13:02:23 -0700
BlueMonkey,
I never thought of the best practice for only supporting English locale but here is what I typically do when I want to minimize my
English-only image footprint:
- Disable he MUI for *all* components included in my Config. I usually do that with a custom CMI script so that I don't have to
manually go through all the components. The script is actually available with XPeTools and SmartUpgrade components of XPeTools
package on www.xpefiles.com.
- Disable "support all system locales for English" on the English Language Support component's setting page.
- Make sure I don't include other language components explicitly via Component Browser or via checkbox option on some macro
component page (e.g., Quick Start macro, etc.)
- Disable TD auto-dependency resolver and watch for any component that may want to bring other language components in during
Dependency Check phase.
--
=========
Regards,
KM
I would like to know the most efficient way to avoid extra languages and
input being dragged into my images.
Example: If I'm building a kiosk that has a GUI SHell that only has
symbols/pictures rather than words, obviously I wouldn't want to bloat the
system by having support for all the languages XP supports.
I vaguely remember to set the system region and local before doing a
dependancy check.. Some how the other languages creep in to the build.
So, what is the offical best practice way of only supporting English only?
.
- Prev by Date: Re: Tray Icons and custom shell
- Next by Date: Re: MSDN EWFAPI Sample Logic Error.
- Previous by thread: Re: Tray Icons and custom shell
- Next by thread: using minlogon
- Index(es):
Relevant Pages
|
Loading
