[Fedora-i18n-bugs] [Bug 958802] New: [ibus-typing-Booster][gu_IN]- Proper information to install hunspell dictionary.

[Red Hat Bugzilla]

Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=958802

Bug ID: 958802
           Summary: [ibus-typing-Booster][gu_IN]-  Proper information to
                    install hunspell dictionary.
           Product: Fedora
           Version: 19
         Component: ibus-typing-booster
          Severity: unspecified
          Priority: unspecified
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]
          Category: ---

Description of problem:
When type in gedit using typing booster, First It says "Please install hunspell
dictionary!" through popup window If it's not installed, When i clik on that
part then nothing happened, For new user it's bit confusing.

Suggestion:

There should be proper path For installation like settings->Region &
Language->Gujarati-inscript(hunspell))->go to "Install dictionary" on the
preference window
OR
when click on that part then it should be automatically go to hunspell
dictionary window where we can install it.

Version-Release number of selected component (if applicable):
ibus-typing-booster-0.0.26-1.fc19.noarch

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

[Fedora-i18n-bugs] [Bug 958802] [ibus-typing-Booster][gu_IN]- Proper information to install hunspell dictionary.

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=958802

Mike FABIAN  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|[e-mail]           |[e-mail]

[Fedora-i18n-bugs] [Bug 958802] [ibus-typing-Booster][gu_IN]- Proper information to install hunspell dictionary.

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=958802

--- Comment #1 from Fedora End Of Life  ---
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

[Fedora-i18n-bugs] [Bug 958802] [ibus-typing-Booster][gu_IN]- Proper information to install hunspell dictionary.

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=958802

Fedora End Of Life  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |EOL
        Last Closed|                            |2015-02-17 10:08:12

--- Comment #2 from Fedora End Of Life  ---
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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