Bug 103713
Summary: | Evolution's cal's summary doesn't take xim | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | David Joo <djoo> |
Component: | gal | Assignee: | Dave Malcolm <dmalcolm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | eng-i18n-bugs |
Target Milestone: | --- | Keywords: | i18n |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-02 05:16:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 100644 |
Description
David Joo
2003-09-04 05:16:01 UTC
Can you at least do so if you say New Task? I don't think that this can really be fixed without significant ETable changes (a quick look shows that basically just the gtk-event is being taken and turned from a key event into a character) Well, this issue has been fixed in CVS. FYI. 2003-10-14 Suresh Chandrasekharan <suresh.chandrasekharan> * Fix for "44222 task summary entry widget not i18ned". The following files are changed. ... I'm not sure the upstream still be planning to release 1.4.x series, because the upstream started to release 1.5.x. but we still have this problem on both RHEL3 and FC. so could you please backport the patch to fix this problem? They are planning a 1.4.6 release for the next few weeks. I'm planning to definitely do an update for FC1 for this. What happens with RHEL will depend on how many regressions it looks like it causes. Are we in position to push it on RHEL updates? if not we are still happy to use this bug. s/use/close/ and ping :) Closing this bug as it is a bit out-dated. IIIMF will be replacing XIM in the future release. Thanks, Lawrence |