On Fri, Dec 17, 2010 at 4:50 PM, Stanislav Paskalev <[hidden email]> wrote: Hi, Maybe we should report this to Eliot? cheers mariano Best regards, |
On 19 December 2010 23:02, Mariano Martinez Peck <[hidden email]> wrote: > > > > On Fri, Dec 17, 2010 at 4:50 PM, Stanislav Paskalev <[hidden email]> wrote: >> >> Hi, >> I also have to write in cyrilic in pharo 1.1 / 1.1.1 and it works. >> >> You have to first update the fonts from system and then set new, >> unicode enabled fonts on all the elements. Updating the fonts just >> adds them to a list of known fonts, it doesn't make the image to use >> them in other words. >> Also, with the latest build (4 oct) of CogVM, updating fonts from >> system does not work on any system (win,mac,linux) - so use the >> standart VM. >> > > Maybe we should report this to Eliot? This is because Cog does not including freetype plugin. This is why i worked on it during last couple of days, and i managed to get a Cog VM which reacting adequately on 'update fonts' on mac :) > > cheers > > mariano > > >> >> Best regards, >> Stanislav Paskalev >> >> >> >> On Fri, Dec 17, 2010 at 5:45 PM, qpogo <[hidden email]> wrote: >> > Hi all, I'm a real newbie in Pharo and Smalltalk. I want to type in Cyrillic >> > and Hebrew. However I get question marks. I tried to change fonts, but I >> > have only to available fonts: * Accuny * Bitmap DejaVu Sans Which don't have >> > Unicode glyphs. When I try to update fonts from the system, I don't see any >> > result. Thank you. Alex >> > ________________________________ >> > View this message in context: Unicode in Pharo1.1 >> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >> > > > -- Best regards, Igor Stasenko AKA sig. |
> You have to first update the fonts from system and then set new, >>> unicode enabled fonts on all the elements. Updating the fonts just >>> adds them to a list of known fonts, it doesn't make the image to use >>> them in other words. >>> Also, with the latest build (4 oct) of CogVM, updating fonts from >>> system does not work on any system (win,mac,linux) - so use the >>> standart VM. >>> >> >> Maybe we should report this to Eliot? > > This is because Cog does not including freetype plugin. > This is why i worked on it during last couple of days, and i managed > to get a Cog VM which reacting adequately on 'update fonts' on mac :) igor, you can also say that this is based on money we received for pharo :) Stef |
On 20 December 2010 09:22, stephane ducasse <[hidden email]> wrote: > >> You have to first update the fonts from system and then set new, >>>> unicode enabled fonts on all the elements. Updating the fonts just >>>> adds them to a list of known fonts, it doesn't make the image to use >>>> them in other words. >>>> Also, with the latest build (4 oct) of CogVM, updating fonts from >>>> system does not work on any system (win,mac,linux) - so use the >>>> standart VM. >>>> >>> >>> Maybe we should report this to Eliot? >> >> This is because Cog does not including freetype plugin. >> This is why i worked on it during last couple of days, and i managed >> to get a Cog VM which reacting adequately on 'update fonts' on mac :) > > igor, you can also say that this is based on money we received for pharo :) > > of course Stef, of course. But i think everyone aware of it, so i don't need to repeat this every time :) Btw, let us make clear one little thing: I am right to say, that our development model remains the same, i.e. all things we produce under/for Pharo, become available as soon as possible to public? Because once you got money, there is someone who could say 'do not publish those, before i allow you to do so'. > Stef > > -- Best regards, Igor Stasenko AKA sig. |
On 20.12.2010 09:48, Igor Stasenko wrote: > > On 20 December 2010 09:22, stephane ducasse<[hidden email]> wrote: >>> You have to first update the fonts from system and then set new, >>>>> unicode enabled fonts on all the elements. Updating the fonts just >>>>> adds them to a list of known fonts, it doesn't make the image to use >>>>> them in other words. >>>>> Also, with the latest build (4 oct) of CogVM, updating fonts from >>>>> system does not work on any system (win,mac,linux) - so use the >>>>> standart VM. >>>>> >>>> Maybe we should report this to Eliot? >>> This is because Cog does not including freetype plugin. >>> This is why i worked on it during last couple of days, and i managed >>> to get a Cog VM which reacting adequately on 'update fonts' on mac :) >> resources folder of a Cog-VM on Mac works just fine, so that's a work around for those who need it before it's buildable directly by Cog. (at least on Mac, I haven't tested on other platforms) Cheers, Henry |
On 20 December 2010 11:14, Henrik Sperre Johansen <[hidden email]> wrote: > > On 20.12.2010 09:48, Igor Stasenko wrote: >> >> On 20 December 2010 09:22, stephane ducasse<[hidden email]> >> wrote: >>>> >>>> You have to first update the fonts from system and then set new, >>>>>> >>>>>> unicode enabled fonts on all the elements. Updating the fonts just >>>>>> adds them to a list of known fonts, it doesn't make the image to use >>>>>> them in other words. >>>>>> Also, with the latest build (4 oct) of CogVM, updating fonts from >>>>>> system does not work on any system (win,mac,linux) - so use the >>>>>> standart VM. >>>>>> >>>>> Maybe we should report this to Eliot? >>>> >>>> This is because Cog does not including freetype plugin. >>>> This is why i worked on it during last couple of days, and i managed >>>> to get a Cog VM which reacting adequately on 'update fonts' on mac :) >>> > FWIW, dropping a Freetype-plugin built with the standard vm into the > resources folder of a Cog-VM on Mac works just fine, so that's a work around > for those who need it before it's buildable directly by Cog. > (at least on Mac, I haven't tested on other platforms) > yeah, i thought about the same. > Cheers, > Henry > -- Best regards, Igor Stasenko AKA sig. |
So...if it works in all OS, can we add such plugin in the next PharoOne Click? or in the vms linked from the Pharo website? because in pharo freetype plugin is important. On Mon, Dec 20, 2010 at 11:28 AM, Igor Stasenko <[hidden email]> wrote:
|
In reply to this post by Igor Stasenko
>> > > of course Stef, of course. > But i think everyone aware of it, so i don't need to repeat this every time :) :) > Btw, let us make clear one little thing: > > I am right to say, that our development model remains the same, i.e. > all things we produce under/for Pharo, become available as soon as > possible to public? yes > Because once you got money, there is someone who could say 'do not > publish those, before i allow you to do so'. Yes this guy could be me but this is not the model :) Stef |
Free forum by Nabble | Edit this page |