unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
Cc: quarl@cs.berkeley.edu, emacs-devel@gnu.org,
	Kenichi Handa <handa@m17n.org>
Subject: Re: BDF files
Date: Tue, 24 May 2005 16:56:10 -0400	[thread overview]
Message-ID: <m3mzqke42d.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <E1DaDXt-0008A7-AS@fencepost.gnu.org> (Richard Stallman's message of "Mon, 23 May 2005 10:04:41 -0400")

>>>>> "KH"  == Kenichi Handa <handa@m17n.org> writes:
>>>>> "RMS" == Richard Stallman <rms@gnu.org> writes:

KH> someone ...

It may have been Primoz Peterlin.

Roman Czyborra also has http://czyborra.com/unifont, but I believe
that only has a 16 pixel high font.

KH> compiled those files and built iso10646 fonts (e.g.
KH> etl24-unicode.bdf).  And someone added them in ps-mule.el.

RMS> Are these fonts free?

Gentoo's mirror of the (24 MB) tar file is at:

http://gentoo.osuosl.org/distfiles/efont-unicode-bdf-0.4.2.tar.bz2

The COPYING file therein says:

=====
(c) Copyright 2000-2001 /efont/ The Electronic Font Open Laboratory.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. Neither the name of the team nor the names of its contributors
   may be used to endorse or promote products derived from this font
   without specific prior written permission.

THIS FONT IS PROVIDED BY THE TEAM AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE TEAM OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS FONT, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
=====

-JimC
-- 
James H. Cloos, Jr. <cloos@jhcloos.com>

  reply	other threads:[~2005-05-24 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  0:32 BDF files Karl Chen
2005-05-23  0:53 ` Kenichi Handa
2005-05-23 14:04   ` Richard Stallman
2005-05-24 20:56     ` James Cloos [this message]
2005-05-25  9:44       ` Richard Stallman
2005-06-01 17:25       ` Richard Stallman
2005-06-01 20:04         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3mzqke42d.fsf@lugabout.cloos.reno.nv.us \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=quarl@cs.berkeley.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).