Apache OpenOffice (AOO) Bugzilla – Issue 12877
StarOffice is not providing valid UTF8 strings
Last modified: 2003-04-01 11:43:02 UTC
OVERVIEW DESCRIPTION : Using gnome-2.2 stack from 27 of March, java-access-bridge from today's CVS HEAD, java 2 sdk 1.4.1_01 and StarOffice from 27 February, I found out that StarOffice is NOT providing valid UTF8 strings. STEPS TO REPRODUCE : - launch StarOffice - launch at-poke and poke the "Bold" toggle button from "Text Object Bar" (OR any other child of "Text Object Bar") ACTUAL RESULTS: You will notice, in the terminal from which you lauched at-poke lots of warnings like : ** (at-poke:499): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() ** (at-poke:499): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() ** (at-poke:499): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() EXPECTED RESULTS: I would expect valid UTF8 strings. ADDITIONAL INFORMATION: Screenshot that proves that information provided by StarOffice is generating warnings related to invalidity of UTF8 strings (messages are displayed in the terminal by at-poke).
Created attachment 5364 [details] Screenshot - at-poke inspecting StarOffice
Adi, this is the same cause as in issue 12876. As brackets were reported on these controls these messages were thrown. This is already fixed in newer builds of SO.
Closed