[DISCONTINUED] Translation Plugin for our themes
I had the same problem. With this version, it has worked for me:
PS: Meanwhile, I no longer use the plugin. The translations are stored in the database, which has very negative effect on the performance of the website. I have now translated my content in the po / mo file as it corresponds to the standard for other WordPress Plugins.
@seetalchile I searched for the plugin and found it at this link, but I sould like to get your confirmation as it is not available in the wordpress.org repository and it seems it gets the patest update on 2008:
Is it right?
Concerning the performance, I already made all translations with IMIC-TRANSLATOR so, is it enough to disabale to avoid losing performances?
@samuele_cervi Yes that’s the correct one.
If you disable the IMIC-Translator Plugin, you’ll see how your web site is loading faster. For me, the difference is about 2 seconds when I use po/mo files for translating. This is not surprising in terms of the many database queries.
The Plugin “CodeStyling Localization” has not be updated a really long time. But that does not matter because it has no direct impact on the functionality of your web site. Only files translation files (po/mo) will be created/updated. Alternatively you can use a local editor such as Pedit.
Unfortunately, there is no reasonable option to migrate the translations form IMIC to po. I have entered all the translations again.
unfortunately the plugin was not working, installed activated but the buttons pression did nothing at all…
I actually switch to Poedit and rebuilding all thanslation again 🙂
Concerning the performances of the website, you are right it is faster.
LucaSignaleParticipantPost count: 23
1) Attempt to download the originally linked plugin (http://cl.ly/3S0R3G3O3w16) generated a chrome browser warning of malicious content. The updated ‘attached’ plugin however downloaded without issue.
2) After install and clicking ‘fetch strings’ the page has a broken image (probably intended as a spinning disc loading graphic).
3) For usability, after clicking ‘fetch strings’, there is a report how many strings are found. It would be logic to have a hyperlink to then edit.
4) If there was an option to categorise the 1971 found strings, this would be useful. For example it is not necessary to translate WP admin strings – rather just public facing strings. With 99 pages of strings, there is a lot to do, but plenty of strings which don’t require a translation.
5) The pagination (99 pages) doesn’t seem to work. If I am on page 6 (of 99) it shows:
<< < 6 > >>
The 6 is a form field and editable, but I can’t click enter or an arrow (>) and go to a page (such as page 25).
Hope the feedback is useful.
You must be logged in to reply to this topic.