home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
General Forums
Website/Forum/Wiki Feedback
Improvement for Download Section
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Dadeo" data-source="post: 632112" data-attributes="member: 27204"><p>Hi kesar - about the translations - it's a bit off topic for downloads - website feedback, but there really is no place to talk about Translation other than in the Development forum > Localization. There is some good info there as you likely know! </p><p></p><p>I am sure you can understand it is impractical to support all plugin translations in the MP string files. If we did that, then plugin updates would be inaccurate until MP was updated. The good news is that I find more and more plugins are paying more attention to translations, both by providing string files with the plugin and by providing translatable properties to use in the skin files. The one area that is problematic still is Basic Home for the plugin name since it does not use the plugin string files, nor any property defined in the plugin for the plugin name (that only works in MyHome/Plugins). Once our feature freeze is lifted, after MP 1.1.0 I plan to ask for a solution to this. Any suggestions?</p></blockquote><p></p>
[QUOTE="Dadeo, post: 632112, member: 27204"] Hi kesar - about the translations - it's a bit off topic for downloads - website feedback, but there really is no place to talk about Translation other than in the Development forum > Localization. There is some good info there as you likely know! I am sure you can understand it is impractical to support all plugin translations in the MP string files. If we did that, then plugin updates would be inaccurate until MP was updated. The good news is that I find more and more plugins are paying more attention to translations, both by providing string files with the plugin and by providing translatable properties to use in the skin files. The one area that is problematic still is Basic Home for the plugin name since it does not use the plugin string files, nor any property defined in the plugin for the plugin name (that only works in MyHome/Plugins). Once our feature freeze is lifted, after MP 1.1.0 I plan to ask for a solution to this. Any suggestions? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
Website/Forum/Wiki Feedback
Improvement for Download Section
Contact us
RSS
Top
Bottom