mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typos

Browse Source 
Change-Id: I89ff5493c70d6e64ee6ab65b1b789a0db543c0aa
Reviewed-on: https://gerrit.libreoffice.org/84917
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Tested-by: Julien Nabet <serval2412@yahoo.fr>
This commit is contained in:
Andrea Gelmini
2019-12-11 09:03:07 +01:00
committed by Julien Nabet
parent 2e968bb29b
commit d87f6fd46d
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
filter/source/graphicfilter/icgm/class1.cxx
View File

@@ -60,7 +60,7 @@ void CGM::ImplDoClass1()
{
nUInteger = ImplGetUI16();
nI0 = ImplGetI( pElement->nIntegerPrecision ); // exponent
nI1 = ImplGetI( pElement->nIntegerPrecision ); // mantisse
nI1 = ImplGetI( pElement->nIntegerPrecision ); // mantissa
switch( nUInteger )
{
case 0 :

2
filter/source/graphicfilter/icgm/class3.cxx
View File

@@ -41,7 +41,7 @@ void CGM::ImplDoClass3()
{
nUInteger = ImplGetUI16();
const long nI0 = ImplGetI( pElement->nIntegerPrecision ); // exponent
const long nI1 = ImplGetI( pElement->nIntegerPrecision ); // mantisse
const long nI1 = ImplGetI( pElement->nIntegerPrecision ); // mantissa
switch( nUInteger )
{
case 0 :

2
svl/source/numbers/zformat.cxx
View File

@@ -2629,7 +2629,7 @@ bool SvNumberformat::ImpGetScientificOutput(double fNumber,
if ( nExPos >= 0 )
{
// split into mantisse and exponent and get rid of "E+" or "E-"
// split into mantissa and exponent and get rid of "E+" or "E-"
sal_Int32 nExpStart = nExPos + 1;
switch ( sStr[ nExpStart ] )

2
tools/source/generic/poly.cxx
View File

@@ -1730,7 +1730,7 @@ static void impCorrectContinuity(basegfx::B2DPolygon& roPolygon, sal_uInt32 nInd
// it needs to be corrected to be able to detect the continuity in this points
// correctly.
// We only have the integer data here (already in double precision form, but no mantisse
// We only have the integer data here (already in double precision form, but no mantissa
// used), so the best correction is to use:
// for C1: The longest vector since it potentially has best preserved the original vector.