Bug 82116

Summary:	CJK: Font change does not update composition string immediately
Product:	LibreOffice	Reporter:	Matthew Francis <fdbugs>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	medium	CC:	fdbugs, foss, iplaw67, jorendc, philipz85
Version:	Inherited From OOo
Hardware:	Other
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	83066

Description Matthew Francis 2014-08-04 04:40:29 UTC

On OSX 10.9.4 / LO 4.3.0.4 release:

Steps to reproduce:
1. Create a new Writer document
2. Start typing any Japanese text with the 'Kotoeri' - 'Hiragana' input method. For instance, 'aaaaaaaaaaaaaaaaa' (which will produce the text 'ああああああああああああああ')
4. Without confirming the input conversion (i.e. without pressing 'Return'), select a new font from the font dropdown

Expected result:
The new font is immediately applied to the selected mid-conversion text

Actual result:
The new font is applied to the selected mid-conversion text *only after another character is entered*


This was discovered while reporting bug 82115 - it seems like the issues are separate but I could be wrong about that

I have only observed this in Writer for the reason that changing the font mid-conversion in a spreadsheet or presentation appears to have no effect at all on the selected text. Should this inconsistency be yet another bug?

Comment 1 Jay Philips 2014-08-05 05:48:00 UTC

Hi Matthew,

Thanks for another bug and the simple instructions. Mac team added.

Comment 2 Alex Thurgood 2014-10-15 15:18:32 UTC

Confirming on OSX 10.9.5

There always seems to be one character extra, no matter what the font. This might have something to do with the input checking code which has to decide whether the combination of letters entered is a valid character ?

Comment 3 Matthew Francis 2015-01-19 05:35:05 UTC

Occurs all the way back to 3.3.0 (and still in 4.4.0.2)

Setting Version to "Inherited from OOo"

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.