If the output from the EDD things (which I really don’t know anything about) is located in a place where it’s filtered by qtranslate/mqtranslate during output, then you could do it the semi-manual way.
An example:
On one site, I’ve entered the site title as:
[:en]English blog name[:ru]Russian blog name[:es]Spanish blog name
In a text widget, I’ve entered the widget name as “[:en]Photos[:ru]Фото[:es]Fotos“
In these cases, I’ve used the short tags.
You may use the long tags, too.
In a text widget, there are links and images that should always be there, and I just enter them as usual. If there’s anything that should be visible only for a certain language, then I frame it with qtranslate special tags (the same tags that are actually used by qtranslate in every saved blog post).
<!--:en-->Click here for more!<!--:--><!--:ru-->Есть много, кликните здесь<!--:--><!--:es-->Hay más. Haz clic aquí.<!--:-->
Thanks for the reply.
This is not the point, because EDD (https://easydigitaldownloads.com/) it’s a plugin and has its own translation files, so it should be translated, but it isn’t.
The strange thing is that every other plugins I have are correctly translated.
Plugin Author
chsxf
(@chsxf)
We did not test EDD with mqTranslate. It is possible that EDD requires its translation files before mqTranslate is correctly initialized. We have to make some tests to understand where it breaks.
Plugin Author
chsxf
(@chsxf)
The problem comes exactly from what I stated earlier. EDD imports language files way before mqTranslate is completely initialized, so locale is not updated yet by mqTranslate.
In fact, EDD does not use hooks for its initialization process, so even if we change in the future the way we setup locale modification (and it is not planned at this time), we cannot guarantee the good language files would be loaded for EDD as plugin loading order is unpredictible (I guess it is first activated / first loaded but I am not sure).
I suggest you contact EDD developer to ask them for an update to their plugin.
