svn commit: r396872 - in head: Keywords Mk/Uses

[Hiroki Sato]

Baptiste Daroussin <bapt at FreeBSD.org> wrote
  in <20150919230718.GK57815 at ivaldir.etoilebsd.net>:

ba> On Sun, Sep 20, 2015 at 07:55:58AM +0900, Hiroki Sato wrote:
ba> > Baptiste Daroussin <bapt at FreeBSD.org> wrote
ba> >   in <20150914055033.GA54344 at ivaldir.etoilebsd.net>:
ba> >
ba> > ba> On Sun, Sep 13, 2015 at 11:30:22PM +0000, Hiroki Sato wrote:
ba> > ba> > Author: hrs
ba> > ba> > Date: Sun Sep 13 23:30:21 2015
ba> > ba> > New Revision: 396872
ba> > ba> > URL: https://svnweb.freebsd.org/changeset/ports/396872
ba> > ba> >
ba> > ba> > Log:
ba> > ba> >   Add "fc", "fcfontsdir", "fontsdir", and "none" arguments to USES=fonts.
ba> > ba> >   They controls whether fc-cache and/or mkfontdir run in
ba> > ba> >   post-{,de}install targets.
ba> > ba> >
ba> > ba> >   japanese/font-* use manually generates fonts.dir entries to utilize
ba> > ba> >   special modifiers which are useful for CJK fonts.  Because mkfontdir
ba> > ba> >   does not understand and silently remove them from fonts.dir,
ba> > ba> >   options like fonts:fc or fonts:none is required.
ba> > ba> >
ba> > ba> >   Approved by:	portmgr (bapt)
ba> > ba>
ba> > ba> Thank you! can you add a comment at the top of fonts.mk to explain this issue?
ba> > ba> That would avoid someone else coming in a few years making the same mistake as I
ba> > ba> did.
ba> >
ba> >  Sorry for the delay.  I added some comments about this just now.
ba> >
ba> > ba> Do you know how they do fix in linux land? because when working on the fonts, I
ba> > ba> found nothing special being done on any Linux distro, have I missed something?
ba> >
ba> >  I do not think most of Linux distros care about CJK fonts in
ba> >  XLFD---at least for Japanese fonts.  Some distros for Japanese market
ba> >  use a small script to generate fonts.dir.  RedHat was using ttmkfdir
ba> >  utility (included as x11-fonts/ttmkfdir but removed a while ago), but
ba> >  there is no special handling of fonts.dir in RPM of Japanese fonts
ba> >  these days.  This may be because most of applications which support
ba> >  CJK fonts now use Xft/fontconfig only.
ba> >
ba> >  ttmkfdir is one of the utilities which can understand extensions
ba> >  designed for CJK fonts (-x flag).  The difference from normal XFLD
ba> >  entries is modifiers.  In the following example:
ba> >
ba> >  fn=1:dfhsg3.ttc -dynalab-dfhsgothicp-light-r-normal--0-0-0-0-p-0-jisx0208.1983-0
ba> >
ba> >  "fn" specifies font number in TTC.  And since most of Japanese fonts
ba> >  do not have italic variant in the font glyphs, "ai" is used to
ba> >  generate "poor man's italic" glyphs:
ba> >
ba> >  fn=1:ai=0.1:dfhsg3.ttc -dynalab-dfhsgothicp-light-i-normal--0-0-0-0-p-0-jisx0208.1983-0
ba> >
ba> >  I am still not sure of what is the best way for us to maintain
ba> >  fonts.dir which mkfontdir cannot understand.  While ttmkfdir supports
ba> >  it, this utility is not upper-compatible with mkfontdir.  One of the
ba> >  practical ways is that putting a Japanese font to a separate
ba> >  directory and maintaining fonts.dir by pkg-{,de}install script.
ba> >
ba> First thanks for the explanation and the comment that would prevent someone like
ba> me doing the same mistake.
ba>
ba> Do you know if someone is speaking with xorg people to that they can work on the
ba> issue?

 No, I don't.  I think it is relatively easy to make a patch to add
 ttmkfdir-like feature into mkfontdir, though.

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20150920/8ffaf789/attachment.bin>