[etoys-dev] Re: Etoys new fonts

Korakurider korakurider at gmail.com
Wed Jun 9 21:25:12 EDT 2010


On Wed, Jun 9, 2010 at 11:49 PM, Ricardo Moran <richi.moran at gmail.com> wrote:
> I see what the problem is. It seems TTFileDescription is not able to find
> the fonts because it looks in
>
> FileDirectory default directoryNamed: 'fonts'.
>
> and the default directory in the etoys-dev image is not the same
> directory where we put the image. If you move the fonts directory into the
> default directory, it works.
   Thanks, the problem resolved.
   I think raising more informative error would be great where there
is risk that user accidentally make change to environment and break
something.


 I noticed a couple of problems:
 1) project title in ToolBar corrupts
 2) string of icon of TextMorph in ToolBin and ObjectCatalog corrupts.
       The morph actually dragged from them still corrupts

I think I know the source of them;
Default font of TextMorph is VeraSans that is not for Japanese.
But traditionally we see Japanese string shown correctly even with
such settings because of fallback to "default (Japanese) font".  I
believe we still need such functionality.

> Should we change TTFileDescription to look for the fonts directory into
> "SmalltalkImage current imagePath" just move the fonts to the default
> directory?
   +1
   I am working on installers right now.  Please speak up if you want
to change layout of directories that Etoys runtime expects :-)



BTW, when the initialization (#installFamilyNamed:, etc) will be
executed, building time or changing locale?


/Korakurider

> I would prefer changing TTFileDescription because the default directory is
> more easily accesible by the users than the image directory and we do not
> want the fonts to get lost due to an user's mistake.
>
> Richo
>
> On Wed, Jun 9, 2010 at 10:46 AM, Ricardo Moran <richi.moran at gmail.com>
> wrote:
>>
>> Mmm... I think this may be related with my last commit. I tried to fix a
>> bug yesterday which caused an emergency evaluator to show up when changing
>> the locale to japanese or korean without initializing the fonts correctly.
>> Maybe I screwed up there...
>>
>> Anyway, I will try this again with a clean image. Updating still works,
>> right?
>>
>> Thanks for testing this!
>> Richo
>>
>> On Wed, Jun 9, 2010 at 4:07 AM, Korakurider <korakurider at gmail.com> wrote:
>>>
>>> On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran <richi.moran at gmail.com>
>>> wrote:
>>> > Hi, I managed to use the new fonts depending on the locale selected.
>>> > To test it, update your image, extract the new fonts into the fonts
>>> > directory (you can download them
>>> > from http://tecnodacta.com.ar/gira/gsoc/new-etoys-fonts.zip), execute:
>>> > TTFileDescription
>>> > installFamilyNamed: 'Mona';
>>> > installFamilyNamed: 'UnBatang';
>>> > installFamilyNamed: 'UnDotum';
>>> > installFamilyNamed: 'DejaVu LGC Sans';
>>> > installFamilyNamed: 'DejaVu LGC Serif';
>>> > installFamilyNamed: 'DejaVu LGC Sans Mono'.
>>> > and then execute:
>>> >
>>> > TTCFont registerAll.
>>> > latinFont := TTCFont familyName: 'DejaVu LGC Sans' pointSize: 15
>>> > emphasis:
>>> > 0.
>>> > japaneseFont := TTCFont familyName: 'Mona' pointSize: 15 emphasis: 0.
>>> > koreanFont := TTCFont familyName: 'UnDotum' pointSize: 16 emphasis: 0.
>>> > newFontArray := Array new: 14.
>>> > newFontArray at: 1 put: latinFont.
>>> > newFontArray at: 6 put: japaneseFont.
>>> > newFontArray at: 8 put: koreanFont.
>>> > newFontSet := TTCFontSet newFontArray: newFontArray.
>>> > TextStyle defaultFont fallbackFont: newFontSet.
>>> > Preferences standardEToysFont fallbackFont: newFontSet.
>>>
>>> I tried above but Etoys died with LowSpaceDebug.log (attached) after
>>> looong wait.
>>> I tested it on WinXP box with >2GB RAM.
>>> Does anyone have clue about this?
>>>
>>> /Korakurider
>>>
>>> > Now when you change your locale to japanese or korean it will use the
>>> > new
>>> > ttf files.
>>> > We should now decide which fonts to include for chinese, greek,
>>> > arabian,
>>> > russian, and so on.
>>> > Cheers
>>> > Richo
>>> >
>>> > On Fri, Jun 4, 2010 at 8:54 AM, Ricardo Moran <richi.moran at gmail.com>
>>> > wrote:
>>> >>
>>> >> Hi, I've been testing Andreas code with the DejaVu, Mona, UnDotum, and
>>> >> UnBatang fonts. You can install them by copying the .ttf files in the
>>> >> font
>>> >> directory and executing the following code (make sure you have an
>>> >> updated
>>> >> image):
>>> >> TTFileDescription
>>> >> installFamilyNamed: 'Mona';
>>> >> installFamilyNamed: 'UnBatang';
>>> >> installFamilyNamed: 'UnDotum';
>>> >> installFamilyNamed: 'DejaVu LGC Sans';
>>> >> installFamilyNamed: 'DejaVu LGC Serif';
>>> >> installFamilyNamed: 'DejaVu LGC Sans Mono'
>>> >> For convenience, I uploaded the fonts
>>> >> to http://tecnodacta.com.ar/gira/gsoc/new-etoys-fonts.zip. The size is
>>> >> 11.1
>>> >> MB.
>>> >> I haven't managed to link these fonts with the LanguageEnvironment (so
>>> >> that Mona would be the default font when you're using the japanese
>>> >> locale,
>>> >> or UnDotum for the korean) but I'm looking into that.
>>> >> Cheers
>>> >> Richo
>>> >
>>> > _______________________________________________
>>> > etoys-dev mailing list
>>> > etoys-dev at squeakland.org
>>> > http://lists.squeakland.org/mailman/listinfo/etoys-dev
>>> >
>>> >
>>
>
>


More information about the etoys-dev mailing list