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
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.
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@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
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
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@gmail.com wrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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:
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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
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. Should we change TTFileDescription to look for the fonts directory into "SmalltalkImage current imagePath" just move the fonts to the default directory? 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@gmail.comwrote:
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@gmail.comwrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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:
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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
Yes, change it to Smalltalk imagePath.
This is used in various other places (like for locales, quickguides, etc.). We might want to add a "resourcePath" method somewhere. Not sure in which class to best put it though.
- Bert -
On 09.06.2010, at 16:49, Ricardo Moran 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. Should we change TTFileDescription to look for the fonts directory into "SmalltalkImage current imagePath" just move the fonts to the default directory? 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@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@gmail.com wrote: On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Wed, Jun 9, 2010 at 12:06 PM, Bert Freudenberg bert@freudenbergs.dewrote:
Yes, change it to Smalltalk imagePath.
This is used in various other places (like for locales, quickguides, etc.). We might want to add a "resourcePath" method somewhere. Not sure in which class to best put it though.
What if we add an "etoysPath" instead and we keep the default directory pointing to the image path?
Richo
- Bert -
On 09.06.2010, at 16:49, Ricardo Moran 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. Should we change TTFileDescription to look for the fonts directory into "SmalltalkImage current imagePath" just move the fonts to the default directory? 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@gmail.comwrote:
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@gmail.comwrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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:
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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Fri, Jun 11, 2010 at 10:19 AM, Ricardo Moran richi.moran@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:06 PM, Bert Freudenberg bert@freudenbergs.de wrote:
Yes, change it to Smalltalk imagePath. This is used in various other places (like for locales, quickguides, etc.). We might want to add a "resourcePath" method somewhere. Not sure in which class to best put it though.
What if we add an "etoysPath" instead and we keep the default directory pointing to the image path? Richo
Default directory could be dynamically changed by security plugin for sandboxing of user projects that was downloaded from somewhere and hasn't been "blessed". What is meaning and usage of etoysPath? To me API name resourcePath (=same as image path as default) seems clearer than "etoysPath" for locating various resources. <resourcePath>/QuickGuides <resourcePath>/fonts <resourcePath>/locale <resourcePath>/ExampleEtoys
/Korakurider
- Bert -
On 09.06.2010, at 16:49, Ricardo Moran 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. Should we change TTFileDescription to look for the fonts directory into "SmalltalkImage current imagePath" just move the fonts to the default directory? 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@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@gmail.com wrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Friday 11 Jun 2010 7:33:23 am Korakurider wrote:
To me API name resourcePath (=same as image path as default) seems clearer than "etoysPath" for locating various resources. <resourcePath>/QuickGuides <resourcePath>/fonts <resourcePath>/locale <resourcePath>/ExampleEtoys
Why not search in both paths for all resources instead of introducing yet another path variable? i.e.
<defaultDirectory>/fonts and then <imagePath>/fonts?
Subbu
On Fri, Jun 11, 2010 at 2:06 PM, K. K. Subramaniam kksubbu.ml@gmail.com wrote:
On Friday 11 Jun 2010 7:33:23 am Korakurider wrote:
To me API name resourcePath (=same as image path as default) seems clearer than "etoysPath" for locating various resources. <resourcePath>/QuickGuides <resourcePath>/fonts <resourcePath>/locale <resourcePath>/ExampleEtoys
Why not search in both paths for all resources instead of introducing yet another path variable? i.e.
<defaultDirectory>/fonts and then <imagePath>/fonts?
IIUC resourcePath is actually just alias of imagePath as Etoys installer assume such structure.
Locating resources in search list is completely different topic. Those resources are usually installed by Etoys installer. So I think locating them only in resourcePath would be sufficient. Does user really want to place them in default directory (i.e. %MyDocuments%\Etoys on Windows environment for an example)?
/Korakurider
Subbu
On Fri, Jun 11, 2010 at 2:06 PM, K. K. Subramaniam kksubbu.ml@gmail.com wrote:
On Friday 11 Jun 2010 7:33:23 am Korakurider wrote:
To me API name resourcePath (=same as image path as default) seems clearer than "etoysPath" for locating various resources. <resourcePath>/QuickGuides <resourcePath>/fonts <resourcePath>/locale <resourcePath>/ExampleEtoys
Why not search in both paths for all resources instead of introducing yet another path variable? i.e.
<defaultDirectory>/fonts and then <imagePath>/fonts?
IIUC resourcePath is actually just alias of imagePath as Etoys installer assume such structure.
Locating resources in search list is completely different topic. Those resources are usually installed by Etoys installer. So I think locating them only in resourcePath would be sufficient. Does user really want to place them in default directory (i.e. %MyDocuments%\Etoys on Windows environment for an example)?
/Korakurider
Subbu
Please correct me if I'm wrong. What I mean is: currently Etoys uses the default directory to store project files and so it changes the default directory to point to a different place than the imagePath. But the default directory is used for a lot of other stuff (saving the image with "save as...", looking for fonts, monticello's package cache, writing logs, and so on). Maybe we could keep the default directory pointing to the image path (as the squeak trunk image) and simply change the directory where we store the project files. This directory would be "etoysPath" (or any other name you consider better). So, what I propose is, instead of making a "resourcePath" for locales, quickguides, fonts, etc. we create an "etoysPath" only for storing projects and we change the default directory back to the image path.
Cheers. Richo
On Thu, Jun 10, 2010 at 11:03 PM, Korakurider korakurider@gmail.com wrote:
On Fri, Jun 11, 2010 at 10:19 AM, Ricardo Moran richi.moran@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:06 PM, Bert Freudenberg bert@freudenbergs.de wrote:
Yes, change it to Smalltalk imagePath. This is used in various other places (like for locales, quickguides, etc.). We might want to add a "resourcePath" method somewhere. Not sure
in
which class to best put it though.
What if we add an "etoysPath" instead and we keep the default directory pointing to the image path? Richo
Default directory could be dynamically changed by security plugin for sandboxing of user projects that was downloaded from somewhere and hasn't been "blessed". What is meaning and usage of etoysPath? To me API name resourcePath (=same as image path as default) seems clearer than "etoysPath" for locating various resources. <resourcePath>/QuickGuides <resourcePath>/fonts <resourcePath>/locale <resourcePath>/ExampleEtoys
/Korakurider
- Bert -
On 09.06.2010, at 16:49, Ricardo Moran 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. Should we change TTFileDescription to look for the fonts directory into "SmalltalkImage current imagePath" just move the fonts to the default directory? 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@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@gmail.com wrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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:
koreanFont := TTCFont familyName: 'UnDotum' pointSize: 16 emphasis:
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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
At Fri, 11 Jun 2010 14:57:32 -0300, Ricardo Moran wrote:
Please correct me if I'm wrong. What I mean is: currently Etoys uses the default directory to store project files and so it changes the default directory to point to a different place than the imagePath. But the default directory is used for a lot of other stuff (saving the image with "save as...", looking for fonts, monticello's package cache, writing logs, and so on). Maybe we could keep the default directory pointing to the image path (as the squeak trunk image) and simply change the directory where we store the project files. This directory would be "etoysPath" (or any other name you consider better). So, what I propose is, instead of making a "resourcePath" for locales, quickguides, fonts, etc. we create an "etoysPath" only for storing projects and we change the default directory back to the image path.
One thing is that Etoys needs more strict readonly vs. read-write permission distinction of files and directories than a typical trunk installation, as somebody can make a malicious project and upload it to a server and mess up the writable directory. So, in general the fonts should be in the read-only directory. (It has never been a problem so far, and seraching two places like Subbu suggested would have the advantage of allowing downloadable fonts, but less secure.)
I am pretty sure that you are not proposing to add a new directory that SecurityPlugin knows. (A new directory accessing method that returns already-known directory name.) But I am not still sure if what you proposes simplifies the problem...
(I am not really closely following the discussion so forgive me if I'm missing something.)
-- Yoshiki
On 11.06.2010, at 20:48, Yoshiki Ohshima wrote:
At Fri, 11 Jun 2010 14:57:32 -0300, Ricardo Moran wrote:
Please correct me if I'm wrong. What I mean is: currently Etoys uses the default directory to store project files and so it changes the default directory to point to a different place than the imagePath.
Not quite. It changes the default directory to the only guaranteed writeable directory. Everything else becomes inaccessible once the security sandbox is enabled (which happens when you run someone else's project). The only exception is the resource directory, which is still accessible, but read-only. In the Etoys case, we chose that resource directory to be the image directory. I was simply suggesting that for better clarity we use "resource directory" in the code, rather than "image directory".
But the default directory is used for a lot of other stuff (saving the image with "save as...", looking for fonts, monticello's package cache, writing logs, and so on).
Right, except for loading fonts. Those need to be looked up in the resource directory for the fonts we ship, and possibly also in the default directory for user-installed fonts (but I'd hope that in normal operation we do not need that font download anymore).
Maybe we could keep the default directory pointing to the image path (as the squeak trunk image) and simply change the directory where we store the project files. This directory would be "etoysPath" (or any other name you consider better). So, what I propose is, instead of making a "resourcePath" for locales, quickguides, fonts, etc. we create an "etoysPath" only for storing projects and we change the default directory back to the image path.
Not a good idea.
A lot of code assumes (rightly) that the default directory is writable. When the security sandbox is enabled, we only have a single writable directory. We definitely need to write projects. Hence, the project directory must be the default directory.
One thing is that Etoys needs more strict readonly vs. read-write permission distinction of files and directories than a typical trunk installation, as somebody can make a malicious project and upload it to a server and mess up the writable directory. So, in general the fonts should be in the read-only directory. (It has never been a problem so far, and seraching two places like Subbu suggested would have the advantage of allowing downloadable fonts, but less secure.)
I am pretty sure that you are not proposing to add a new directory that SecurityPlugin knows. (A new directory accessing method that returns already-known directory name.) But I am not still sure if what you proposes simplifies the problem...
(I am not really closely following the discussion so forgive me if I'm missing something.)
Yoshiki is right. You need to take the security sandboxing into account.
- Bert -
Ohhh, ok, I didn't consider the security issues. Please forget what I said :)
Richo
On Fri, Jun 11, 2010 at 5:12 PM, Bert Freudenberg bert@freudenbergs.dewrote:
On 11.06.2010, at 20:48, Yoshiki Ohshima wrote:
At Fri, 11 Jun 2010 14:57:32 -0300, Ricardo Moran wrote:
Please correct me if I'm wrong. What I mean is: currently Etoys uses the
default directory to store project files and so
it changes the default directory to point to a different place than the
imagePath.
Not quite. It changes the default directory to the only guaranteed writeable directory. Everything else becomes inaccessible once the security sandbox is enabled (which happens when you run someone else's project). The only exception is the resource directory, which is still accessible, but read-only. In the Etoys case, we chose that resource directory to be the image directory. I was simply suggesting that for better clarity we use "resource directory" in the code, rather than "image directory".
But the default directory is used for a lot of other stuff (saving the image with "save as...", looking for
fonts, monticello's package cache, writing logs,
and so on).
Right, except for loading fonts. Those need to be looked up in the resource directory for the fonts we ship, and possibly also in the default directory for user-installed fonts (but I'd hope that in normal operation we do not need that font download anymore).
Maybe we could keep the default directory pointing to the image path (as
the squeak trunk image) and simply
change the directory where we store the project files. This directory
would be "etoysPath" (or any other name you
consider better). So, what I propose is, instead of making a "resourcePath" for locales,
quickguides, fonts, etc. we create an "etoysPath"
only for storing projects and we change the default directory back to the image path.
Not a good idea.
A lot of code assumes (rightly) that the default directory is writable. When the security sandbox is enabled, we only have a single writable directory. We definitely need to write projects. Hence, the project directory must be the default directory.
One thing is that Etoys needs more strict readonly vs. read-write permission distinction of files and directories than a typical trunk installation, as somebody can make a malicious project and upload it to a server and mess up the writable directory. So, in general the fonts should be in the read-only directory. (It has never been a problem so far, and seraching two places like Subbu suggested would have the advantage of allowing downloadable fonts, but less secure.)
I am pretty sure that you are not proposing to add a new directory that SecurityPlugin knows. (A new directory accessing method that returns already-known directory name.) But I am not still sure if what you proposes simplifies the problem...
(I am not really closely following the discussion so forgive me if I'm missing something.)
Yoshiki is right. You need to take the security sandboxing into account.
- Bert -
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Saturday 12 Jun 2010 1:42:04 am Bert Freudenberg wrote:
I was simply suggesting that for better clarity we use "resource directory" in the code, rather than "image directory".
+1 and introduce userRepository or toysRepository instead of defaultDirectory. The current names are misleading.
Right, except for loading fonts. Those need to be looked up in the resource directory for the fonts we ship, and possibly also in the default directory for user-installed fonts (but I'd hope that in normal operation we do not need that font download anymore).
fonts are just one type of such resource. I could think of images, audio, video clips (referenced in guides for instance). Not all audio clips need to loaded into an image (e.g. cultural variations of meow sounds for instance).
A lot of code assumes (rightly) that the default directory is writable. When the security sandbox is enabled, we only have a single writable directory.
why only one directory (writable+persistent)? When I wrote LatexMorph, I also needed writable+volatile for converting LaTeX code to images quickly on the fly. I didn't want persistent directory because of higher i/o latencies, power drain and/or wear-n-tear risks. Do you see any increased security issues with two repos?
I expect similar situations in code involving dynamic font operations, multimedia codec or inter-process communications. Anyone?
Subbu
On 12.06.2010, at 10:09, K. K. Subramaniam wrote:
On Saturday 12 Jun 2010 1:42:04 am Bert Freudenberg wrote:
I was simply suggesting that for better clarity we use "resource directory" in the code, rather than "image directory".
+1 and introduce userRepository or toysRepository instead of defaultDirectory. The current names are misleading.
I do not think this would add clarity. By default, stuff goes to the default directory. Seems clear enough to me.
A lot of code assumes (rightly) that the default directory is writable. When the security sandbox is enabled, we only have a single writable directory.
why only one directory (writable+persistent)?
Simplicity.
When I wrote LatexMorph, I also needed writable+volatile for converting LaTeX code to images quickly on the fly. I didn't want persistent directory because of higher i/o latencies, power drain and/or wear-n-tear risks. Do you see any increased security issues with two repos?
I expect similar situations in code involving dynamic font operations, multimedia codec or inter-process communications. Anyone?
We would have to change the SecurityPlugin on all platforms. I see little benefit to Etoys, but hypothetically, which directories would you like this "volatile" directory to be, on each of our supported platforms?
- Bert -
On Wed, Jun 9, 2010 at 11:49 PM, Ricardo Moran richi.moran@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@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@gmail.com wrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Wed, Jun 9, 2010 at 10:25 PM, Korakurider korakurider@gmail.com wrote:
I noticed a couple of problems:
- project title in ToolBar corrupts
- 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.
Thanks for finding these issues. I believe you're right, and I think we should make one set of fallback fonts and all the fonts in the image should point to that set. I only changed the "defaultFont" and the "standardEToysFont" because I thought it would be enough, but I guess I was wrong.
BTW, when the initialization (#installFamilyNamed:, etc) will be executed, building time or changing locale?
I think it would be building time.
Richo
/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@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@gmail.com
wrote:
On Wed, Jun 9, 2010 at 1:40 AM, Ricardo Moran richi.moran@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:
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@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@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
K. K. Subramaniam -
Korakurider -
Ricardo Moran -
Yoshiki Ohshima