9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese Font
Date: Fri,  9 Feb 2001 13:16:45 +0900	[thread overview]
Message-ID: <20010209041728.9F506199EF@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 180 bytes --]

Thank you very much, Rob.

Yes, I was wondering there must be some smart way like your first method
in Plan 9, but not only by forcing it strongly.   I will try it.

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 2008 bytes --]

From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese Font
Date: Thu, 8 Feb 2001 22:41:43 -0500
Message-ID: <20010209034147.2ACFB199E1@mail.cse.psu.edu>

Yes, I understand that.  I was trying to tell you the way to do it.
It's like this, schematically:

	s = allocimage(0, 0, HUGE, height);
	x = 0;
	for(i in number of characters){
		c = allocmemimage(0, 0, c.width, height);
		convert bdf to character in c
		draw(s, Rect(x, 0, x+c.width, height), c, nil, ZP);
		fontchar[i] = {...., x, ...};
		x += c.width;
	}
	t = allocimage(0, 0, x, height);
	draw(t, t->r, s, nil, ZP);

Or you could calculate the subfont width before allocating
s by adding another loop.

-rob

             reply	other threads:[~2001-02-09  4:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09  4:16 okamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-20  3:14 suzuki
2001-02-19  2:18 okamoto
2001-02-19  2:13 okamoto
2001-02-19  2:11 suzuki
2001-02-15  4:50 okamoto
2001-02-13  7:24 okamoto
2001-02-13  5:35 okamoto
2001-02-09  3:41 rob pike
2001-02-09  3:34 okamoto
2001-02-09  3:14 rob pike
2001-02-09  3:06 okamoto

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

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

  git send-email \
    --in-reply-to=20010209041728.9F506199EF@mail.cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --cc=9fans@cse.psu.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.
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 NNTP newsgroup(s).