This new version has two major changes and lots of bug fixes included.
The most important change is the integration of the plugin with the WordPress GetText system, which is the way WordPress (and some themes and plugins) provide localized versions of themselves. This is done with a couple of files (called .po/.mo files because of their extensions) that includes a list of translated strings that that software include.
What Transposh now does is to utilize said files, so if you have the files that translate WordPress to Spanish, they will take precedence and Transposh will use the files to make the translation of the interface to Spanish. Why is this better? there are a few reasons, one is that sometimes it enables translations where they were previously impossible, another is that the translation is human based and deemed more accurate, and the last is that it can clear ambiguity especially in short strings such as month names and day abbreviations.
How to get the .po/.mo files, and more information about how this work can be found at http://trac.transposh.org/wiki/UsingGetText.
This feature also includes a rewrite of the in-memory caching system of the plugin, which now supports xcache and eaccelarator in addition to the previous versions APC support. This version uses a more compact representation of the data which improves performance and reduce memory usage.
More fixes in this version:
- Tags from the tag cloud will now be translated with mass translate
- Fix for the sneaky “not a valid plugin header” issue, if you get “Default” listed twice in your widget selection settings, please delete the widgets/tpw_deafult.php file
- Fix for MS translate tendency to add an extra space to translation result
- Fixed bug with list with flags css widget preventing the view of flags
We have also changed this site layout a bit so you can see the development feed and changes in a more real time fashion.
Waiting for your feedbacks on this version.
Update: A bug was discovered when using the plugin without caching, if you have repeat translations, or you can’t see translations previously made, please reinstall the plugin from wordpress.org, the plugin there is now fixed. Thanks Nicholas for reporting this.
Hi,
I have a new bug with the new release (0.6.3) and the plugin Mailpress. When we want to display one of the translations of the page, there is an error :
Warning: DOMDocument::loadXML() [domdocument.loadxml]: Unregistered error message in Entity, line: 4 in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 7
Warning: DOMDocument::loadXML() [domdocument.loadxml]: PCDATA invalid Char value 1 in Entity, line: 4 in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 7
Warning: DOMDocument::loadXML() [domdocument.loadxml]: PCDATA invalid Char value 3 in Entity, line: 4 in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 7
Warning: DOMDocument::loadXML() [domdocument.loadxml]: Sequence ‘]]>’ not allowed in content in Entity, line: 4 in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 7
Warning: DOMDocument::loadXML() [domdocument.loadxml]: internal errorExtra content at the end of the document in Entity, line: 4 in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 7
Fatal error: Call to a member function hasAttributes() on a non-object in /wp-content/plugins/mailpress/mp-includes/class/MP_Xml.class.php on line 50
I installed that plugin and could not see the conflict, I guess I am missing something somewhere.
The conflict is caused by the way Transposh uses to integrate into gettext (by adding those chars and later removing them) normally the conflict you are describing should not happen.
You may add an option “disable gettext integration” …
Yes, guess I’ll add it to the next version
I love what i see and read here, just not technically able to implement. Getting ready to have my coffee site updated to latest WP and this plug-in for translation is a must for me. When translated, will it update and populate the page as though it were a unique page? If I had 20 pages in english and translated into Japanese, would i be able to use the translated page to create an actual page and save it as now a live page and enable full meta optimization?
I need a website done and I want to incorporate this functionality, anybody avialable to quote this?
Hello Edward,
The translated page is an actual page for any practical purpose, I don’t know what you mean exactly by full meta optimization but I surely hope it works
Hi,
(sorry for my english)
For my polish web i set Polish language to default. When changing lang to other, i get translated to this lang title widget “Translation” and options “Set as default language” and “Edit Translation”
eg. for German > translation, As a standard language
Edit translation.
But when i change to Polish (my default lang) this text is in english, not polish. 🙁
Why missing widget translation for defalut lang if default is other than english?
This will be fixed in the coming version (0.6.4) soon
Hello, I have a problem with Norwegian nb_NO. The activity in buddypress gets translated only for the first activity, all the other activity stays in english…Any ideas?
I also get a blank page for some of the languages…I can give you access to my private community if you want to check out why?
Actually it’s the language that don’t have any .mo files. I get a blank page…
Hello, in the virtual host configuration, my web administrator increased the php_admin_value memory_limit to 128 and now it works… So you were right, it was a memory problem! Thx for your help!
Glad I was able to help
Yes, thx again!
I still get a problem though, when I have the buddypress language files…In Norwegian for example, only the first activity is translated, the rest is not…any ideas?