The language Id is simply a parameter in the query string when entering the
room. You don't need to set the language parameter in any of the rest calls.

$url =
$this->url_server."/openmeetings/hash?secure=".$hash."&language=".$language;

While $hash is the hash you created via rest calls.
And $language is simply the id of the language, starting with 1 (for
english) and 37 for your new custom language.

Thanks
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Fri, 25 Dec 2020 at 09:37, Robert Savickas <[email protected]> wrote:

> Dear Daniel,
>
> Actually, my language (Lithuanian) was not included in the distribution;
> so, about 6 weeks ago, I undertook the task of translating the entire OM
> interface and created the language file to use in OM and added this file to
> the directory that contains all other languages.  It works very well and
> the entire OM on that server of mine is in Lithuanian.
>
> I will be glad to share that file with the production team for the future
> inclusion in the OM distribution, if desired.
>
> So, the direct OM interface uses Lithuanian language, because I can
> specify the language in each user's profile. No problem.
>
> But when I connect users to my OM via the REST API, i do not know what
> keword to use to specify the language. In my installation of OM, Lithuanian
> is language 37. So, I tried to include the following in the REST call to
> connect the user: languageID = 37 and language_id = 37.  But neither one
> yielded any result: the OM conference room that comes up is still in
> English...
>
> Thank you for any hints that you could share!
>
> Robert
>
>
> On Thu, Dec 24, 2020, 15:11 Daniel Baker <[email protected]>
> wrote:
>
>> The  full list  of  languages  is  here :
>>
>>
>> https://github.com/apache/openmeetings/blob/ad9013588d43996282ee568a89a46a689d8916d9/openmeetings-web/src/main/webapp/languages/languages.xml#L21
>>
>>
>> On 24-Dec-20 8:02 PM, Robert Savickas wrote:
>>
>> Dear Maxim and friends,
>>
>> Please forgive me for sending this question the second time, but I
>> reckoned it to be more appropriate to send it under a different subject
>> line, rather than continuing the previous thread.
>>
>> This is just to update you: your REST integration is a beautiful thing.
>>  I was able to make OM work perfectly within my platform, for a
>> seamless user experience. Super! Thank you very much.
>>
>> Just one question: Even though I did set up the local language interface
>> for the users, and it works when they login directly into OM, the language
>> is English when users connect via REST.  I tried to specify the
>> languageID : keyword in the REST call to connect, but it still connects in
>> English interface.
>>
>> Is there a way to specify user language in Rest?
>>
>> Thank you.
>> Robert.
>>
>>

Reply via email to