On Tue, Jan 6, 2009 at 12:57 PM, Paweł Hajdan Jr.
<[email protected]> wrote:
> I thought about bundling required fonts with the test_shell. I'm not
> sure about the licensing issues, but this would probably solve these
> technical problems. These fonts shouldn't change etc... What do you
> think?

All of the fonts but one that we depend on are in msttcorefonts, where
others have interpreted[1] the license to say that you may only
distribute the .exe files, not the .ttf files contained within them.
So I think we can't really distribute those.

I haven't looked into that one other font (Lucida?) but maybe we could
distribute that one -- on Ubuntu the package dependencies work out
such that installing the package that has that font pulls in some
enormous side thing like the java sdk.

Some other ideas:
 - always pull fonts from a resources directory within test_shell, and
require people to fix symlinks from that directory themselves (can we
check in symlinks in svn?)
 - use a fontconfig file rather than the hard-coded list of paths and
let people override it
 - use a command-line flag for the paths to search for fonts?  ugh, I
hope that's not the best option.

[1] http://corefonts.sourceforge.net/faq8.htm

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to