Bug 117455 - improve IIim start and stop messages
improve IIim start and stop messages
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: im-sdk (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Yu Shao
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-04 01:47 EST by Jens Petersen
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-21 23:30:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to change message name to IIIMF server (557 bytes, patch)
2004-03-04 01:55 EST, Jens Petersen
no flags Details | Diff
improved patch (712 bytes, patch)
2004-03-05 01:45 EST, Jens Petersen
no flags Details | Diff

  None (edit)
Description Jens Petersen 2004-03-04 01:47:51 EST
Description of problem:
The startup and shutdown message should be improved.

Steps to Reproduce:
1. service IIim start
2. service IIim stop
  
Actual results:
"Starting[Stopping] /usr/lib/im/htt: "

Expected results:
"Starting[Stopping] IIIMF server: "

Additional info:
This will ease translation too :)
Comment 1 Jens Petersen 2004-03-04 01:55:49 EST
Created attachment 98275 [details]
patch to change message name to IIIMF server

I don't know if "IIIMF server" is friendly enough?

Perhaps it should be "Internet/Intranet Input Method Framework server"
though that this is a little long....
or "IIIMF input method server" is perhaps enough?
What do other people think?
Comment 2 Miloslav Trmac 2004-03-04 08:57:40 EST
The "Stopping..." message should be marked for translation with $"..."
too.
Comment 3 Jens Petersen 2004-03-05 01:45:52 EST
Created attachment 98309 [details]
improved patch

Good point mitr, here's an improved patch.
Comment 4 Jens Petersen 2004-03-10 10:23:53 EST
Should be better in -24.

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