As mentioned by John Lamb in his blog over at Modality Systems, we have been looking into automating the localisation of Office Communicator client.
After a bit of thought it seems most obvious to match the language of Office Communicator to the operating system language rather than Office, however before this happened I put together the following code to match the office communicator client to office 2007:
OfficeCode=oShell.RegRead("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Common\LanguageResources\UILanguage")
If Err.Number <> 0 Then
ologging.CreateEntry "zAZCFG-OCSLanguage: Office Language Key not found, defaulting to: en-US", LogTypeInfo
oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator MUI\Default Language", 1033, "REG_DWORD"
iRetVal = Success
Else
If OfficeCode = 1033 Or OfficeCode = 2052 Or OfficeCode = 1043 _
Or OfficeCode = 1036 Or OfficeCode = 1031 Or OfficeCode = 1041 _
Or OfficeCode = 1042 Or OfficeCode = 1046 Or OfficeCode = 3082 _
Or OfficeCode = 1028 Or OfficeCode = 1030 Or OfficeCode = 1035 _
Or OfficeCode = 1040 Or OfficeCode = 1053
ologging.CreateEntry "zAZCFG-OCSLanguage: Writing language code to OCS key: " & OfficeCode, LogTypeInfo
oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator MUI\Default Language", OfficeCode, "REG_DWORD"
iRetVal = Success
Else
ologging.CreateEntry "zAZCFG-OCSLanguage: Office Language Key not supported in OCS MUI, defaulting to: en-US", LogTypeInfo
oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator MUI\Default Language", 1033, "REG_DWORD"
iRetVal = Success
End If
End If
oshell is a windows shell object and ologging is a ZTIUtility file writing parameter.
In the near future I will update with a script to set office communicator to match Vista 
Steven
