Bug 703211 - Typo in a message
Summary: Typo in a message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: im-chooser
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-09 16:44 UTC by dmoctezuma
Modified: 2011-08-22 15:28 UTC (History)
3 users (show)

Fixed In Version: im-chooser-1.5.0.1-2.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-10 02:54:26 UTC
Type: ---


Attachments (Terms of Use)

Description dmoctezuma 2011-05-09 16:44:29 UTC
Description of problem:
#: ../src/ui/im-chooser-simple.c:483
"<small><i>Note: this change will not take effect until you next log "
"in%s</i></small>"

it should be

"<small><i>Note: this change will not take effect until your next log "
"in%s</i></small>"


Also, I'd like to point out that there is no separation between the message and the variable %s: "next log in%s". Can you confirm if that separation is correct?


How reproducible:
If you are translating the corresponding .pot file you will find the above message.


Steps to Reproduce:
1. Open the im-chooser .pot file.

Expected results:
Instead of "you next log in", should be "your next log in".

Comment 1 Akira TAGOH 2011-05-30 10:14:23 UTC
Fixed in upstream. will be pushed in next release.

http://git.fedorahosted.org/git/?p=im-chooser.git;a=commit;h=7a27909f123bc10b97c0612c4333181689fc601d

Comment 2 Fedora Update System 2011-08-09 10:16:37 UTC
im-chooser-1.5.0.1-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/im-chooser-1.5.0.1-2.fc16

Comment 3 A S Alam 2011-08-10 02:54:26 UTC
it is fixed with im-chooser-1.5.0.1-2.fc16

Comment 4 A S Alam 2011-08-10 02:54:50 UTC
rawhide->Fedora 16

Comment 5 Fedora Update System 2011-08-22 15:28:21 UTC
im-chooser-1.5.0.1-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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