Bug 648773 - abiword in LXDE Fedora Spin - Major bug with Japanese/Chinese/Korean input.
Summary: abiword in LXDE Fedora Spin - Major bug with Japanese/Chinese/Korean input.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abiword
Version: 13
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Marc Maurer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-02 04:05 UTC by nomnex
Modified: 2011-06-28 10:57 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:57:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description nomnex 2010-11-02 04:05:51 UTC
Description of problem:

I am using using the Fedora 13 LXDE Spin. My machine is a low specification (old) and my preference is a light-weight OS, and Software (LXDE rocks compared to a bloated Gnome or KDE, in my opinion). I am particularly happy of with the Fedora LXDE Spin, but I need advice.

The default Office application of the F13 LXDE Spin are gnumeric & abiword. They are somewhat inseparable as a replacement of a basic OpenOffice installation.

If gnumeric perform fine, Abiword suffers a long standing major bug with Asian input. There are already some upstream bug reports. The bug reports date from 2005 and are most of them are not assigned with a status of NEW. Nowadays Asian languages have become more popular and their use have broaden.

All the applications I know (Open-office, gedit, gnumeric, etc.), but Abiword, comply homogenously to the older SCIM and newer I-Bus input method.

This is not only a bug affecting productivity. This is a bug preventing Abiword being used with an Input method (I-bus). The only alternative I see are installing Openoffice.org (quite heavy on additional libraries) or learning LaTeX.

My question is the following: Since upstream bugs are stagnant since 2005, but Abiword is now part of a Fedora Distribution (Lxde Spin). Could the contact between a dev. from redhat or fedora with a dev. of Abiword be easier and straight forward? I am only a end user who has commented on some of the upstream bugs. Some advice in the way to proceed correctly is welcome (as to know what can I expect). Thank you.

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

Abiword 2.8.6

How reproducible:


Steps to Reproduce:
1. Open a new document
2. Start i-bus input method
3. The Japanese/Chinese/Korean, etc. input appears in a small windows beneath abiword. The input does not display directly inside the open document. You need to push the enter key after each input to display the input in the open document.
  
Actual results:

see above

Expected results:

On-screen display of the input in the open document window (Abiword)

Additional info:

See upstream bugs:

http://bugzilla.abisource.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=AbiWord&content=Japanese

http://bugzilla.abisource.com/show_bug.cgi?id=5801

http://bugzilla.abisource.com/show_bug.cgi?id=10756

Comment 1 Marc Maurer 2010-11-02 20:50:25 UTC
I'm AbiWord's maintainer, so I might be able to get this working. No promisses though, as I have no clue how IMs are supposed to work, let alone how Japanese IMs are supposed to work.

Let's take this up at http://bugzilla.abisource.com/show_bug.cgi?id=10756 , I've added my questions there.

Comment 2 nomnex 2010-11-03 12:46:37 UTC
Hello Marc.  Thank you for the feedback.  I don't think there is much difference between the East Asian languages selected, but more in the way Abiword understand the i-bus framework input.  I answer your question on the bugzilla page.

Comment 3 nomnex 2010-11-06 12:12:34 UTC
Hello Marc, I have updated the bugzilla.abisource.com with 2 print screens. I also sent a message to the abiword list at destination of msevior, (following jean's recommendation). Do you communicate with each other? They would surely provide a better information. I am only an end-user and my understanding is limited. If you have some free time and if you are still willing looking into this bug, I welcome some feedback. It would be nice to be able to use Abiword with East Asian languages.

Comment 4 Bug Zapper 2011-05-30 14:22:14 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-28 10:57:12 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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