Incorrect use of _n()

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Tim W

    (@timwhitlock)

    My source singular should read “%s string marked Fuzzy” because the intention is NOT that the first form be used for exactly one.

    This is merely bad form on my part using a literal “1” in the English singular. I hadn’t considered that this might be misleading to translators, causing them to copy the “1” into their first form. Mostly they don’t though, which is why this hasn’t been picked up since it was added in 2017.

    Interestingly in this example the original Russian translator had added the first form correctly using a placeholder and then later another translator changed it to a literal “1” making the translated text incorrect. That change was approved by you almost three years ago.

    I accept that my style is also bad for validation so does need changing. Doing so will obviously invalidate a lot of source strings and cause translators unnecessary work. I would not do that if there were no erroneous translations out there, but it seems there are. So I will make this change and mark resolved when in trunk.

    Plugin Author Tim W

    (@timwhitlock)

    I’ve fixed this in trunk now. You will see that all languages that were at 100% are now at 98% after four source strings were changed.

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

    Moderator Yui

    (@fierevere)

    永子

    Thank you.
    Fixed the fuzzies for russian.
    —

    CC notification @kleindberg

    +1

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Incorrect use of _n()’ is closed to new replies.