Apache OpenOffice (AOO) Bugzilla – Issue 79658
Cursor traveling and Writer input when a non-CTL script needs CTL processing
Last modified: 2017-05-20 11:22:48 UTC
For advanced typography it does not matter what the script type is. When the typographic layout engine does some fancy processing for the active font this must be taken into account. Currently this more complex and time consuming processing is only enabled for CTL-scripts. It should be enabled depending on the font and the font features that are activated.
The info about the typographic complexity of a font should be requested from the subsystem responsible for typographic layout, e.g. by calling the OutputDevice::GetFontMetric() method. Until this gets implemented here is a temporay workaround to enable CTL-processing for all interactive text input into Writer: --- sw/source/core/text/itrform2.cxx 23 Jan 2007 08:31:48 -0000 1.99 +++ sw/source/core/text/itrform2.cxx 16 Jul 2007 11:59:07 -0000 @@ -2020,8 +2020,10 @@ // --> FME 2004-09-27 #i28795#, #i34607#, #i38388# // step back six(!) more characters for complex scripts // this is required e.g., for Khmer (thank you, Javier!) +#if 0 // removing the if() unconditionally enables CTL for text input into Writer const SwScriptInfo& rSI = GetInfo().GetParaPortion()->GetScriptInfo(); if ( ScriptType::COMPLEX == rSI.ScriptType( nReformat ) ) +#endif { if ( nReformat > GetInfo().GetLineStart() + 6 ) nReformat -= 6;
Reset assigne to the default "issues@openoffice.apache.org".