Bob Owen 72886c7966 Bug 1809657: Start next line break chunk from start of previous search when no breaks found. r=jfkthame ... This means that we start from a known non-break and that we shouldn't be in any danger of causing false breaks once Uniscribe gets to unprocessed characters. This also makes the crash tests manual and debug only. Manual because now that the win32k pref is default on and not dynamic the tests will not run on try any more. Debug only so that we don't include code in opt builds that is only for manual tests. Differential Revision: https://phabricator.services.mozilla.com/D167271		2023-01-20 13:12:06 +00:00
..
crashtests	Bug 1809657: Start next line break chunk from start of previous search when no breaks found. r=jfkthame	2023-01-20 13:12:06 +00:00
gtest
tools
jisx4051class.h
jisx4051pairtable.txt
LineBreaker.cpp
LineBreaker.h
moz.build
nsCarbonBreaker.cpp
nsComplexBreaker.cpp
nsComplexBreaker.h	Bug 1774865 - extra cleanup mozglue, security, intl and netwerk includes r=sylvestre	2022-06-22 09:51:52 +00:00
nsLWBrkCIID.h
nsPangoBreaker.cpp	Bug 1808182 - Use of uninitialised values originating from NS_GetComplexLineBreaks (in nsPangoBreaker.cpp). r=jfkthame.	2023-01-03 10:40:34 +00:00
nsRuleBreaker.cpp	Bug 1774865 - extra cleanup mozglue, security, intl and netwerk includes r=sylvestre	2022-06-22 09:51:52 +00:00
nsUniscribeBreaker.cpp	Bug 1809657: Start next line break chunk from start of previous search when no breaks found. r=jfkthame	2023-01-20 13:12:06 +00:00
rulebrk.c
rulebrk.h
Segmenter.cpp
Segmenter.h
th_char.h
WordBreaker.cpp
WordBreaker.h