Kaydet (Commit) 0143e976 authored tarafından Andrea Gelmini's avatar Andrea Gelmini Kaydeden (comit) Julien Nabet

Fix typos

Change-Id: Ic7a29f572ce4c42cc88e5d45ebbb774c4b21aaa0
Reviewed-on: https://gerrit.libreoffice.org/63488
Tested-by: Jenkins
Reviewed-by: 's avatarJulien Nabet <serval2412@yahoo.fr>
üst b12acadf
......@@ -567,7 +567,7 @@ void SAL_CALL OPreparedStatement::setClob(sal_Int32 nParameterIndex, const Refer
break;
}
// We need to make sure we close the Blob even if their are errors, hence evaluate
// We need to make sure we close the Blob even if there are errors, hence evaluate
// errors after closing.
closeBlobAfterWriting(aBlobHandle);
......@@ -605,7 +605,7 @@ void OPreparedStatement::setClob( sal_Int32 nParameterIndex, const OUString& rSt
sData.getLength(),
sData.getStr() );
// We need to make sure we close the Blob even if their are errors, hence evaluate
// We need to make sure we close the Blob even if there are errors, hence evaluate
// errors after closing.
closeBlobAfterWriting(aBlobHandle);
......@@ -657,7 +657,7 @@ void SAL_CALL OPreparedStatement::setBlob(sal_Int32 nParameterIndex,
}
}
// We need to make sure we close the Blob even if their are errors, hence evaluate
// We need to make sure we close the Blob even if there are errors, hence evaluate
// errors after closing.
closeBlobAfterWriting(aBlobHandle);
......@@ -824,7 +824,7 @@ void SAL_CALL OPreparedStatement::setBytes(sal_Int32 nParameterIndex,
}
}
// We need to make sure we close the Blob even if their are errors, hence evaluate
// We need to make sure we close the Blob even if there are errors, hence evaluate
// errors after closing.
closeBlobAfterWriting(aBlobHandle);
......
......@@ -737,7 +737,7 @@ private:
Note further: it patches the info struct
more than ones. E.g. the new temp URL is set
before the file is saved. And the old URL is removed
only if removing oft he old file was successfully.
only if removing of the old file was successfully.
If this method returns without an exception - everything
was OK. Otherwise the info struct can be analyzed to
get more information, e.g. when the problem occurs.
......
......@@ -463,7 +463,7 @@ void SdImportTestSmartArt::testAccentProcess()
CPPUNIT_ASSERT(xGroupShape.is());
// The pair is a parent (shape + text) and a child, so 3 shapes in total.
// The order is importent, first is at the back, last is at the front.
// The order is important, first is at the back, last is at the front.
uno::Reference<drawing::XShapes> xFirstPair(xGroup->getByIndex(0), uno::UNO_QUERY);
CPPUNIT_ASSERT(xFirstPair.is());
CPPUNIT_ASSERT_EQUAL(static_cast<sal_Int32>(3), xFirstPair->getCount());
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment