Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Finnish translation/Mango puhuu suomea
-
means mango speaking finnish.
I know there are some finns using Mango. I made the translation for finnish language. There may be typos and incorrect translations. Here is something to start with. Please post your comments.
Some datasources and emport message translations are missing as the messages are quite specific. It needs some testing to make correct translations. And the help files are not translated.
Attached the files, just extract the zip to /WEB-INF/classes and restart tomcat to take into use.
Same in finnish as it is relevant in this case
Kun tiedän että on muitakin meikäläisiä Mango-käyttäjiä, niin tein käännökset suomeksi. Siinä voi olla kirjoitus- ja käännösvirheitä, mutta jotain mistä lähteä. Kommentoikaa vapaasti.
Puuttuvia käännöksiä on, jotkin datasourcet ja emport viestit, kun muotoilu on aika tarkkaa, jottei asia häviä käännökseen. Pitäisi testata tarkemmin, jotta voi tehdä oikeat käännökset. Helppien käännökset puuttuvat myös.
Tiedostot liitteenä. Pura zip kansioon /WEB-INF/classes käynnistä tomcat uudestaan niin siinäpä se.
BR
-JokkeAttachment: download link
-
Hi Jokke,
This can be added to the Mango distribution if it is reasonably complete. Let me know.
-
Hi Matthew,
Yes why not, I will let you know. It is already quite complete. In normal usage, you wont run into untranslated parts(except the some data sources, helps and some error messages). I hope after some fine tuning it could be included. I have fixed some typos already. I hope getting some comments on the terms/equivalents I have used in the translation.
The engineering units is something I am not sure what to do with. Usually the SI abbreviations are used, so translation might not make sense. But maybe I just did not catch the idea of this property. Could it be used on some unit conversion?
Not all (error)messages can be translated as they are printed from other components, I assume. There was some minor findings where there was not used localization in message. Like the "(unknown)" in mysql size and this event message "Maximum alarm level has increased from common.alarmLevel.none to common.alarmLevel.info". These maybe some glitch on the localization?
You have done the localization quite nicely. Only minor issues found and they could have pretty workarounds. in such case when a word translation depends on context(like in many languages things do). I could think it could have lots of issues, if the structures are too much based on some language. There is lots of redundant looking definitions in message files, which looks unnecessary, but they are usable.
For example "period of 2 months" mango shows "period = 2 month(s)". And in an other place it is using the same stings when context is "backwards for 2 months" is shown as "backwards = 2 month(s)" This is quite clear in English, but in Finnish the word "month" (and the multiply) is different in depending when talking about "of" or "for" :D We don't have the words like of, to, for, from, in, on, at, .... all are mostly kind of extensions to the subject word.
BR
-Jokke -
Hi Jokke,
Ok, send over the file when you feel it is ready, as well as the i18n.properties with the language name.
You are correct about the mysql size value and the alarm level change message. These have been fixed.
Regarding the translations being "too English", this of course is entirely possible. In many areas there was an effort to use parameterization to prevent there from being a huge number of messages. I can understand how this may make for translation problems itself. If you have suggestions for how to address this, please send along.
-
Hello Matthew,
Here is the "final" translation. Now the missing translations are limited on help files and some datasources. Typos corrected and minor changes on the used translations.
There was some minor findings nothing major
- This was seen "Modbus pointo locator test: "Illegal data address: {1}""
- This was not localized so it is same on all language settings. "SomeCompoundEventDetectorName: java.lang.Exception: Detector S3 not enabled or does not exist"
- On audit events the publisher deletion/change does not make any event.(like all other user actions) I am not needing it, but just noticed while testing.
- The common.true and common.false is used on logical true/false and in the audit events. It has a slight difference on translation if the context talking about something is on/off or binary/logical value true/false.
- This was a tricky one to translate properly making correct sentence. (because of the missing words in finnish :) ) But I think I got it worked around. "User "admin (1)" deleted Data point with id 307:
Export ID (XID)="DP_713928"
Name="yeaa"
Enabled="True"
Logging type="When point value changes"
Interval logging period="15 minutes(s)"
Value type="Instant"
Tolerance="0.0"
Purge="1 year(s)""
Attachment: download link
-
Wonderful. Thanks Jokke. Can you also provide the name for Finnish in Finnish for the i18n.properties file? I.e. "fi=suomea" (a complete guess).
Also, how would you like to be credited for the work?
-
Maybe promotion to Padawan 1st class :D
BR
-Jokke -
Alas, the rankings are based upon the number of messages you post, not your karma.
I didn't look closely enough. I thought you had just posted the translation file. I think i have everything now.
-
Hi Jokke,
Regarding the findings you had mentioned earlier...
This was seen "Modbus pointo locator test: "Illegal data address: {1}""
This has been found and fixed. The {1} part was removed.
This was not localized so it is same on all language settings. "SomeCompoundEventDetectorName: java.lang.Exception: Detector S3 not enabled or does not exist"
This was fixed too.
On audit events the publisher deletion/change does not make any event.
The commission to do the audit work did not extend to publishers.
The common.true and common.false is used on logical true/false and in the audit events. It has a slight difference on translation if the context talking about something is on/off or binary/logical value true/false.
It's not exactly correct to use true/false in those contexts in English either, but it's common to do so.