Rendering text-justify:distribute for 8 bit characters.

Source/core/platform/graphics/Font.h

 /*
  * Copyright (C) 2000 Lars Knoll (knoll@kde.org)
  *           (C) 2000 Antti Koivisto (koivisto@kde.org)
  *           (C) 2000 Dirk Mueller (mueller@kde.org)
  * Copyright (C) 2003, 2006, 2007, 2010, 2011 Apple Inc. All rights reserved.
  * Copyright (C) 2008 Holger Hans Peter Freyther
  *
  * This library is free software; you can redistribute it and/or
  * modify it under the terms of the GNU Library General Public
  * License as published by the Free Software Foundation; either
@@ skipping 138 matching lines @@
     }
 #if OS(MACOSX)
     const SimpleFontData* fontDataForCombiningCharacterSequence(const UChar*, size_t length, FontDataVariant) const;
 #endif
     std::pair<GlyphData, GlyphPage*> glyphDataAndPageForCharacter(UChar32, bool mirror, FontDataVariant = AutoVariant) const;
     bool primaryFontHasGlyphForCharacter(UChar32) const;
 
     static bool isCJKIdeograph(UChar32);
     static bool isCJKIdeographOrSymbol(UChar32);
 
-    static unsigned expansionOpportunityCount(const LChar*, size_t length, TextDirection, bool& isAfterExpansion);
-    static unsigned expansionOpportunityCount(const UChar*, size_t length, TextDirection, bool& isAfterExpansion);
+    static unsigned expansionOpportunityCount(const LChar*, size_t length, TextDirection, bool& isAfterExpansion, bool distributeJustification = false);
+    static unsigned expansionOpportunityCount(const UChar*, size_t length, TextDirection, bool& isAfterExpansion, bool distributeJustification = false);

[leviw_travelin_and_unemployed, 2013/11/04 19:37:58]

Should we ever call this without passing in a value for distributeJustification?
I see calls to expansionOpportunityCount() in ComplexTextController. Will this
be right?

[dw.im, 2013/11/05 10:26:10]

It seems ComplexTextController is only belong to mac port.

I think we need to handle the mac port as a seperate patch.
I cannot handle the mac port, so I will leave a FIXME in that file.

[leviw_travelin_and_unemployed, 2013/11/05 19:07:24]

Please add a complex text test case and we'll run it through the bots. I want an
example with Arabic to see how we handle connected characters. We'll definitely
need a FIXME and a tracking bug.

 
     static void setShouldUseSmoothing(bool);
     static bool shouldUseSmoothing();
 
     enum CodePath { Auto, Simple, Complex, SimpleWithGlyphOverflow };
     CodePath codePath(const TextRun&) const;
     static CodePath characterRangeCodePath(const LChar*, unsigned) { return Simple; }
     static CodePath characterRangeCodePath(const UChar*, unsigned len);
 
 private:
@@ skipping 162 matching lines @@
 
 namespace WTF {
 
 template <> struct OwnedPtrDeleter<WebCore::TextLayout> {
     static void deletePtr(WebCore::TextLayout*);
 };
 
 }
 
 #endif