Hi Monty (and Kim and whoever else is interested :)),
You should probably localize the load theme
descriptions as well.
BTW, I've made some changes to the search.nsi
installer to detect which theme is currently active
and copy the appropriate theme_*.css file to
theme.css. I've attached the search.nsi file here as
search.nsi.txt so be sure to rename it and you'll have
to build the installer with nsis.
Would you be willing to be a guinea pig and try it?
I've not got XP available to me until late tonight to
test it myself.
Brent
--- Monty Scroggins <[EMAIL PROTECTED]> wrote:
> (this copy actually includes the attachment!) :-)
>
>
> Hi Kim,
>
> Attached is the configure.xml(.txt) with the
> localization changes made
> to it. It seems to work fine..
>
> I put the variables in the file, and referenced them
> in the menu defs..
> Is there another change that needs to be made
> elsewhere? I dont know
> how the translation is done.
>
> Monty
>
>
> Kim Gr�sman wrote:
>
> > Hi Monty,
> >
> > Just one thing: Make sure you use a localizable
> constant for the menu
> > options - that's what the weird arrays are for.
> With that in place,
> > people can translate the menu from strings.js.
> >
> > Thanks,
> > Kim
> >
>
> > <search function="configureDQSD">
> <name>Configure DQSD</name>
> <description>
> Configure DQSD<br/>
> </description>
> <link></link>
> <category nomenu="true">Configure</category>
> <contributor>Brent Beardsley</contributor>
>
> <script><