Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 675623

Summary: Wrong language for spell checking - pt_BR instead of pt
Product: [Fedora] Fedora Reporter: António Lima <amrlima>
Component: virtaalAssignee: Dwayne Bailey <dwayne>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: dwayne
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Fixed In Version: virtaal-0.6.1-7.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-18 01:52:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description António Lima 2011-02-06 23:59:40 UTC
Description of problem:

I use my Fedora system with language set to pt (European Portuguese) but for some reason virtall set the spell checker to Basilian Portuguese. I have to change it every time.

This does not happen with other apps nor with virtaal in Debian for example.

Comment 1 Dwayne Bailey 2011-02-07 06:42:33 UTC
Thanks for the report.

I need a bit more information to help diagnose this.

1) Which version of Virtaal are you using? 0.6.1 or 0.7beta4?  If you are using 0.6.1 would you mind installing 0.7 beta4 from the following repo?

Virtaal will be releasing a 0.7 version soon so I'd like to make sure that this is fixed in that version.

2) When you say "I have to change it every time" do you mean change it in the language switcher the one that says 'English -> Portuguese' or in spell checers popoup menu where you can select an entry from the 'Languages' menu entry?

3) Could you maybe provide a small snippet of pt_PT text that is spelled correctly but mispelled in pt_BR.  Without being able to understand either this would allow us to test when the checker is in the correct configuration.

Thanks again for reporting this and hopefully with your help we can fix it.

Comment 2 António Lima 2011-02-07 14:55:42 UTC

Sorry for the little detail in the bug report, it was a late night bug :).

2- I have to change the language in the pop-up menu from pt_BR to pt_PT. The language pair is correct in the language switcher: English -> Portuguese. (there is also the option for English -> Portuguese (Brasil).

3- pt_PT -> O tempo está muito húmido para fazer algo activo.
pt_BR -> O tempo está muito úmido para fazer algo ativo.
Note the words "húmido/úmido" and "activo/ativo".

1- I'm using virtaal 0.6.1. I've tested 0.7 from the above and the bug is more serious. I'll explain. With 0.7 the language switcher is set to the correct language pair once more- English -> Portuguese - but pt_PT spelled words are marked as incorrect, so the used dictionary is the pt_BR. The problem is that there is no switcher from pt_BR to pt_PT in the pop up menu as in 0.6.1. This makes virtaal 0.7 unusable to translate to pt_PT as you can imagine...

Note very relevant right now, but just as a side note, there is an undergoing process of unifying the spelling of pt_PT and pt_BR [1]. The new spelling is starting to be used now but I think only in 2016 it will be mandatory to write in the new spelling. That I know of, there is no open-source spell checker for it yet. But I'm sure there will be some in the next few years.


Please let me know if I can provide any further info.


Comment 3 Dwayne Bailey 2011-02-08 07:35:08 UTC
I've reported this upstream at

Thanks for the feedback.  We think the problem is happening because of the following:

1) On Fedora there is no pt spell checker but a pt_PT and pt_BR one
2) Our spellchecker provider looks like it tries to find a pt_* checker when no pt is provided
3) It seems to take the first one pt_BR

We'll do some experiments but will probably hardode pt to pt_PT.

I wonder how people will represent the language code once the spellings are unified, do you have any idea?  Not a priority as this is 5 years away.

Comment 4 António Lima 2011-02-08 11:54:19 UTC
Thank you for working on this. Hope it can get fixed.

As for the new language code, I am not aware of how it will be represented. There are other Portuguese speaking country's (mostly in Africa) that as not ratified the agreement and so there are still different spellings... Anyway, it's really not a priority now.

Thanks again.

Comment 5 Dwayne Bailey 2011-02-09 14:12:26 UTC
(In reply to comment #4)
> Thank you for working on this. Hope it can get fixed.

Upstream is fixed see

I will try to backport this to Fedora.

Comment 6 Fedora Update System 2011-02-09 16:28:18 UTC
virtaal-0.6.1-7.fc14 has been submitted as an update for Fedora 14.

Comment 7 António Lima 2011-02-09 16:37:14 UTC
That was fast! Thank you!

Comment 8 Dwayne Bailey 2011-02-09 17:03:25 UTC
(In reply to comment #7)
> That was fast! Thank you!

Pleasure, please test.  I tested the path on 0.7 and it worked, but 0.6.1 is very different when it comes to spelling.

Comment 9 Fedora Update System 2011-02-09 20:19:06 UTC
virtaal-0.6.1-7.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update virtaal'.  You can provide feedback for this update here:

Comment 10 Fedora Update System 2011-02-17 12:07:33 UTC
virtaal-0.6.1-7.el6 has been submitted as an update for Fedora EPEL 6.

Comment 11 Fedora Update System 2011-02-18 01:52:18 UTC
virtaal-0.6.1-7.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2011-03-04 20:25:04 UTC
virtaal-0.6.1-7.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.