summaryrefslogtreecommitdiffstats
path: root/chrome/installer/mini_installer.gyp
diff options
context:
space:
mode:
authorkochi@google.com <kochi@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2012-02-08 06:35:44 +0000
committerkochi@google.com <kochi@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2012-02-08 06:35:44 +0000
commit1f9a6d1bbb415d8ebd7403ddb41534441a4a6b0d (patch)
tree0f2eea380a486abbb0b04c129328651a5963033f /chrome/installer/mini_installer.gyp
parent11d676bb608acbaedd009f578bbf4d7990cbc1e7 (diff)
downloadchromium_src-1f9a6d1bbb415d8ebd7403ddb41534441a4a6b0d.zip
chromium_src-1f9a6d1bbb415d8ebd7403ddb41534441a4a6b0d.tar.gz
chromium_src-1f9a6d1bbb415d8ebd7403ddb41534441a4a6b0d.tar.bz2
Revert 120926 - Intoroducing Motoya font for ChromeOS
We will introduce Motoya fonts (MotoyaG04Gothic, MotoyaG04Mincho) as the default Japanese font for ChromeOS. This CL is for preparing resource to define default font and Skia to check the font family is compatible with their counterparts of MS Windows fonts. Note that GTK font specification in the resource does not handle multiple fonts (e.g. "MotoyaG04Gothic 10, IPAPGothic 10") and I left it as is (see crosbug.com/17382 for details). Fontconfig should cover the compatibility check (IPAPGothic => MotoyaG04Gothic) and display the proper font. BUG=chromium-os:16690 TEST=build, run and see Japanese fonts are properly displayed in both web contents and Chrome UI. Review URL: http://codereview.chromium.org/9309048 TBR=kochi@chromium.org Review URL: https://chromiumcodereview.appspot.com/9363017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120949 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/installer/mini_installer.gyp')
0 files changed, 0 insertions, 0 deletions