|
Sorry for the late reply. I'm happy to report that the problem was caused by a mistake in the way I ran Sigil. I made a novice mistake and tried to run Sigil right from the directory in which it was built. Running "sigil" (the sigil in the path variable) from Terminal or running Sigil using the shortcut (I didn't know one was created) fixed the problem completely. The problem was not related to language packages in any way.
One thing I am uncertain of is whether the Sigil shortcut is visible until the computer is started. The shortcuts of some newly installed programs can't be found via the dash until a restart, and I think Sigil might be one of these. It's not a big deal but if this is indeed the case, and if it's easy to fix, it might be helpful to new users to have the shortcut show up right away before a restart is done.
Thanks.
|