Re: Windows Installer L10n - request for developer assistance

> These PO files are currently encoded in UTF-8 and as Urmas observed of
> the NSH files, "Apparently they can be either in usual Windows
> encoding (CP125x) or UTF-16 (LE)."
>
> I would like to collaborate with a developer on improving (or adding
> to) the existing .nsh files in the mvsc branch so that the Windows
> installation process has improved L10n.
>
> A hacker-ish manual convert-encoding, copy, paste into the English.nsh
> as a template seems like an adequate approach to what is hopefully a
> one-time fix. I would not object to collaborating on modifying the PO
> file to be more suitable for an automated approach, but I think that
> is not necessarily the quickest solution (i.e. in time for a
> hypothetical 2.9.4 release), although it would probably be more
> sustainable over the very long run. I'd be more than satisfied just
> to get the currently completed PO files manually converted to improved
> NSH files and to document the necessary steps for future use.
>
> Is there anyone even vaguely familiar with the Windows install process
> that would be willing to work with me on this interim step of manually
> creating new NSH files (Prashant, Simon, Ingo, Marc)?

Hi Chris,

I haven't much worked with either the NSH files or the Encodings till
now, but I'll certainly like to help with this in whatever way I can.
Let me know how you want to proceed.

Thanks,
Prashant
Received on Mon Jul 9 08:52:06 2012