2014-01-17 15:00:14 +00:00
|
|
|
# This is the official list of Skia authors for copyright purposes.
|
|
|
|
#
|
2014-01-24 12:39:25 +00:00
|
|
|
# Names should be added to this file with one of the following patterns:
|
|
|
|
#
|
|
|
|
# For individual contributors:
|
|
|
|
# Name <email address>
|
|
|
|
#
|
|
|
|
# For corporate contributors:
|
|
|
|
# Organization <fnmatch pattern>
|
|
|
|
# See examples below or python fnmatch module documentation for more information.
|
|
|
|
#
|
2014-01-17 15:00:14 +00:00
|
|
|
# Please keep the list sorted.
|
|
|
|
|
Drawing fake bold text, line and normal text made normal text bolder on PDF.
When PDF uses fake bold text, it uses stroke and fill for the
text. After that, line is drawn. It creates new ContextEntry which
GraphicStateEntry has 0 fTextScaleX. Since fTextScaleX is 0,
GraphicStackState::updateDrawingState() doesn't update text fill mode or
the PDF page. When the normal text is drawn, it reuse the line's
ContextEntry because GraphicStateEntry::compareInitialState() returns
true. However, since the reused GraphicsStateEntry's fTextScaleX is 0,
the text fill mode is not updated to fill, and the text is drawn in
stroke and fill mode.
When the fTextScaleX is changed, we should not reuse GraphicStateEntry
even if ether of fTextScaleX is 0.
BUG=skia:2132
R=reed@google.com, vandebo@chromium.org, bungeman@google.com
Author: yuki.sekiguchi@access-company.com
Review URL: https://codereview.chromium.org/137923005
git-svn-id: http://skia.googlecode.com/svn/trunk@13369 2bbb7eff-a529-9590-31e7-b0007b416f81
2014-02-07 19:39:57 +00:00
|
|
|
ACCESS CO., LTD. <*@access-company.com>
|
2014-01-24 12:39:25 +00:00
|
|
|
ARM <*@arm.com>
|
2014-02-14 00:03:38 +00:00
|
|
|
George Wright <george@mozilla.com>
|
2014-01-24 12:39:25 +00:00
|
|
|
Google Inc. <*@google.com>
|
|
|
|
Intel <*@intel.com>
|
|
|
|
NVIDIA <*@nvidia.com>
|
2014-03-01 20:12:26 +00:00
|
|
|
Samsung <*@samsung.com>
|
2014-01-31 19:12:43 +00:00
|
|
|
The Chromium Authors <*@chromium.org>
|
2014-01-17 15:00:14 +00:00
|
|
|
Thiago Fransosi Farina <thiago.farina@gmail.com>
|