- This topic has 3 replies, 3 voices, and was last updated 8 years, 11 months ago by
.
Viewing 4 posts - 1 through 4 (of 4 total)
-
Posts
-
Hi, I am using the loco translate plugin to add my translation. Since I want to keep the translation during theme/plugin update, I am using the global language directory to store my translation. However, both wplms theme and vibe-course-module didn't declare its text domain, and the former use wplms/locale.[mo|po] in global directory, and the latter use vibe-locale.[mo|po] in the global directory. Since loco translate loads the translation file according to text domain, it can't find the translation of wplms theme and vibe-course-module in global directory.Please note the text domain of wplms theme has nor prefix and is like " en_US.po/mo " . But the vibe course module plugin has prefix in its text domain like " vibe-en_US.po/mo " . I would recommend you to use the code styling localization plugin .ALthough it is outdated now but it reads the text domians accurately and also the translation do not gets removed when on update of you install the preserver plugin also . refer : https://wplms.io/support/knowledge-base/translate-using-codestyling-localization-plugin/I mean declare text domain in the comment area of style.css for the theme and loader.php for the plugins. I see this is already done in other plugins such as vibe-shortcodes.Yes, you're correct. However, the text domain is declared in the function which applies the translation. Since we used Codestyling location plugin it did not require text domain declaration, but now it seems this is an issue with the Loco translate plugin. Thanks for pointing this out. We'll add this in next update. Moving this topic to issue log.
Viewing 4 posts - 1 through 4 (of 4 total)
- The topic ‘text domain issue – compatibility with loco translate plugin’ is closed to new replies.