Re: [WiX-users] How to localize with Votive
Christopher Karper wrote: > I'm just starting the localization stuff, so I'll take whatever > reccomendation you have. Is the MUI pack stuff supported by WiX in any > way, or do I just need to go google up info on that as a seperate tech? > No special support but it's just another package that installs files into the same directory structure as the language-neutral package. If you have a Fragment with just the Directory elements you need, you can share the authoring so it's not duplicated among all the packages. Note that it does assume your app is smart about having all the language-specific stuff in resources. It can be either in files with the same name (e.g., foo.exe loads resources from foo_loc.dll) or, assuming managed code or manual support, in named resources (e.g., foo_en-us.dll or subdirectories like en-us). -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to localize with Votive
I'm just starting the localization stuff, so I'll take whatever reccomendation you have. Is the MUI pack stuff supported by WiX in any way, or do I just need to go google up info on that as a seperate tech? Chris On Thu, Jan 22, 2009 at 8:55 PM, Bob Arnson wrote: > Christopher Karper wrote: > > I'd like to have Votive build a language neutral (en-US for my company) > > version, then apply translation transformations to it when needed. > > Votive doesn't support transforms. But you'll probably have better luck > with an actual language-neutral base package, if you have any languages > you need to support that don't use code page 1252. > > An alternative, if your app is architected correctly, is to build an > English or language-neutral package then "language pack" or MUI packages > for each additional language's resources. > > -- > sig://boB > http://joyofsetup.com/ > > > > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to localize with Votive
Christopher Karper wrote: > I'd like to have Votive build a language neutral (en-US for my company) > version, then apply translation transformations to it when needed. Votive doesn't support transforms. But you'll probably have better luck with an actual language-neutral base package, if you have any languages you need to support that don't use code page 1252. An alternative, if your app is architected correctly, is to build an English or language-neutral package then "language pack" or MUI packages for each additional language's resources. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to localize with Votive
I've read through the help and my list archive, and I'm a little stuck. It seems to me that there are 2 approaches to building localized installers... 1.) Build an installer for each supported culture-language.. This is what Votive defaults to when you add .wxl files. 2.) Build a language neutral installer, and apply a culture-language specific transform to it. I'd like to have Votive build a language neutral (en-US for my company) version, then apply translation transformations to it when needed. I can't stop it from putting my .msi in the en-US folder, and I would like to have the culture identifier in the filename, but I don't see it as an available variable. Am I missing the right place to look? Can anyone assist or advise, please? Chris -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
