• It would be great to show two columns instead of one for “Translations (PO)” on the main screen. One column would contain “official” translations (from the plugin or theme directory), the other column would contain “user” translations (those saved in wp-content/language).

    Currently it is very hard to know where the translation files are getting saved. In the meantime a good thing would be to show the full file path instead of just the file name.

    https://www.ads-software.com/plugins/loco-translate/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter mayerwin

    (@mayerwin)

    I just submitted a pull request to show more information about the file being edited (though it is not meant to solve the whole issue).
    https://github.com/wp-plugins/loco-translate/pull/1

    Plugin Author Tim W

    (@timwhitlock)

    Thanks for your work. I like the idea of flagging translations that are outside the package.

    Don’t be offended if your pull request isn’t merged. I’m about to start work on a complete rebuild for version 2.0 of the plugin. It will address all the many issues, including the ones you mention here.

    Thread Starter mayerwin

    (@mayerwin)

    No worries about the pull request, it will anyway be helpful to people in the meantime would want to apply this minor commit to their local installation.

    One other thing you may want to look at is Codestyling Localization’s internal compiler. I had this “Not acceptable” error with both the internal compiler and msgfmt (apparently due to due to mod_security on Bluehost; they were able to fix it but may they reduced the server security to achieve this). However Codestyling localization’s compiler worked, so if the license is compatible it may be worth just offering it as an alternative.

    Finally, another feature request to consider would be to add a global search option to find which packages contains a particular string to be translated, when we don’t know to which package(s) it belongs.

    Keep up the great work! I look forward to seeing version 2.0. Locotranslate is the only serious option today for doing efficient (and now persistent) WP translations online.

    Plugin Author Tim W

    (@timwhitlock)

    I’ve received many mod_security issues on this forum, but never got to the bottom of what the issue is (other than it’s well known to break WordPress Ajax requests). I don’t see how the compiler (assuming you mean MO compiler) could cause this, but I’ll take a deeper look some time.

    Thread Starter mayerwin

    (@mayerwin)

    True, it is actually the (different) way Ajax requests are handled that prevents the mod_security issue, than the compiler itself. I even tried to exit PHP before any compilation were processed and still got the error, so it really looks like related to how Ajax communication is implemented.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Feature request: show separately translations from wp-content/languages’ is closed to new replies.