[EXCONTRANS-313] "include Sub-nodes" does not include i18n values in xliff in JCR content app Created: 18/Dec/18  Updated: 24/Mar/20  Resolved: 18/Dec/19

Status: Resolved
Project: Content Translation Extended (CTX)
Component/s: Translations.com Translator
Affects Version/s: 2.0.3
Fix Version/s: 3.0.1

Type: Bug Priority: Neutral
Reporter: Sascha Oberhuber Assignee: Teresa Miyar
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.6.X


Attachments: File incorrect.xliff     XML File products.B2B-Produkte.Dispenser.BRITA-VIVREAU-Bottler.BRITA-VIVREAU-Bottler-101-Floorstanding.xml     XML File translationBatches.issue_showcase_batch.xml     XML File translationQueues.OPEN.1545146832695.xml     XML File translationQueues.OPEN.1545146837081.xml     XML File translationQueues.OPEN.1545146837458.xml    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 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.



 Comments   
Comment by Teresa Miyar [ 18/Dec/19 ]

Works on 3.0.1

Generated at Mon Feb 12 00:30:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.