On Dec 10, 2013, at 2:06 PM, Ryan Schmidt wrote:
>
> On Dec 10, 2013, at 11:47, Murray Eisenberg wrote:
>
>> I guess it’s “tidy” to keep the docs within /opt/local/share/fontforge, but
>> what will happen on a version upgrade? will they be left unaffected (I would
>> presume)?
>
> MacPorts w
On Dec 10, 2013, at 11:47, Murray Eisenberg wrote:
> I guess it’s “tidy” to keep the docs within /opt/local/share/fontforge, but
> what will happen on a version upgrade? will they be left unaffected (I would
> presume)?
MacPorts will not touch files it did not put there, so they should remain
I suspected it would be somewhere in /opt/local. Thanks!
Looking further, I see in the fontforge app’s File > Preferences menu item
window an entry for HelpDir that’s set to default, in fact, to:
/opt/local/share/fontforge/doc/fontforge
So that’s where I unarchived the docs, and now I do get
On Tue, Dec 10, 2013 at 12:25 PM, Murray Eisenberg <
murrayeisenb...@gmail.com> wrote:
> I’ve installed the port fontforge @20120731_2. Now I want the Help to call
> local help files.
>
> Following instructions at
> http://fontforge.org/source-build.html#Documentation, I put the
> downloaded, unar
I’ve installed the port fontforge @20120731_2. Now I want the Help to call
local help files.
Following instructions at http://fontforge.org/source-build.html#Documentation,
I put the downloaded, unarchived documentation at
/usr/local/share/doc/fontforge.
But still, after starting fontforge fro