https://issues.apache.org/ooo/show_bug.cgi?id=108388
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from [email protected] --- Created attachment 83559 --> https://issues.apache.org/ooo/attachment.cgi?id=83559&action=edit attempt to reproduce Unable to reproduce in AOO4.1.0 Build: AOO410m18(Build:9764) - Rev. 1589052 OS: Win7 Professional SP1 (OS language: English; Location: Netherlands) Pre-conditions: 1) Windows Input Language is 'Bengali (Bangladesh)' with keyboard 'Bengali' 2) Bengali font available in Windows: Mukti Narrow 3) OpenOffice Language settings: Default languages for documents - CTL: Bengali (Bangladesh) As can be seen in the attached file 'Issue108388_Bengali_MuktiNarrow.odp', I tried the following: 1) type a space then text in comment, text box or Options > User Data (slide 1) 2) type text not preceded by space in comment, text box, note (slide 2) 3) type text not preceded by space in Options > User Data (slide 3) Language settings and font are as described in the Pre-conditions. With 1) I was able to reproduce boxes in the comment as per the original bug report. However, comparing screenshots it looks to me that in the orignally screenshot, the first character in the comment is not a space. So I don't think I reproduced the actual bug. Also note that with 2) and 3) I was able to produce a box being displayed in the comment and in the User Data by entering only one character. However, this doesn't match the original report either as that had several characters inserted into the comment. Based on my test it seems that OpenOffice handles Bengali (and perhaps other complex scripts (http://en.wikipedia.org/wiki/Complex_Text_Layout) too) in two different manners: - In text boxes and notes the first character entered is displayed. When the second character is entered, the characters are combined if needed. If the first character is a space, this is not an issue. - In comments and the User Data fields a square is displayed instead of the actual first character. When the second character is entered, the characters are combined if needed. If the first character is a space, character interpretation fails. I have no idea to what degree the above is related to the original bug report, as I was not able to exactly reproduce the original report. I had to prepend a space to the text in a comment field to get multiple boxes to display. Secondly, I see no difference in behaviour between the comments and the User Data, while the original reporter did. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
