[EXCONTRANS-193] Translation Service Config - Ability to configure FileFormat Parsing Rule and Default PD Project Created: 09/May/18  Updated: 20/Jul/18  Resolved: 16/May/18

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0

Type: Task Priority: Neutral
Reporter: Trung Luu Assignee: Trung Luu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: 1d

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Scrum Sprint 8

 Description   

What file formats exist besides the one implemented today?

This is not related to the fileformat per se but to the asigned name for a parsing rules set. Upon PD5 all parsing rules set are global (not local to project any longer) so the fileformat could be XML_Magnolia, XML-Magnolia, etc

 

How should the filename be set (naming of individual files in batches to be shortened, numbering or similar to be introduced)?

If the name of the file could be the title of the page or the product name that would make it easier for the biz user and the linguists to identify each exported file with the content those carry



 Comments   
Comment by Trung Luu [ 16/May/18 ]
  • We can update the fileFormat property in the configuration of magnolia-content-translation-support-ext-translation-com module.
Generated at Mon Feb 12 00:28:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.