diff options
| author | Andrea Gelmini <andrea.gelmini@gelma.net> | 2019-08-31 19:29:31 +0200 |
|---|---|---|
| committer | Julien Nabet <serval2412@yahoo.fr> | 2019-09-01 12:29:39 +0200 |
| commit | ee8f0a10661b747db9a82b9acba4de343a5a51d6 (patch) | |
| tree | ce9b6b2cf18caa73b8500245d558ff2ac484074d /i18npool/source/search | |
| parent | 0940229305247b4e64e8c85c9734020c9808a6ec (diff) | |
Fix '..'
To complete this:
https://gerrit.libreoffice.org/#/c/78312/
This is a massive replace for
".." instead of "..." between words.
It passed "make check" on Linux.
Change-Id: I144d8061fca9f545c762941551e59dffdd3650e8
Reviewed-on: https://gerrit.libreoffice.org/78357
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Tested-by: Jenkins
Diffstat (limited to 'i18npool/source/search')
| -rw-r--r-- | i18npool/source/search/levdis.hxx | 2 | ||||
| -rw-r--r-- | i18npool/source/search/textsearch.cxx | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/i18npool/source/search/levdis.hxx b/i18npool/source/search/levdis.hxx index fc7ed021dfa8..c789b7da8fb5 100644 --- a/i18npool/source/search/levdis.hxx +++ b/i18npool/source/search/levdis.hxx @@ -63,7 +63,7 @@ // One caveat, if the WLD reaches nLimit due to nDelR0 (i.e. data string is nZ // characters longer than pattern) then no character can be replaced any more. // This can be circumvented by increasing nX or/and nZ, but of course with the -// side effect of being less strict then.. or the other solution is to use +// side effect of being less strict then... or the other solution is to use // relaxed SplitCount (see below), which is the default when using CalcLPQR(). // // Attention: shorter = WLD.Insert, longer = WLD.Delete diff --git a/i18npool/source/search/textsearch.cxx b/i18npool/source/search/textsearch.cxx index f6f5fd3c618e..ea369329542e 100644 --- a/i18npool/source/search/textsearch.cxx +++ b/i18npool/source/search/textsearch.cxx @@ -867,7 +867,7 @@ void TextSearch::RESrchPrepare( const css::util::SearchOptions2& rOptions) // of the processor and the details of the specific pattern, but will // typically be on the order of milliseconds." // Just what is a good value? 42 is always an answer ... the 23 enigma - // as well.. which on the dev's machine is roughly 50 seconds with the + // as well... which on the dev's machine is roughly 50 seconds with the // pattern of fdo#70627. /* TODO: make this a configuration settable value and possibly take * complexity of expression into account and maybe even length of text |