I'd say that one should clear all fonts being loaded, refresh the list of available fonts because they are on another location (and this should happen even moving from windows to windows), and switch back to a default font that is sure to be available.
I got an issue with the "hack" font because the new version changed the file names of the fonts and the system died. That should already solve some problems. Phil On Wed, Apr 26, 2017 at 5:10 PM, Andrei Chis <[email protected]> wrote: > Any hints about how to handle Freetype fonts? > Right now I'm getting also some segmentation faults when opening on mac an > image saved on windows, that seem related to Freetype fonts. > > On Wed, Apr 26, 2017 at 5:04 PM, [email protected] <[email protected]> > wrote: > >> You will also face serious fun with Freetype fonts. >> >> Phil >> >> On Wed, Apr 26, 2017 at 3:06 PM, Andrei Chis <[email protected]> >> wrote: >> >>> Hi all, >>> >>> I saw that there are a few issues about images saved on an operating >>> system not working when opened on other operating systems: >>> - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-ima >>> ge-in-OSX-after-it-has-been-updated-in-Windows >>> - https://pharo.fogbugz.com/f/cases/19869/Infinite-loop-on-m >>> ac-when-opening-an-image-saved-on-windows >>> - https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-L >>> inux-if-it-was-previously-saved-on-Windows >>> - http://forum.world.st/Image-freezes-on-Linux-if-it-was-pre >>> viously-saved-on-Windows-td4903258.html >>> >>> I gave the fix in case 19869 a try and with it I can save an image on >>> windows and open it on mac, however, there are some side effects. >>> First several folders having the following name are created in the image >>> folder: >>> >>> '\Users\andrei\test-image' >>> '\Users\andrei\test-image\pharo-local\' >>> '\Users\andrei\test-image\pharo-local\ombu-sessions' >>> >>> Second, I can only open the image on man once. The second time I get the >>> following stack: >>> >>> [31mPrimitiveFailed: primitive #createDirectory: in WindowsStore failed >>> [0mWindowsStore(Object)>>primitiveFailed: >>> WindowsStore(Object)>>primitiveFailed >>> WindowsStore(DiskStore)>>createDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> WindowsStore(FileSystemStore)>>ensureCreateDirectory: >>> FileSystem>>ensureCreateDirectory: >>> FileReference>>ensureCreateDirectory >>> OmSessionStore>>resetWithStoreNamed: >>> OmSessionStore>>resetWithNextStoreName >>> OmSessionStore>>store >>> WeakMessageSend>>value >>> WeakMessageSend>>cull: >>> WeakMessageSend>>cull:cull: >>> [ action cull: arg1 cull: announcer ] in LegacyWeakSubscription(WeakAnn >>> ouncementSubscription)>>deliver: in Block: [ action cull: arg1 cull: >>> announcer ] >>> BlockClosure>>on:do: >>> BlockClosure>>on:fork: >>> LegacyWeakSubscription(WeakAnnouncementSubscription)>>deliver: >>> [ tmp4 deliver: arg1 ] in SubscriptionRegistry>>deliver:to:startingAt: >>> in Block: [ tmp4 deliver: arg1 ] >>> BlockClosure>>ifCurtailed: >>> SubscriptionRegistry>>deliver:to:startingAt: >>> SubscriptionRegistry>>deliver:to: >>> SubscriptionRegistry>>deliver: >>> SystemAnnouncer(Announcer)>>announce: >>> SystemAnnouncer>>announce: >>> SystemAnnouncer>>snapshotDone: >>> SessionManager>>snapshot:andQuit: >>> [0m >>> >>> So it seems that OmSessionStore is not reset and holds a reference to a >>> the windows path which it tries to create. >>> >>> Cheers, >>> Andrei >>> >>> >>> >>> >>> >> >
