FS#29854 - The libreoffice build of 3.5.2.2 does not wordwrap CTL words properly

Attached to Project: Arch Linux
Opened by ido (ik_5) - Saturday, 12 May 2012, 09:18 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 19 May 2012, 19:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
LibreOffice 3.5.2.2 does not wrap words using CTL languages (Hebrew for example) properly.
The issue seems to be something with the build itself, because Fedora and Debian unstable does not contain the issue with the same versions.

The problem is that the word does not go to the next line, but part of the chars of that words only go to the next line.
In English (even on right to left paragraph), it takes the whole word to the next line as expected.

Additional info:
* LibreOffice 3.5.2.2

Steps to reproduce:
* In Options -> Languages Settings -> Languages, enable the support for CTL languages and choose at the combobox of CTL Hebrew as the language.
* approve the settings, and start writing letters in Hebrew, and separate part of them with space.
* When part of the word arrive at the end of the line, and you continue to write it, part of the chars will appear on the next line.

Expected Results:
* The whole word should arrive to the next line.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 19 May 2012, 19:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in 3.5.3-3
Comment by Andreas Radke (AndyRTR) - Saturday, 12 May 2012, 14:03 GMT
This sounds more like a bug in ICU. You can try to recompile LibreOffice using (older) internal ICU and recheck if other programs using our latest ICU libs are also broken.
Comment by Andreas Radke (AndyRTR) - Sunday, 13 May 2012, 12:12 GMT
Is this the correct upstream bug?

https://bugs.freedesktop.org/show_bug.cgi?id=49849
Comment by Assaf Sapir (meijin) - Monday, 14 May 2012, 09:23 GMT
yes it is. as you can see - the bug is solved for 3.6 - so can you please use the patch on this version, meanwhile?

Loading...