why on earth

  • Resolved tbaikamine

    (@tbaikamine)


    3 years, 10 months ago

    am holding myself so hard from using any profanity language.
    but please someone help me understand why even think of making this: pll_register_string ????????
    just why ?
    i dont understand why this plugin gainged popularity while it must be hated by most developers. (I guess because most end users don’t understand the damage it’s making)
    why do something to damage the community standards ?
    now all plugins and themes need to change the _() and _e() functions to pll_register_string() ????
    there is already an existing i18n STANDARD accross ALL plugins and themes in the wordpress directory
    you had one job ! only one job to do: make a l11n plugin giving users a widget for switching language, and maybe an admin menu where users can translate strings (THAT WERE ALREADY PROVIDED BY THE ENTIRE COMMUNITY USING THE EXISTING WORDPRESS i18n STANDARDS)
    none of them can SIMPLY be translated.
    now whever I download a plugin I have to open its files and look for every _() function and change it to pll_register_string() ?

    • This topic was modified 3 years, 10 months ago by tbaikamine.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Chouby

    (@chouby)

    Hello,

    now all plugins and themes need to change the _() and _e() functions to pll_register_string() ????

    Where did you read this? Do you really believe that 600,000 users are modifying the thousands of files of their theme and plugins and repeat the operation at each update?

    Install your plugins and your theme. If they are already translated by the community, then you don’t have to do anything more. If they are not translated, then do it as you would for any site in only one (non-English) language. You know: the existing WordPress i18n standards.

    If you don’t understand the need for pll_register_string(), just ignore it.

    Thread Starter tbaikamine

    (@tbaikamine)

    the question is: how ?
    say I installed a plugin/theme and no one in our beautiful community already translated it.
    YOUR “Strings translations” admin submenu is UNCAPABLE of listing strings wrapped in __() or _e() functions in the so called plugin/theme
    so again: how ?
    after couple of hours doing research I found a plugin “Theme and plugin translation for Polylang (TTfP)” that fixes the faulty plugin of yours.
    now that we answered the “how”. this brings me back to the title of my question: WHY ?
    just why on earth something that is soo simple by nature
    we work so hard to make it complicated.
    I don’t want to waste more time trying to understand the need for pll_register_string()
    because am afraid once I discover that. it would be a silly reason and I will end up jumping from the window

    • This reply was modified 3 years, 10 months ago by tbaikamine.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘why on earth’ is closed to new replies.