Am I first non-German speaking Musik Server user? ;)

[TomekWaw]

Hello,
I've successfully installed MusicServer4Lox and started testing it. Thanks for all the work done with that project.
Unfortunately, I don't see or can't find an option to change language German language to English
I've found LANG="de" in /opt/music_server/sq_cfg/sq_lang.cfg, but changing it to LANG="en" doesn't seem to work.
I see German phases are hard coded into html code of web interface but I don't prejudge as percheps it's used as localization keyphrases.
English language as an option would make MS4Lox MUCH easier to use for non-German speaking.

[hismastersvoice]

No, you are not the first non-German user, there are may others with the same (google translate) problem

The sq_lang.cfg you have found is a setting for the 1.0 Version of the MS4L and is not implemented now.

Why only German...
I have started the project for a good friend of mine to give him as an non-technical-person the opportunity to setup a Multiroom system.
At that time I had never the idea to implement so much feature like we have today. Me and my friend are German speaker, so at the beginning I don`t ever thought about to implement language support.

I do the hole project by myself (one man show), and is was a lot of work to bring the system to the state of today.

In the last 1 1/2 years I had a lot to do in my company and was travelling the most of the time. So I was not able to Release the 1.0 of the MS4L. My plan is to write the new version in the winter-days 2019->2020. The base of Version 1.0 is 100% different from the beginning, so the most of the code has to be rewriten.

We will see...

A little preview...

[TomekWaw]

hismastersvoice, Thanks for your answer.
I suspected it's like this, just needed to be sure there is no English translation.
I'm using Google translator plugin in my Chrome browser extensively, so somehow I will manage this (the same way I deal with most of that forum, by the way
There are no so many settings in the web interface, after all.
It's great you plan working on new version. It would be great if you might consider using some simple localization framework for future version, or even using English as a base language. After all it's used in all command parameters / url parameters, even in current version (thankfully!)



PS.
In current version I've found one area that needs a different solution for non-Germans for sure
When I executed CTS event, polly's Jacek read "Es ist jetzt ............. Minuten" in Polish haha!
Surrounding text of cts its not templated as in w2t or tt2t.
Btw, tt2t is templated, but value of {duration} includes text "Minuten" in German.

[TomekWaw]

hismastersvoice I've found those "Minuten" in /var/www/event/event_functions.php Not a long file, but any of my changes would be probably wiped out during update (woudn't they?) At first I thought that if you'd took with the next update all strings from this file to separate external files (like: event_function_strings_de.php, event_function_strings_en.php, event_function_strings_pl.php), it would be easy to translate to English and Polish.
But I see now it's not so straightforward. In German you have Eine Minute, all else is X Minuten. In Polish - its more complicated... (1 minuta, 2,3,4 minuty, 5-21 minut, 22-24 minuty, 25-31 minut, etc I'm sure there is an open source library for that kind of issues though

[hismastersvoice]

I don't take care about your changes..
As written in the final version you get language support not before.

I you can't life with that, you have to use a different solution like buying a Loxone MusicServer.

Also I hate if people plays around with my code. That could have the effect that maybe another function run into problems if you don't know the interrelation of all.

My support ends here.

[TomekWaw]

hismastersvoice ,

I'm surprised you have reacted this way. Please note I didn't ask for support in this thread. I didn't require any support with MS4Lox so far, as help pages are good enough and I have read them thoroughly twice before I even started.

But since I became a user of MS4Lox I thought I'd contribute some feedback, which might be valuable both for author(s) and users, especially non-German speaking. Isn't that what this part of loxforum is for? User feedback and error reports are essential parts of any software development flow, after all. Not much feedback from non-German speaking users here though. Perhaps that's why some great parts of MS4Lox like CTS, Weather2TTS and TravelTime2TTS turn out to be unusable with any other language param then "de-de". And it wasn't mentioned in documentation (or forum until now).

Then, when you told that "you do the whole project by myself" I thought you would make use of some help. I was planning to offer you help with translations (I would be happy to contribute Polish translation, but might also help with English). But since you clearly prefer to do all by yourself, I'll eventually just translate it for my needs and workaround the update process. I will not come here and beg for your support if I would by any change brake something, don't worry

And finally, if you hate when people poke around your php code, why do you share it plain in the first place?
You'd might feel much better if you encoded it with ionCube or any other similar technics.

[Christian Fenzl]

LoxBerry has no Polish yet. We would welcome a new language 🙂

https://www.loxwiki.eu/display/LOXBERRY/Translation+Guide+for+LoxBerry

[hismastersvoice]

But since I became a user of MS4Lox I thought I'd contribute some feedback,

I like feedback, but the input is for multi-lag support that is not included yet.
I already have solved this, and in TTS/WTS/CTS ... it will be included in the lang-file. If you lang "de" you geht "eine Minute" or "Minuten" if you use "en" you get " one minute" or "minutes".
W2T or TT2T Wind/Rain/Time is hard-coded in German, but can change to get the vars out of the lang-file.

So I welcome offer to help and `ll come back to you when I`m ready with the support of languages.

I'll eventually just translate it for my needs and workaround the update process. I will not come here and beg for your support if I would by any change brake something, don't worry

Thanks, others do so.