editeng/source/items/svxfont.cxx |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 79152891824581ad765dc8518150027c417bb9a2
Author:     Khaled Hosny <kha...@aliftype.com>
AuthorDate: Sat Sep 24 22:58:20 2022 +0200
Commit:     خالد حسني <kha...@aliftype.com>
CommitDate: Sun Sep 25 09:11:32 2022 +0200

    tdf#83581: Improve caret travelling in in Edit Engine
    
    This uses the same caret positioning array introduced in:
    
    commit 8cb4db941f91cc234dd18c61f8b1e51f65360d1f
    Author: Khaled Hosny <kha...@aliftype.com>
    Date:   Fri Aug 26 22:20:55 2022 +0200
    
        tdf#30731: Improve caret travelling in Writer
    
    But unlike the Writer change, this is used unconditionally not only when
    calculating caret (cursor) position. This might break something, so lets
    find out.
    
    Change-Id: Ia285197b7ee41f01ccd37101436be86b476c0272
    Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140557
    Tested-by: Jenkins
    Reviewed-by: خالد حسني <kha...@aliftype.com>

diff --git a/editeng/source/items/svxfont.cxx b/editeng/source/items/svxfont.cxx
index 65191cab8ed7..9911beec85b0 100644
--- a/editeng/source/items/svxfont.cxx
+++ b/editeng/source/items/svxfont.cxx
@@ -37,7 +37,7 @@ static tools::Long GetTextArray( const OutputDevice* pOut, 
const OUString& rStr,
 
 {
     const SalLayoutGlyphs* layoutGlyphs = 
SalLayoutGlyphsCache::self()->GetLayoutGlyphs(pOut, rStr, nIndex, nLen);
-    return pOut->GetTextArray( rStr, pDXAry, nIndex, nLen, false, nullptr, 
layoutGlyphs);
+    return pOut->GetTextArray( rStr, pDXAry, nIndex, nLen, true, nullptr, 
layoutGlyphs);
 }
 
 SvxFont::SvxFont()

Reply via email to