• Resolved hussong

    (@hussong)


    Using this on a multi-site install, I noticed that the french translation has a (rather confusing) error: in a couple places it says “sans perte” (lossless optimization) where it should say “avec perte” (or something, whatever’s the right term for “lossy optimization” — not a native speaker).

    Hope this helps, thanks!

    https://www.ads-software.com/plugins/ewww-image-optimizer/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Fist thing: I know translating plugins is a big work not easy to do and some errors can be done.

    This said, I found another important mistake:

    One path per line, must be within %s. Use full paths, not relative paths.

    is translated into

    Une chemin par ligne, chacun doit être séparé par %s.\n
    Utilisez des chemins absolus et non pas relatifs.

    “séparé” is “separated” so it says every path must be separated by %s.
    It’s a big mistake and will break the option if the user try to do so.

    I will have a look at the other sentences but this one should be corrected quickly.

    Plugin Author nosilver4u

    (@nosilver4u)

    Li-An, would you mind creating an account at https://translate.ewww.io and fixing the lossy optimization translation? I’ll take a look myself at the other issue with the %s, but it may be difficult for me to figure out exactly what is happening there, so I might need your help on that one too. I’ll reach out to our regular translator as well and see if he can lend any assistance in resolving the issues.

    Plugin Author nosilver4u

    (@nosilver4u)

    As an update, %s represents the filesystem path to your WordPress install. So %s would never show up on the settings page, it should look something like this:

    Une chemin par ligne, chacun doit être séparé par /var/www/wordpress/.
    Utilisez des chemins absolus et non pas relatifs.

    If that still isn’t correct, feel free to register and propose a better translation.

    No problem for the %s, it shows correctly the path. “séparé” is the only problem here. I did register to your translation site.

    Thread Starter hussong

    (@hussong)

    I would like to add that I really appreciate the work of the plugin author and all translators, thank you!

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, I think Li-An took care of the ‘aux paths’ issue, and Dominique took care of standardizing the strings that have ‘lossy optimization’ in them: optimisation avec perte minimale

    Thanks everyone, you’re what makes the open source community so great!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘French translation error’ is closed to new replies.