Issue 105050: FreeType: don't use bitmap strikes when antialiasing

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 105050: FreeType: don't use bitmap strikes when antialiasing

Can't Edit
Can't Publish+Mail
Start Review

Created:
15 years, 2 months ago by agl

Modified:
15 years, 2 months ago

Reviewers:
reed

Visibility:
Public.

Description

FreeType: don't use bitmap strikes when antialiasing If the user requested anti-aliasing then we don't use bitmap strikes in the font. The consensus among our Japanese users is that this results in the best quality. http://code.google.com/p/chromium/issues/detail?id=18333

Patch Set 1 #

Created: 15 years, 2 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+7 lines, -0 lines)			Patch
	M	src/ports/SkFontHost_FreeType.cpp	View		1 chunk	+7 lines, -0 lines	0 comments	Download

Messages

Total messages: 2

Expand All Messages | Collapse All Messages

LGTM

Expand All Messages | Collapse All Messages