On 24 Jan 2017, at 13:39, phil@highoctane.be wrote:
I also have has issues with FT fonts that were not named the same on various boxes.
For example, the Hack font installed a few months ago on one machine had names like "Hack-Oblique.ttf" and are not named like "Hack-Italic.ttf" on the new installs. So, there is a primitive error showing up and blocking the image.
Not saying that is the cause of other troubles but there should be a way to switch back to in image fonts if such a case arises.
This for sure caused me a few headaches.
yep, but this is not a VM issue. In this case is correct that primitive fails⦠is just that FT2 image side doesnât know how to manage the problem :( So we need an issue with this, but I wouldnât say is a blocking point to move latest to stable. Esteban
Phil
On Tue, Jan 24, 2017 at 10:57 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: Hi guys,
I want to move latest vm to stable (for Pharo 6.0, of course).
And I have the idea there are still some blocking issues⦠can you
I have this issues in mind:
No write right on Windows with the new VM <https://pharo.fogbugz.com/f/cases/19525/No-write-right-on-Windows-with-the-n...> Freetype2 primitive failed [error 2][unknown file format] <https://pharo.fogbugz.com/f/cases/19315/Freetype2-primitive-failed-error-2-u...> -> for this Iâm testing the solution pointed here: http://log.smallworks.eu/web/post/289 <http://log.smallworks.eu/web/post/289>, plus a fix Phil sent me. Image freezes on Linux if it was previously saved on Windows <https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-Linux-if-it-was-pre...>
⦠but also anything else that I might be missing.
cheers, Esteban