Suggestion: Changes for translations of public frontend texts

  • Author
  • #114580
    Power User

    Hey Cryouts ๐Ÿ™‚

    in advance: I already know about the translation guides (loco translate/po/mo/…).

    Of course, it would be much more comfortable, to have translations included with the theme.

    I’m sure, for most developer, the texts for the admins can be english, but the (very few) texts on the frontend, which are visible for the visitors, really have to be in the native language. A popular example in yout themes is “To search type and press enter” and “Search Results for:”. It feels disproportionate to use translation-workflows for a few words to translate.

    Maybe there could be an integrated theme option for these few strings to translate?

    Or … can you split the translation-string on into categories/tags/sections/…, like “backend”/”frontend” or “admin”/”public”?
    Then, the initial language pack for each theme could be generated alot earlier, maybe depending on translation progress of the public-category.

    Cryout Creations mastermind


    In WordPress the only way to split translations is using different textdomains.

    The official themes repository only accepts a maximum of 2 textdomains in published themes (one for the theme and one in case a framework is used – which we do, even if it’s our own framework).

    We would have liked to separate translations more logically, but this is impossible within the existing limit.

    If you like our creations, help us share by rating them on
    Please check the available documentation and search the forums before starting a topic.
Viewing 2 posts - 1 through 2 (of 2 total)

The topic ‘Suggestion: Changes for translations of public frontend texts’ is closed to new replies.