Bugzilla – Bug 5183
Norwegian localisation issues
Last modified: 2008-12-18 10:24:56 UTC
A Norwegian customer wrote me today stating that the translation is not 'up to par' and should be overlooked. Below I have pasted the email that the customer sent. It's a good thing that there is a Norwegian version available, but there are so many silly errors in it. The translation is not good, and the Norwegian version should have been proof read. Any comments? Regards Jan (who is not fluent in English, but who prefers English language over not good Norwegian)
Would this customer be willing to make a list of the problem strings?
As long as Norwegian isn't an officially translated language there isn't much we can do. We rely on volunteers in this case (as with most other languages, too). Only a hand full is officially translated by pros (DE, FR, IT, ES, HE, NL - for a hand with six fingers, see http://www.herger.net/photo/india/slide.cgi?&no=4 ;-)). If he's willing to send some improved translations, I'll be happy to integrate them.
There are many mistakes, especially long words split into several parts (considered really serious errors in Norwegian), examples: Musikk biblioteket (correct: Musikkbiblioteket), Musikk folder (musikkfolder), Server innstillinger (Serverinnstillinger), Spiller innstillinger (Spillerinnstillinger). In addition spelling errors like "komonist" (correct: componist), Komme igang (Komme i gang), comma errors, grammar errors etc. I might make a longer list later if I find the time. Regards Jan
Jan - thanks for the feedback. But as I mentioned earlier - there's not much we can do. Today's translation is the work of volunteers. I don't know whether there are plans to have an official translation done by professionals. If you would like to help us improve it, this would greatly be appreciated. Feel free to use my StringEditor plugin (http://www.herger.net/StringEditor) or any decent text editor to add/fix the translation. I'll take care of the integration in the nightly builds. Thanks!
I'll cc Mickey and Jim to see if they have input about the Norwegian language support.
I might have time to do some work with the Norwegian translations. Should this work be done in the 6.5 branch or in trunk?
Steinar - thanks for your offer, it's greatly appreciated. Please go for the trunk. I'll be able to merge most of it rather easily with 6.5, but you won't translate strings which will are removed in the trunk and won't miss the new parts. Please don't edit the strings.txt file itself, but create a custom-strings.txt instead. Feel free to contact me if you have any question regarding the localization. Thanks!
Oh, one more thing: I just noticed that there's already been a rather large update of the Norwegian translation only a few weeks back. But I didn't merge it with 6.5... (https://bugs-archive.lyrion.org/show_bug.cgi?id=5122). Therefore you really better start off with the trunk version - many pieces probably are already much improved in there.
Steinar - any news?
I am bad at keeping promises... I'll try to do some work on this, what is currently the best tools to this?
http://www.herger.net/StringEditor - give it a try :-)
Created attachment 2635 [details] Sample update of Norwegian translation Before I use more time on this, is a file in the format of the attachment OK?
Perfect!
If we get an updated translation this week, we'll put it in for 7.0. Please attach and then assign to Michael for integration. Thanks, Steinar!
Steinar/Michael: Are we done with this for 7.0?
I am really sorry, but I need some more time on this. I underestimated the amount of work to get this done properly.
I guess that work will be done when it's done. Can't target community contributions.
Ahm... now that we have official NO translation I consider this done. Feel free to open new bugs for particular issues. Thanks.
This bug has been fixed in the latest release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.