From: Didier B. <d....@fr...> - 2012-05-18 15:57:22
|
-----Original Message----- >From: Marc Prior [mailto:ma...@ma...] >Sent: Friday, May 18, 2012 12:02 PM >To: Mailing list for OmegaT developers. >Subject: Re: [OmTdev] Installer language vs UI language > > then the installer can write that information when it installs the >program > >I imagine that in terms of programming overhead, this is fairly minor. It wasn't that obvious :) >The problem would be more that there is likely to be a wider choice of >installer languages (since the installer text doesn't change much) than >UI languages, leading to conflicts or unexpected behaviour. What I decided is to remove all languages for which we do not have a user interface. I had to create a few user interface strings in the installer, because someone might want not to configure any specific language, but use the language of the computer, as was the default before, so I had to create a wizard page to configure that. I'll include the strings in the localisation packages. Currently, they only work in ANSI, but, time permitting, I'll migrate to the Unicode version of Inno Setup in a few weeks (I don't want to do it in a hurry). The process is a bit clumsy, as I have to add the string manually to the Inno Setup language file, but I don't expect them to change often. As usual, if the text is not translated, it appears in English. Didier |