| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 5094208 - Browser does not handle Japanese text in vertical writing mode.
This changeset syncs up with Chrome's implementation for vertical text rendering. It
1. Adds fontOrientation and textOrientation to FontPlatformData.
2. Rotates the text in drawGlyphs for vertical writing mode.
Here are the changesets for Chrome's vertical writinig mode support:
1. http://trac.webkit.org/changeset/74232
2. http://trac.webkit.org/changeset/80610
3. http://trac.webkit.org/changeset/80654
This CL re-applies reverted CL136684(https://android-git.corp.google.com/g/#/c/136684/).
CL136684 was rollbacked because 2 constructors in FontPlatformDataAndroid.cpp
did not have the init for fontOrientation and textOrientation. That caused the
inconsistent comparison while FontCache.cpp tries to get the cached font and
falls into an infinite loop in HashTable.h:656
Change-Id: I45700dcc8c9266e1b5ae8e588205f24825ca4317
|
|
|
| |
This reverts commit 5403113c5aa5d55a05ea001f562829e907632178
|
|
|
|
|
|
|
|
|
| |
Bug 5094208 - Browser does not handle Japanese text in vertical writing mode.
This changeset syncs up with Chrome's implementation for vertical text rendering. It
1. Adds fontOrientation and textOrientation to FontPlatformData.
2. Re-layout the text in drawGlyphs for vertical writing mode.
Change-Id: Icac88a464b4b25b05c758a4e24c1827e0a7a0c91
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When Skia resorts to fallback fonts for non-latin characters, it
retains the font ID of originally requested font, concealing the
fact that a fallback was invoked. Harfbuzz needs to know the fallback
font ID to read the correct GSUB/GPOS tables from the fallback font
file so that these complex languages can be properly rendered.
This change uses the script recognized by Harfbuzz as a means to
surmise the fallback font that would be used by Skia and then injects
that font file as a replacement for the originally requested font.
Fallback fonts are loaded once and reused multiple times. An earlier
implementation did not cache fonts in this way, causing large pages
to run out of files for mmap streaming.
Bug: 5087744
Change-Id: I61222829209d9bd6df465d37923ccff3681c2c54
|
|
|
|
|
|
|
|
|
|
| |
On large pages, too many font file references are open for mmap
streaming. Rolling back this feature while I add caching.
This reverts commit cfcbe02678eabf19b6b904be61d9991d4515ecb6.
Bug: 5179817
Change-Id: I689db7794c945d548a90006b9484467b784d4b11
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When Skia resorts to fallback fonts for non-latin characters, it
retains the font ID of originally requested font, concealing the
fact that a fallback was invoked. Harfbuzz needs to know the fallback
font ID to read the correct GSUB/GPOS tables from the fallback font
file so that these complex languages can be properly rendered.
This change uses the script recognized by Harfbuzz as a means to
surmise the fallback font that would be used by Skia and then injects
that font file as a replacement for the originally requested font.
Bug: 5087744
Change-Id: I3a3469bcd589ee796c9b5a828fb47d40ecb38738
|
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/80582 and
http://trac.webkit.org/changeset/80589
Change-Id: I77941a880d7bb8347efcf6969a378ed941fce0e6
|
|
|
|
|
|
|
|
|
| |
This will become relevant after we merge beyond
http://trac.webkit.org/changeset/81977 (and its follow-up build fixes
r81982, r81988, r81990, r82018) which relies on all platforms'
instances of FontPlatformData.h using the correct include guard.
Change-Id: I58ec4c8ee23698c41d86794333d603b95f303764
|
|
This moves files in the following WebCore subdirectories ...
- bindings/js
- bindings/v8/custom
- plugins/android
- platform/android
- platform/graphics/android
- page/
- css/
- dom/
- loader/archive/android
|