Fix typo "then"->"than"

Change-Id: Ic8a5797b0196f36288bf0af984dd074a2a443198
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/202919
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Tested-by: Julien Nabet <serval2412@yahoo.fr>
This commit is contained in:
Andrea Gelmini
2026-03-29 09:45:27 +02:00
committed by Julien Nabet
parent 19c19b98a8
commit e95334a66e
5 changed files with 5 additions and 5 deletions
@@ -464,7 +464,7 @@ public class AccessibilityTreeModel
// Map to translate from accessible object to corresponding tree node.
private final NodeMap maNodeMap;
// If the lock count is higher then zero, then no events are processed.
// If the lock count is higher than zero, then no events are processed.
private int mnLockCount;
private Canvas maCanvas;
+1 -1
View File
@@ -250,7 +250,7 @@ static void impl_unpackLocalizedProperties( const Sequence< OUString >& l
// => I think we should make it fast for i). ii) is a special case and mustn't be SOOOO... fast.
// We should reserve same space for output list like input ones first.
// Follow algorithm looks for these borders and change it for ii) only!
// It will be faster then a "realloc()" call in every loop ...
// It will be faster than a "realloc()" call in every loop ...
nSourceSize = lInNames.getLength();
lOutNames.realloc ( nSourceSize );
+1 -1
View File
@@ -55,7 +55,7 @@
// API calls, all widgets are drawn without text. Drawing of text is done separately by VCL on top of graphical Carbon widget
// representation. drawNativeControl is called by VCL using content rectangle determined by getNativeControlRegion.
// FIXME: when calculation bounding rectangle larger then content rectangle, text displayed by VCL will become misaligned. To avoid
// FIXME: when calculation bounding rectangle larger than content rectangle, text displayed by VCL will become misaligned. To avoid
// misalignment bounding rectangle and content rectangle are calculated equally including adornments. Reduction of size for content
// is done by drawNativeControl subsequently. Only exception is editbox: As other widgets have distinct ControlPart::SubEdit control
// parts, editbox bounding rectangle and content rectangle are both calculated to reflect content area. Extending size for
+1 -1
View File
@@ -1603,7 +1603,7 @@ sk_sp<SkImage> SkiaSalGraphicsImpl::mergeCacheBitmaps(const SkiaSalBitmap& bitma
if (targetSize.Width() > drawAreaSize.Width() || targetSize.Height() > drawAreaSize.Height())
{
// This is a bit tricky. The condition above just checks that at least a part of the resulting
// image will not be used (it's larger then our drawing area). But this may often happen
// image will not be used (it's larger than our drawing area). But this may often happen
// when just scrolling a document with a large image, where the caching may very well be worth it.
// Since the problem is mainly the cost of upscaling and then the size of the resulting bitmap,
// compute a ratio of how much this is going to be scaled up, how much this is larger than
+1 -1
View File
@@ -32,7 +32,7 @@ static sal_uInt16 ImplAccelEntryGetIndex( const ImplAccelList* pList, sal_uInt16
size_t nCount = pList->size();
sal_uInt16 nCompareId;
// check if first key is larger then the key to compare
// check if first key is larger than the key to compare
if ( !nCount || (nId < (*pList)[ 0 ]->mnId) )
{
if ( pIndex )