Bug 1304116 - gchemtable: "Electronegativity" misspelled in "View:Element charts" menu
Summary: gchemtable: "Electronegativity" misspelled in "View:Element charts" menu
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-chemistry-utils
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Julian Sikorski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 22:44 UTC by Steve
Modified: 2016-02-08 03:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-07 08:55:02 UTC
Type: Bug


Attachments (Terms of Use)
screenshot showing misspelled menu item: "Electronegativty" (28.55 KB, image/png)
2016-02-02 22:44 UTC, Steve
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Savannah 47081 0 None None None 2016-02-07 08:55:01 UTC

Description Steve 2016-02-02 22:44:20 UTC
Created attachment 1120577 [details]
screenshot showing misspelled menu item: "Electronegativty"

Description of problem:
In gchemtable, the spelling should be "Electronegativity" instead of "Electronegativty" in the "View:Element charts" menu.

Version-Release number of selected component (if applicable):
gchemtable-0.14.10-13.fc23.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Display "View:Element charts" menu.

Actual results:
"Electronegativty" is displayed.
              ^^

Expected results:
"Electronegativity" is displayed.
               ^
Additional info:
$ locale | grep LC_CTYPE
LC_CTYPE="en_US.utf8"

Comment 1 Steve 2016-02-04 08:07:06 UTC
In the same menu, "Electron affinity" is misspelled "Electon affinity".

Comment 2 Julian Sikorski 2016-02-07 08:55:02 UTC
This needs to be fixed upstream as the change breaks existing translations.

Comment 3 Steve 2016-02-08 03:24:59 UTC
Thanks, Julian.
Upstream cross-reference:
http://savannah.nongnu.org/bugs/?47081


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