drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit aad2ca8bd3986510b2331752d92958c96ec93f9f
Author: Andrea Gelmini <andrea.gelm...@gelma.net>
AuthorDate: Wed May 31 19:25:39 2023 +0200
Commit: Julien Nabet <serval2...@yahoo.fr>
CommitDate: Wed May 31 21:03:30 2023 +0200
Fix typo
Change-Id: I4b877a06c1fc09fa866c29dc39cb9478a50581b1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152459
Tested-by: Julien Nabet <serval2...@yahoo.fr>
Reviewed-by: Julien Nabet <serval2...@yahoo.fr>
diff --git a/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx
b/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx
index c73fa508fb60..86ac335907d7 100644
--- a/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx
+++ b/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx
@@ -2301,7 +2301,7 @@ void
VclMetafileProcessor2D::processTransparencePrimitive2D(
if (nullptr != pFiGradient &&
pFiGradient->getFillGradient().cannotBeHandledByVCL())
{
// If not, reset the pointer and do not make use of this special case.
- // Adding a gradient in incomplete state that canot be handled by vcl
+ // Adding a gradient in incomplete state that can not be handled by vcl
// makes no sense and will knowingly lead to errors, especially with
// MCGR extended possibilities. I checked what happens with the
// MetaFloatTransparentAction added by OutputDevice::DrawTransparent,
but
