| Age | Commit message (Collapse) | Author |
|---|
|
By default, the native API will be used instead of ICU, but if ICU is
forced in using configure, it will take precedence.
|
|
|
|
|
|
|
|
state left over from the previous (failed) layout attempt.
|
|
Uniscribe is sometimes producing different results compared to ICU, especially
when RTL and LTR content is mixed. Comparing the results to other programs
(like editors or web browsers) leads me to believe that the result are at least
not worse than ICU and possibly better.
|
|
instead of relying on overloads.
|
|
colours. (#6737)
This replaces the internal SCC_PREVIOUS_COLOUR swap.
|
|
|
|
ICU (lx) or the sorting/collation part of ICU (i18n)
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
|
|
glitches
|
|
line depends on the used layouter.
|
|
can use proper coding style for names again
|
|
-Fix [FS#5711]: crash when the ICU layouter thinks a font is corrupted
|
|
|
|
|
|
filtered out, but shown as ? when ICU was not used for layouting. These are included in chat and console messages to force them to be displayed right
|
|
|
|
90c920601c84975acb694f3673e2beb08b013753)
|
|
|
|
|
|
string.
|
|
|
|
members of Layouter and FontCache.
|
|
|
|
|
|
triggered the linebreak.
|
|
|
|
undefined execution order.
|
|
sometimes strings that needed to be broken off earlier got truncated later on
|
|
|
|
space after a newline
|
|
|
|
|
|
|
|
after eachother in a string, the latter isn't taken into account
|
|
|
|
|
|
|
