Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 May 2002 12:03:40 -0700
From:      Joe Kelsey <joek@mail.flyingcroc.net>
To:        Norikatsu Shigemura <nork@FreeBSD.org>
Cc:        Joe Kelsey <joek@mail.flyingcroc.net>, sobomax@FreeBSD.org, freebsd-ports@FreeBSD.org
Subject:   Re: Mozilla and TrueType
Message-ID:  <3CE4028C.8050203@flyingcroc.net>
References:  <3CE29AEF.6090807@flyingcroc.net>	<3CE2A40D.50DB6E61@FreeBSD.org>	<3CE3EED6.10209@flyingcroc.net> <200205161831.g4GIVRlR055565@nd250009.gab.xdsl.ne.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
Norikatsu Shigemura wrote:

>On Thu, 16 May 2002 10:39:34 -0700
>"Joe Kelsey" <joek@mail.flyingcroc.net> wrote:
>  
>
>>+# x11-servers/xfstt creates this directory...
>>+.if exists($(PREFIX)/lib/X11/fonts/TrueType)
>>+WITH_TRUETYPE_DIR=$(PREFIX)/lib/X11/fonts/TrueType
>>+.endif
>>    
>>
>
>	Hum.. Please chage WITH_TRUETYPE_DIR= to WITH_TRUETYPE_DIR?=.
>	I don't use system TrueType fonts (${PREFIX}/lib/X11/...)
>	for Mozilla, but use my others fonts
>	(/usr/local/share/fonts/THIRD_PARTY_TRUETYPE_FONT_COLLECTION/)
>	i.e. made by Ricoh, Dynalab, etc...
>
I suspect that whatever solution Maxim eventually commits, it will not 
solve everyone's problems, especially if you have multiple directories 
that you would like to support.  The samples I posted are just that, 
samples designed to solve my issue with having to edit unix.js on every 
reinstall of Mozilla.

I hope that it provides a starting point for others to try to solve 
their problems with the true type support.  Please feel free to submit 
suggestions to Maxim for ways to solve other problems, especially 
multiple directories.  I have no personal attachments to the code as 
written and anyone who has suggestions for improvements, please submit 
them to the list and/or Maxim.  Of course, the ?= change is something 
that maybe should have been in the original...

Does it hurt to always set truetype suport to true even if you specify 
no directories?  If so, maybe we could split the support into two 
pieces.  One would be to always patch unix.js to set true type support 
to true, another to parse a list of directories containing truetype 
fonts, say in PATH-format.  Then a simple shell script could just append 
the list of directories to unix.js without any special sed processing, e.g.,

#!/bin/sh
font=1
for i in $(echo ${WITH_TRUETYPE_PATH} | sed -e 's/:/ /g'); do
  echo "pref(\"font.directory.truetype.$font\", \"$i\");" >>unix.js
  font=$((font+1))
done

Of course, fitting the above loop into a Makefile would require fiddling 
with quotes and $ and so on...plus, we would have to decide if we accept 
the path value passed in or prepend or append the system default path 
(e.g., /usr/X11R6/lib/X11/fonts/TrueType).  Probably just use ?= to set 
a default value.

/Joe



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CE4028C.8050203>