Bug 988164 - TMX export adminlang not a valid RFC3066 language code
TMX export adminlang not a valid RFC3066 language code
Status: CLOSED NOTABUG
Product: Zanata
Classification: Community
Component: Component-Logic (Show other bugs)
development
Unspecified Unspecified
medium Severity low
: ---
: 3.0
Assigned To: zanata-dev-internal
Zanata-QA Mailling List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-24 19:05 EDT by Damian Jansen
Modified: 2013-07-24 20:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-24 20:15:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Damian Jansen 2013-07-24 19:05:38 EDT
Description of problem:
The exported tmx file has, in the header, the language code "en"
TMX Spec 1.4b expects:
"A language code as described in the [RFC 3066]."
This spec indicates a code to be in the format xx_XX, e.g. en_US, but note that TMX uses a hyphen in place of an underscore.

Version-Release number of selected component (if applicable):
Dev

How reproducible:
Easy always

Steps to Reproduce:
1. Go to any project
2. Press the Export to TMX button
3. Save and open the resulting TMX xml file

Actual results:
<header ... adminlang="en" .../>

Expected results:
<header ... adminlang="en-US" .../>

Additional info:
Comment 1 Damian Jansen 2013-07-24 20:15:05 EDT
Missed the part in the specification that says "and a (possibly empty) series of subsequent subtags."
"en" is valid.

Note You need to log in before you can comment on or make changes to this bug.