“Related JSON files” have a higher priority

  • Resolved i have a question

    (@freelancelab)


    2 weeks, 5 days ago

    My generated translation WooCommerce is ignored, “related JSON files” have a higher priority.
    There is no line “Select %s” in my translation. The translation is uploaded automatically. When I make a copy of this translation and tick the “Merge strings from related JSON files” box, the “Select %s” field appears.
    The changes in this translation do not lead to anything.

    https: //www.ads-software.com/support/topic/translations-stopped-being-respected-in-filter-by-attribute-block/#post-18304281

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

    (@timwhitlock)

    This is very confusing post. I don’t really know where to start.

    Is the actual problem that your translations aren’t showing up, or are you confused about the merging of source strings held in JSON files?

    Thread Starter i have a question

    (@freelancelab)

    I need to change the line translation.

    1. The original translation, which is uploaded automatically, does not contain the line I need.
    2. I create a copy of the original translation by combining the JSON files. The line I need appears in my translation.
    3. I’m changing the line translation. But the translation doesn’t change on the website.
    Plugin Author Tim W

    (@timwhitlock)

    Ok, so the only problem is your point no.3.

    I think there may be a bug in compiling JSONs from PO files that have had system JSONs merged in. I’m trying to reproduce it now.

    However, WooCommerce ships with a seemingly reliable woocommerce.pot file, which I can confirm can be used to create custom PO files, and does generate the correct JSON files.

    Plugin Author Tim W

    (@timwhitlock)

    I’ve identified and fixed a reproducible bug, which probably is the cause of your problem.

    This one line fix will produce valid script references (with a line number of 1) during JSON merges, when the script line number isn’t known (i.e. when imported from a JSON translation file). The absence of the line number was causing JSON compilation to skip affected entries.

    To benefit from this fix you’ll have to either install the dev version, or wait for me to release v2.7.3. Then you’ll have to open any PO files that you’ve copied from the GlotPress PO, and run sync (to populate the JSON refs) and save (to recompile the JSONs).

    If that doesn’t fix your issue, please provide steps to reproduce. I’ve verified this fix resolves at least one issue affecting your sample string.

    Thread Starter i have a question

    (@freelancelab)

    Everything is fine now, thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.