Uploaded image for project: 'Content Translation Extended (CTX)'
  1. Content Translation Extended (CTX)
  2. EXCONTRANS-313

"include Sub-nodes" does not include i18n values in xliff in JCR content app

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Neutral
    • Resolution: Obsolete
    • Affects Version/s: 2.0.3
    • Fix Version/s: 3.0.1
    • Labels:
      None
    • Environment:
      Magnolia 5.6.X
    • Template:

      Description

      Hi all,
      here's another issue.

      On a content app I configured to be translatable, selecting "include sub-nodes" in the "add to batch" dialogue does not include translatable properties from subnodes in the xliff. Translatable properties do show up in the "i18nFields" property of the mgnl:translationSubmission node, however.

      I came across this issue while investigating EXCONTRANS-312, and the outcome is the same (NPE during download, because number of trans-units doesn't match). But as I expected the xliff to contain the properties in this scenario, I figured it warranted a separate report.

      Same note as on the other ticket: The i18n properties carry the same name between main node and subnodes.

      If this ends up being a configuration issue, I'd appreciate a hint on how to circumvene it.

      Attachments:

      • Export of the batch
      • Export of all related entries in "translation queues"
      • Export of the related content item
      • One of the (incorrect) xliffs

      The app used to create the content is identical to EXCONTRANS-312.

        Attachments

          Activity

            People

            Assignee:
            tmiyar Teresa Miyar
            Reporter:
            soberhuber Sascha Oberhuber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response: