On 10:33 Thu 23 Sep     , Bill Kendrick wrote:
> 
> Eep!  John, it looks like you included the smaller locale fonts right in
> Tux Paint.  I'm not sure this is wise. :)
> 
Sorry, bill I thought that was what we were talking about doing.
I look in the data/fonts dir and see nearly 2.5M of fonts, I've added
about 600K of additional fonts supporting 5 languages. It sounded like a
good trade-off to me.

> 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.
> 
Right, I see what you mean.

> 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?
It is since I re-worked it to build from the cvs directory, rather than
from a copy of cvs with lots of things moved and added-in, in an ad-hoc
manner :-)

Oh well :-) I was going to ask if we could move the starters, stamps and
new fonts folders into data directory, but I can see that that does fit
with the strategy of making flexible builds for lots of other platforms.

I guess I could enhance the python script to build a complete data
structure, and then test and build the installer from that.

Must dash, I will remove the fonts later, if you don't. Sorry about the
confusion at this end,

cheers,
John.


> 
> -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
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev

Reply via email to