Ticket #367 (closed enhancement: fixed)

Opened 2 years ago

Last modified 20 months ago

Change default extension for XLIFF files

Reported by: willydee <willydee@…> Owned by: wei
Priority: normal Milestone: 3.0.7
Component: Prado Framework v3 Version: 3.0
Severity: minor Keywords:
Cc:

Description

According to http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm, an XLIFF file should have the extension ".xlf". Please update the framework to use this as default extension for language files, as some XLIFF translation tools don't accept .xml files.

Please keep the support for .xml files for not breaking existing applications.

Change History

Changed 2 years ago by xue

  • owner changed from xue to wei

Changed 2 years ago by xue

  • milestone changed from 3.0.5 to 3.0.6

Changed 2 years ago by wei

  • status changed from new to closed
  • resolution set to wontfix

Sorry, the design is not flexible enough to be fixed easily :(

Changed 2 years ago by willydee

  • status changed from closed to reopened
  • resolution wontfix deleted

I have a suggestion after inspecting the code of MessageSource? and it's derivatives. What about renaming the current MessageSource?_XLIFF to MessageSource?_XML and extend MessageSource?_XLIFF from it by just overriding

	protected $dataExt = '.xlf';

This would indeed break BC, but there's just one attribute to modify in application.xml to fix the problem, no aggravating application changes are required.

Changed 2 years ago by xue

  • milestone changed from 3.0.6 to 3.0.7

Changed 20 months ago by wei

  • status changed from reopened to closed
  • resolution set to fixed

Supports .xlf if .xml is missing

Note: See TracTickets for help on using tickets.