[Title] Fix the parsing-logic used to collect the harfBuzzRuns
authorRashmi Shyamasundar <rashmi.s2@samsung.com>
Fri, 7 Jun 2013 06:03:25 +0000 (11:33 +0530)
committerRashmi Shyamasundar <rashmi.s2@samsung.com>
Fri, 7 Jun 2013 06:04:46 +0000 (11:34 +0530)
commit7fffdf202727ba502c4ab3e68db458eb3f0a64a4
tree68a7f2840ce150394bfa817ca683f3797dacc410
parentb35ab0c1a9200d22578d9315916df4a64a9e07f2
[Title] Fix the parsing-logic used to collect the harfBuzzRuns

[Issue#] N_SE36590

[Problem] Width of any word, containing a complex character after a space, is wrong.

[Cause] There should be one harfBuzzRun created for one word. In the case where the word starts with
        a complex character and there is a space before the word, the first glyph of the complex character
        becomes one harfBuzzRun and the rest of the word is another harfBuzzRun.
        The complex character is not reshaped as expected.

[Solution] Fix the parsing-logic used to collect the harfBuzzRuns, in function HarfBuzzShaper::collectHarfBuzzRuns.
           Update the value of "nextScript" in the for-loop, soon after consuming each character.

[Developer] rashmi.s2@samsung.com
Source/WTF/wtf/Platform.h
Source/WebCore/platform/graphics/harfbuzz/ng/HarfBuzzShaper.cpp