[GRASS-dev] automatic user font cap building for init.sh
William Kyngesburye
woklist at kyngchaos.com
Sun May 20 10:52:30 EDT 2007
Ah, thanks. I forgot to ask what the current status of the switch of
the fontcap files was.
On May 19, 2007, at 5:06 PM, Glynn Clements wrote:
>
> William Kyngesburye wrote:
>
>> I didn't get any response to my possible patch for init.sh to do this
>> (it was in the iconv thread), so I went ahead and committed it. If
>> GRASS_FONT_CAP and/or GRASS_FT_CAP are set, and they do not exist
>> yet, init.sh will run g.mkfontcap to create them. This will leave
>> the GRASS binary-installed cap files alone (that is, GRASS_FONT_CAP
>> or GRASS_FT_CAP is not set), and will not overwrite existing user cap
>> files that they may have customized. But it gets them started with
>> their current state of installed fonts.
>>
>> To go along with this, I also set GRASS_FONT_CAP and GRASS_FT_CAP in
>> the OSX app startup to the user's home GRASS support folder. After
>> the first run of GRASS.app, the user can customize these or
>> regenerate them as they like, and not have to worry about permissions
>> to edit the GRASS.app copy.
>
> GRASS_FT_CAP is no longer relevant; only GRASS_FONT_CAP is used.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"Oh, look, I seem to have fallen down a deep, dark hole. Now what
does that remind me of? Ah, yes - life."
- Marvin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20070520/77b72e2d/attachment.html
More information about the grass-dev
mailing list