OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Public Comment


Comment from: rodolfo@heartsome.net

Name: Rodolfo M. Raya
Title: Director of Product Development
Organization: Heartsome Holdings Pte Ltd
Regarding Specification: XLIFF 1.1 / XLIFF 1.2


Today I received a file with this format:

<?xml version="1.0" encoding="utf-8"?>
<xlf:xliff version="1.1" xmlns:xlf="urn:oasis:names:tc:xliff:document:1.1">
  <xlf:file datatype="xml" original="source.xml" source-language="en">    
    <xlf:body>
          <xlf:trans-unit id="1" datatype="xml">
            <xlf:source>hello</xlf:source>
          </xlf:trans-unit>
    </xlf:body>
  </xlf:file>
</xlf:xliff>


By using a prefix in namespace declaration the names of the XLIFF elements are altered. This is a complication for tools that support XLIFF files and relay on standard element names instead of fully qualified names.

XLIFF specs do not mention the use of prefixes for the XLIFF namespace. Which is the position of the XLIFF TC regarding this use of the XLIFF namespace?

Could an official recommendation or a best practise statement be added to the XLIFF 1.2 specs?

Best regards,
Rodolfo M. Raya


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]