Idea for Translate CPTs and Taxonomies

  • Resolved toto

    (@toto)


    3 years, 4 months ago

    So the plugin stores all CPT on database, but if you generate one php file, and save it one theme directory for example with list of all strings with their localization code _e(‘Custom Post Type Name’, ‘cptui’); may be loco translate will see the strings and will create po mo file for them. What do you thing – the plugin only need one simple option “Store Translation PHP file on wp directory” if any user need translation cheek the checkbox “Use Translation” in plugin settings, and it export the list with all strings.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    3 years, 4 months ago

    Definitely an idea, though I’m not quite sure how to best and elegantly execute this automatically and consistently.

    I do know we have our “Get Code” functionality that generally does that, minus any writing to files. It generates copy/paste-ready code and I believe attempts to grab the textdomain of your active theme, for the output’s gettext functions.

    Would kind of turn the plugin into a generator more than anything, but I consider that a valid use case too.

    Will leave this open in a tab to mull over soon.

    Thread Starter toto

    (@toto)

    3 years, 4 months ago

    Yeah i see now that you have a Tools menu, you can add new tab setting for Translations. Here you place a button “Export Labels for translation”.

    When user press the button – plugin export only labels for CPTs and Taxonomy and save it one one php file in theme/languages directory. That’s all you have 85% of code functionality ready right now. And your plugin will be more useful for the community, because all strings will be visible for other translation plugins – like loco translate with po, mo translations.

    Thank you! 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Idea for Translate CPTs and Taxonomies’ is closed to new replies.