On 4/13/06, <b class="gmail_sendername">n0dalus</b> <<a href="mailto:n0dalus+wine@gmail.com">n0dalus+wine@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Maybe this is a stupid question, but why can't we just distribute the<br>ttf files directly?</blockquote><div><br>Because we're masochists and prefer to build tools.<br><br>It's definitely the simple solution and we're capable of doing that. There used to be issues with having binary files in CVS, but I'm not sure that's as big of a problem. However, as a general rule of thumb the source code releases are just that - source code. The proper solution is to distribute the .sfd files and compile them during the build process. It's the same reason we don't include .bmp or .avi files; we have tools to build them from the resource files. The goal here is to take the functionality in fontforge and trim it down to the bare minimum of what we need.
<br><br>-Brian<br> </div><br></div>