Bug 191844

Summary: anaconda's progress window should not just cut string to 70 bytes
Product: [Fedora] Fedora Reporter: Roozbeh Pournader <roozbeh>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideKeywords: i18n, Patch
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-16 14:40:14 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:
Attachments:
Description Flags
Patch to fix the problem none

Description Roozbeh Pournader 2006-05-16 01:28:34 UTC 
Description of problem:
Anaconda's progress window just cuts some strings to 70 bytes, which may result
in bad things when they are UTF-8 characters that take two or more bytes
(resulting in the character getting cut in the middle and weird pango warnings). 
Also, in languages where letters are joined (like those using the Arabic or
Indic scripts), getting the string broken in a random place is not the best
option, as weird results may appear to the user.

Instead of a very rough estimate, it should use pango's elipsize support.

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

How reproducible:
Always

Steps to Reproduce:
1. Try to start anaconda in a language that doesn't use the Latin script, like
Persian.
2. Proceed until the package installation progress screen.
  
Actual results:
The strings get cut in bad places, and there are a lot of pango warnings on Alt-F1

Expected results:
Better cutting, and dots at the end if the string is too long.

FarsiWeb's internal reference:
farsiweb #170, anaconda-badcut.patch, originally reported by Elnaz Sarbar, patch
by Roozbeh Pournader
Comment 1 Roozbeh Pournader 2006-05-16 01:28:35 UTC 
Created attachment 129148 [details]
Patch to fix the problem
Comment 2 Jeremy Katz 2006-05-16 14:40:14 UTC 
Committed... thanks for the patch!