Bug 1376031

Summary:	[fix available] Zambia english file is named with dash instead of underscore en-ZM
Product:	Red Hat Enterprise Linux 7	Reporter:	Eric Lavarde <elavarde>
Component:	hunspell-en	Assignee:	Caolan McNamara <caolanm>
Status:	CLOSED ERRATA	QA Contact:	QE Internationalization Bugs <qe-i18n-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	eng-i18n-bugs, qe-i18n-bugs, smaitra
Target Milestone:	rc	Keywords:	i18n
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	hunspell-en-0.20121024-6.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:44:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1395973

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