[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (XLIFF-42) Locale Filter in 2 places
David Filip created XLIFF-42:
--------------------------------
Summary: Locale Filter in 2 places
Key: XLIFF-42
URL: https://issues.oasis-open.org/browse/XLIFF-42
Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
Issue Type: Improvement
Components: ITS Module
Affects Versions: 2.1_csprd02
Environment: http://markmail.org/thread/xwtr2naoezptl2aw
Reporter: David Filip
Assignee: David Filip
Priority: Minor
Fix For: 2.1_csprd03
The Locale filter data category is listed in two places:
- In section "5.9.9.3 Locale Filter" as a data category that is not used in
XLIFF
- In section "5.9.6.3 Locale Filter" as a data category defined in the ITS
module
I understand the reasoning behind this: If you have a source file with Locale
Filter you can either A) create an XLIFF where only
the relevant data are extracted, or B) create an XLIFF file with the ITS
metadata.
But I think it is highly confusing to list the data category in both sections.
If Locale Filter attributes can be used in XLIFF then we should have only
section 5.9.6.3. We should also have some text at the top
of that section that basically says something like:
- The best way to extract a source file that uses Locale Filter is to create an
XLIFF file for each target locale with just the
relevant content.
[This *by far* the recommended option: in the real world very few XLIFF tools
will be able to deal with that data category.]
- However, one can also use Locale Filter in XLIFF, and here is how you would do
it... [and have the rest of the current section]
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]