[PD] Changing the defaul language in 0.43

[rene beekman]

Hans, Thanks for your reply and for the time taken to look into this.
For what it's worth, I'm seeing machines that have a locale value of
409, which should be US-English according to this and other tables
http://msdn.microsoft.com/en-us/library/ms903928.aspx, still open Pd
in localized versions.



On Wed, Feb 20, 2013 at 9:35 PM, Hans-Christoph Steiner <hans at at.or.at> wrote:
>
> I'm going to CC the list in case anyone else wants to change this value.
>
> Tcl looks at HKEY_CURRENT_USER\Control Panel\International\locale in particular.  Its a number.  This is not Pd-specific, I imagine its used by lots of apps, and perhaps even the system itself.  I wouldn't recommend changing it directly, it might mess things up.  There should be a way to change the Windows system so that it is set properly in English.
>
> If you really just want to force Pd-extended to be in English, the safest route is to delete all the .msg files in  \Program Files\pd\po
>
> .hc
>
>
> On Feb 20, 2013, at 1:34 AM, rene beekman wrote:
>
>> Hans, I'm replyting off-list so we don't burden the list with this.
>> Attached are screenshots from the registry entries on two of the
>> machines. As you can see from the menus of regedit itself, the OS is
>> running in English, though I am not sure where that is set in the
>> International settings.
>> Some of the other machines (I'm waiting for their owners to mail the
>> screenshots to me) have localeName set to en_US en location to US, but
>> Pd still opens in Bulgarian.
>> I'll send the other screenshots when I get them.
>>
>> Thanks!
>>
>> Rene
>>
>>
>>
>> On Mon, Feb 18, 2013 at 4:53 PM, Hans-Christoph Steiner <hans at at.or.at> wrote:
>>>
>>> Run 'regedit' in the Run command thing on the start menu, and look for:
>>>
>>> HKEY_CURRENT_USER\Control Panel\International
>>>
>>> .hc
>>>
>>> On 02/18/2013 12:57 AM, rene beekman wrote:
>>>> Hans, thanks for the reply
>>>>
>>>> On the Mac it works for me.
>>>> Applelocale reports en_BG and Pd properly shows up in English.
>>>>
>>>> The windows machines I will be able to check tomorrow evening.
>>>> How do I find the proper registry keys there?
>>>>
>>>>
>>>>
>>>>
>>>>> Date: Fri, 15 Feb 2013 09:54:35 -0500
>>>>> From: Hans-Christoph Steiner <hans at at.or.at>
>>>>> Subject: Re: [PD] Changing the defaul language in 0.43
>>>>> To: pd-list at iem.at
>>>>> Message-ID: <511E4C2B.2030908 at at.or.at>
>>>>> Content-Type: text/plain; charset=ISO-8859-1
>>>>>
>>>>>
>>>>> Pd-extended should use the same language that the user is using.  If not, its
>>>>> a bug.  Pd-extended on Mac OS X looks at what language the Dock is configured
>>>>> in and uses that.  Apparently, this is not reliable, since I guess people buy
>>>>> systems in one language, then use them in another, and the Dock doesn't seem
>>>>> to respect that change.  You can check the language of your Dock and your
>>>>> global locale by running this in the Terminal:
>>>>>
>>>>> defaults read com.apple.dock loc
>>>>> defaults read NSGlobalDomain AppleLocale
>>>>>
>>>>> The easiest fix it to probably set the language of the Dock like this:
>>>>>
>>>>> defaults write com.apple.dock loc en_US
>>>>>
>>>>> I have no idea why its failing on Windows, maybe for a similar reason.  As far
>>>>> as I could tell, Pd-extended uses the 'proper' registry value:
>>>>>
>>>>> HKEY_CURRENT_USER\Control Panel\International
>>>>>
>>>>> Could you send the value of that registry key on machines that fail to respect
>>>>> the user setting?
>>>>>
>>>>> .hc
>>>>>
>>>>> On 02/15/2013 01:03 AM, rene beekman wrote:
>>>>>> How do I set / change the default language on both Windoze and Mac for 0.43
>>>>>> ?
>>>>>> I don't have a Windoze machine myself, so can't test there, but the readme
>>>>>> for the Mac version does not say anything about it. There also seems to be
>>>>>> no setting in the preference file for this (or at least none that I could
>>>>>> find).
>>>>>>
>>>>>> I searched the list-archives and the "best" instruction I found was to
>>>>>> delete all .msg files inside /po, which seems a bit crude to me.
>>>>>> Is there a more elegant way to do this?
>>>>>>
>>>>>> I understand from an older discussion that the assumption was that
>>>>>> "non-technical" people were assumed to want to use Pd in their native
>>>>>> language. I did installs this week on about a dozen machines
>>>>>> and apparently they all belonged to "non-technical" people, even though
>>>>>> every single one of them runs all software on their machine in English
>>>>>> only... Wouldn't it be wiser to assume that whatever the language is that
>>>>>> the OS is running in, is also the language that people really want to use
>>>>>> their software in?
>>>>>> Just my two cents.
>>>>>>
>>>>>>
>>>>>>
>> <a.png><b.png><registry editor.jpg><registry editor2.jpg>
>