Bug 469665 - The whole paragraph words cut are displayed at "Undo" line.
The whole paragraph words cut are displayed at "Undo" line.
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openoffice.org (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Caolan McNamara
Depends On: 469145
  Show dependency treegraph
Reported: 2008-11-03 06:23 EST by Suqin Huang
Modified: 2008-11-03 07:02 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-03 07:02:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Suqin Huang 2008-11-03 06:23:13 EST
+++ This bug was initially created as a clone of Bug #469145 +++

Created an attachment (id=321899)
The actual result

Description of problem:
The whole paragraph words cut are displayed at "Undo" line.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create one file and write one paragraph Chinese words. Make sure there is no Enter or space between two words.
2. Cut this paragraph.
3. Click "Edit" at menu bar.
Actual results:
Navigation in "Edit" can not display clearly, the whole paragraph which is cut appear at one line in "Undo" line. 

Expected results:
Only the first several words and last several words are displayed, others are superseded by "...".
Comment 1 Caolan McNamara 2008-11-03 06:35:46 EST
Effort in the RHEL-4 area for non-regressions when we have RHEL-5 out doesn't make a whole pile of sense to me. We should fix it for RHEL-5 and devel, I'm reluctant for RHEL-4 unless there is some particular demand for it.
Comment 2 RHEL Product and Program Management 2008-11-03 07:02:54 EST
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

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