Static documentation for Font Settings Extension API.

Static documentation for Font Settings Extension API.

BUG=114148
TEST=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=129594

[falken, 2012-03-28 06:58:26]

+jungshik, in case you have feedback

[Matt Perry, 2012-03-28 18:26:56]

lgtm

[jungshik at Google, 2012-03-28 20:09:45]

LGTM

http://codereview.chromium.org/9784014/diff/1/chrome/common/extensions/docs/e...
File chrome/common/extensions/docs/experimental.fontSettings.html (right):

http://codereview.chromium.org/9784014/diff/1/chrome/common/extensions/docs/e...
chrome/common/extensions/docs/experimental.fontSettings.html:293: {
genericFamily: 'sansserif', script: 'Hrkt', fontName: 'IPAPGothic' }
This is not a documentation issue but the API implementation issue. In Webkit,
we'd have used 'Japn' if ICU on earlier version of Mac OS has 'Japn' script
available. Using 'Hrkt' for Japanese may not be very user-friendly (well, not
many extensions will be written with this api so that it may not matter
terribly). 

Still, Japn would be better. For now, how about explaining a bit as to why Hrkt
is used here for Japanese?

Later, we may want to change the API to translate Japn to Hrkt before talking to
WebCore. That way, we expose a more user-friendly 'Japn' to extension writers
without changing WebCore. 

The same can be said of Kore vs Hang. However, Hang is  almost as good a Kore so
that we can leave that alone.

[falken, 2012-03-29 06:58:22]

http://codereview.chromium.org/9784014/diff/1/chrome/common/extensions/docs/e...
File chrome/common/extensions/docs/experimental.fontSettings.html (right):

http://codereview.chromium.org/9784014/diff/1/chrome/common/extensions/docs/e...
chrome/common/extensions/docs/experimental.fontSettings.html:293: {
genericFamily: 'sansserif', script: 'Hrkt', fontName: 'IPAPGothic' }
On 2012/03/28 20:09:45, Jungshik Shin wrote:
> This is not a documentation issue but the API implementation issue. In Webkit,
> we'd have used 'Japn' if ICU on earlier version of Mac OS has 'Japn' script
> available. Using 'Hrkt' for Japanese may not be very user-friendly (well, not
> many extensions will be written with this api so that it may not matter
> terribly). 
> 
> Still, Japn would be better. For now, how about explaining a bit as to why
Hrkt
> is used here for Japanese?
> 
> Later, we may want to change the API to translate Japn to Hrkt before talking
to
> WebCore. That way, we expose a more user-friendly 'Japn' to extension writers
> without changing WebCore. 
> 
> The same can be said of Kore vs Hang. However, Hang is  almost as good a Kore
so
> that we can leave that alone. 

Thanks, good idea. I added a little explanation to the previous section about
language scripts.

[commit-bot: I haz the power, 2012-03-29 06:58:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/falken@chromium.org/9784014/5001

[commit-bot: I haz the power, 2012-03-29 08:45:05]

Change committed as 129594