Bug 178002 - Afrikaans myspell dictionary in OpenOffice.org has broken suggestions
Summary: Afrikaans myspell dictionary in OpenOffice.org has broken suggestions
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-17 07:46 UTC by Dwayne Bailey
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-01-26 09:56:12 UTC

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

Description Dwayne Bailey 2006-01-17 07:46:24 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
When spell checking using the Afrikaans Myspell spell checker any suggested spellings contain broken characters.  The errors looks as if it is displaying UTF-8 characters in ISO-8859-1.

On investigation the file:
/usr/lib/openoffice.org2.0/share/dict/ooo/af_ZA.dic
is encoded using UTF-8.

This file should be in ISO-8859-1

Version-Release number of selected component (if applicable):
openoffice.org-langpack-af_ZA-2.0.1.1-4.1

How reproducible:
Always

Steps to Reproduce:
1. Install openoffice.org-langpack-af_ZA-2.0.1.1-4.1
2. Using OpenOffice.org type the following word: geirriteer
3. Select the word
4. Format->Character - change the text to Afrikaans
5. Word should be misspelled.  Now right click and view suggestions.
  

Actual Results:  The following suggestions appear in the list:
ge�riteer
...

Expected Results:  This word should be displayed:
ge�rriteer

Additional info:
Comment 1 Caolan McNamara 2006-01-17 09:49:36 UTC 
A newer upstream dictionary is available. I'll include that instead
Comment 2 Caolan McNamara 2006-01-26 09:56:12 UTC 
fixed in rawhide, will be backported when there is a future respin for FC-4
Note You need to log in before you can comment on or make changes to this bug.