Eep! John, it looks like you included the smaller locale fonts right in
Tux Paint. I'm not sure this is wise. :)
Linux packagers, for example, might prefer to simply create symlinks to
existing TTFs in their distribution, rather than have duplicate TTF files
floating around.
What I was thinking you'd do is simply include a few of the 'locale' TTF
fonts when creating the Windows installer/ZIP releases.
e.g.:
CVS:
tuxpaint -----------------> {
tuxpaint-config ----------> {
{ tuxpaint 0.9.14
FTP: { for windows
hebrew font ---------------> {
greek font ----------------> {
[other fonts]
CVS:
tuxpaint-stamps -----------> { tux paint stamps for windows
FTP:
japanese font -------------> { japanese font for windows
chinese simplified font ---> { chinese simp. font for windows
And Ben would do this something like this for Debian:
CVS:
tuxpaint ----------------> { tuxpaint.deb
tuxpaint-stamps ---------> { tuxpaint-stamps.deb
tuxpaint-config ---------> { tuxpaint-config.deb
FTP:
hebrew font -------------> { N/A (simply depend on an already-packaged
{ Hewbrew TTF from Debian, and make
{ 'tuxpaint-hewbrew.deb' a dummy pkg
{ that symlinks Tux Paint 'el.ttf' to it
[other fonts] ( ditto )
Make sense? Is the above Win32 'path' do-able easily with NIS?
-bill!
[EMAIL PROTECTED] New Breed Software
http://www.newbreedsoftware.com/ Tux Paint 0.9.14 -- Coming soon!
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
