Bug 1376031 - [fix available] Zambia english file is named with dash instead of underscore en-ZM
Summary: [fix available] Zambia english file is named with dash instead of underscore ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: hunspell-en
Version: 7.2
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Caolan McNamara
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1395973
TreeView+ depends on / blocked
 
Reported: 2016-09-14 13:15 UTC by Eric Lavarde
Modified: 2017-08-01 16:44 UTC (History)
3 users (show)

Fixed In Version: hunspell-en-0.20121024-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 16:44:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1963 0 normal SHIPPED_LIVE hunspell-en bug fix update 2017-08-01 17:56:24 UTC

Description Eric Lavarde 2016-09-14 13:15:47 UTC 
Description of problem:
All files have an underscore between language and country, only en-ZM is with a dash.

Version-Release number of selected component (if applicable):
hunspell-en-0.20121024-5.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. rpm -ql hunspell-en
2.
3.

Actual results:
All files are named /usr/share/myspell/en_XX.* and only Zambian English is /usr/share/myspell/en-ZM.*

Expected results:
All files are named with underscore like /usr/share/myspell/en_XX.*

Additional info:
Not a big thing but it has bitten me as I wanted to automate something with a small one-liner; with such "exceptions", "small" becomes rather complicated...
Comment 1 Caolan McNamara 2016-09-14 13:33:41 UTC 
Fixed in fedora since b8bc6f7f hunspell-en.
Comment 2 Satyabrata Maitra 2017-02-15 13:08:15 UTC 
qa_ack provided.
Comment 5 errata-xmlrpc 2017-08-01 16:44:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1963
Note You need to log in before you can comment on or make changes to this bug.