Bug 213697 - kile: aspell component. It is broken (utf-8) after updating to kde-3.5.5
Summary: kile: aspell component. It is broken (utf-8) after updating to kde-3.5.5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kile
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-02 16:58 UTC by Luis
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 1.9.3-1
Clone Of:
Environment:
Last Closed: 2006-12-05 20:32:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Luis 2006-11-02 16:58:50 UTC
Description of problem:

After the recent update of kde to 3.5.5 the aspell component is broken in kile
for non english languages.
It does not recognise utf-8 characters such as ñ á è.
Moreover, the words suggested for these languages are visualized wrong if they
contains such characters. 
I have proved with texts in utf-8 and in ISO-8859-1 Everything works correctly
but aspell.

If I use kate, then I have no problems with the same utf-8 file. Aspell works
well. The same problem happens with the text in ISO-8859-1 but this is expected
as aspell is supposed to work with utf-8.
Also aspell from a terminal against the same utf-8 file works perfectly.

So, it seems that kile is trying to contact aspell in iso-8859-1

Version-Release number of selected component (if applicable):
kile-1.9.2-1.fc5

How reproducible:
Always

Steps to Reproduce:
1. Write an utf-8 text with some accents: Ej "ès un problemón"
2. Run the aspell corrector
  
Actual results:
The words with non ascii-7 characters are recognized wrong. The sugested words
with accents are visualized wrong.

Expected results:
The words should be recognized and visualiced correctly.

Comment 1 Rex Dieter 2006-12-05 20:32:21 UTC
kile-1.9.3-1 is now available from Extras.

If this update doesn't address your issue, please re-open the bug.


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