Hi,
I have submitted a patch for review:
https://gerrit.libreoffice.org/3267
To pull it, you can do:
git pull ssh://gerrit.libreoffice.org:29418/core refs/changes/67/3267/1
delete commented code
Change-Id: Ia144e7b6e567d39816a4baa68187c157f7d8776e
---
M sw/source/core/text/pormulti.cxx
1 file changed, 0 insertions(+), 16 deletions(-)
diff --git a/sw/source/core/text/pormulti.cxx b/sw/source/core/text/pormulti.cxx
index 18951c5..a375f34f 100644
--- a/sw/source/core/text/pormulti.cxx
+++ b/sw/source/core/text/pormulti.cxx
@@ -888,22 +888,6 @@
if ( CH_TXTATR_BREAKWORD == GetChar( rPos ) )
{
bFldBidi = true;
-/*
- // examining the script of the field text should be sufficient
- // for 99% of all cases
- XubString aTxt = GetTxtFrm()->GetTxtNode()->GetExpandTxt( rPos, 1 );
-
- if ( pBreakIt->GetBreakIter().is() && aTxt.Len() )
- {
- bool bFldDir = ( i18n::ScriptType::COMPLEX ==
- pBreakIt->GetRealScriptOfText( aTxt, 0 ) );
- bool bCurrDir = ( 0 != ( nCurrLevel % 2 ) );
- if ( bFldDir != bCurrDir )
- {
- nNextLevel = nCurrLevel + 1;
- bFldBidi = true;
- }
- }*/
}
else
nNextLevel = rSI.DirType( rPos );
--
To view, visit https://gerrit.libreoffice.org/3267
To unsubscribe, visit https://gerrit.libreoffice.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: Ia144e7b6e567d39816a4baa68187c157f7d8776e
Gerrit-PatchSet: 1
Gerrit-Project: core
Gerrit-Branch: master
Gerrit-Owner: Christina Roßmanith <ChrRossmanith@web.de>
Context
- [PATCH] delete commented code · via Code Review
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.