Difference between translation.wp.org and local .po

  • My site is current with all updates, automatically as to ?Updates settings?, and ?Updates? says: Your translations are all up to date.

    When I open Loco Translate I see a total of 3706 strings for WordPress Core German (which is identical to translate.www.remarpro.com), but after syncing that changes to: Updated: 25. January 2020 0:01 – 99.9% translated, 2,876 strings (1 untranslated). Suddenly ?XML Error: %1$s at line %2$s? isn’t translated anymore!

    Why those differences?

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

    (@timwhitlock)

    If a translated string is no longer translated, it means the source text changed. It only has to change by one byte, because Loco Translate does not perform fuzzy matching when sources are changes.

    What are you syncing to?

    WordPress does not ship with a POT file, so syncing any PO file will be extracting from source. I don’t recommend doing this.

    So, configure your WordPress core bundles to use a canonical PO file as a template before syncing any PO files. See What if there is no template.

    Thread Starter Frank Spade

    (@spade)

    Thank you Tim, I have to let this sink in. Thanks for the link to your dokumentation (as a lector I recognized there a double ?into?, which you may want to correct).

    Plugin Author Tim W

    (@timwhitlock)

    Thanks for the correction. I will update in due course.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Difference between translation.wp.org and local .po’ is closed to new replies.

Tags