From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Links for Plan 9
Date: Wed, 10 Dec 2003 21:36:39 -0700 [thread overview]
Message-ID: <8b73be78c54e2828e77e2397022233ab@plan9.ucalgary.ca> (raw)
In-Reply-To: <a69cba51d67423f060b5f3fbea4b0e4f@orthanc.cc.titech.ac.jp>
>> http://pages.cpsc.ucalgary.ca/~mirtchov/p9/links/
>
> Links seems to handle UTF-8 pages correctly. try;
> hget http://p9c.cc.titech.ac.jp/plan9/tmp/links.gz | gunzip | page -w
>
> A good news for japanese-reading people :).
>
> However, the fonts used by links now is not
> very good and the star character appears
> in the place of kanji character.
> --
also note: there is a binary image on the web now, for those of you
with a 386 architecture but without the latest ape/libdraw or ability
to pull one.
there are also numerous fixes to mkfiles (as reported by Presotto) and
leftover binaries caused by my carelessness.
the screenshots that you see on my web page (the slashdot and google
one) show a bug in drawing lines and filled rectangles -- the ordering
of bytes is BGR instead of RGB, this could be just my choice of
incorrect get_color routine. so everything that is not a bitmap (such
as text and images) was drawn with swapped red and blue values.
this bug is now fixed, so you can look at slashdot in all its
(somewhat more properly rendered) glory :)
andrey
ps: the screenshot on titech.ac.jp was taken with an old binary, so
you should probably download it again.
next prev parent reply other threads:[~2003-12-11 4:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 5:18 YAMANASHI Takeshi
2003-12-11 4:36 ` mirtchov [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 1:32 YAMANASHI Takeshi
2003-12-16 2:23 ` okamoto
2003-12-15 2:55 YAMANASHI Takeshi
2003-12-10 22:10 andrey mirtchovski
2003-12-11 2:38 ` David Presotto
2003-12-11 2:39 ` David Presotto
2003-12-12 16:46 ` John Stalker
2003-12-12 17:13 ` mirtchov
2003-12-12 17:15 ` David Presotto
2003-12-13 2:37 ` Dan Cross
2003-12-13 2:48 ` Russ Cox
2003-12-13 3:07 ` Dan Cross
2003-12-13 3:35 ` David Presotto
2003-12-13 8:58 ` Skip Tavakkolian
2003-12-13 18:44 ` ron minnich
2003-12-13 18:06 ` mirtchov
2003-12-13 22:54 ` ron minnich
2003-12-13 23:01 ` boyd, rounin
2003-12-14 5:47 ` ron minnich
2003-12-13 23:03 ` boyd, rounin
2003-12-14 5:47 ` ron minnich
2003-12-14 22:13 ` Dan Cross
2003-12-14 22:02 ` Dan Cross
2003-12-15 1:49 ` okamoto
2003-12-15 1:52 ` Gorka Guardiola Múzquiz
2003-12-15 2:33 ` okamoto
2003-12-15 7:18 ` Skip Tavakkolian
2003-12-15 7:02 ` boyd, rounin
2003-12-15 1:59 ` Geoff Collyer
2003-12-15 2:30 ` okamoto
2003-12-15 2:32 ` Geoff Collyer
2003-12-15 2:40 ` okamoto
2003-12-15 2:52 ` Geoff Collyer
2003-12-15 3:09 ` okamoto
2003-12-16 1:27 ` okamoto
2003-12-15 2:48 ` Russ Cox
2003-12-15 3:00 ` okamoto
2003-12-15 5:20 ` mirtchov
2003-12-15 15:34 ` John Stalker
2003-12-15 17:34 ` vic zandy
2003-12-15 17:51 ` mirtchov
2003-12-15 20:01 ` vic zandy
2003-12-15 20:49 ` rog
2003-12-15 21:36 ` Dan Cross
2003-12-15 23:05 ` C H Forsyth
2003-12-15 23:34 ` Adrian Tritschler
2003-12-16 4:10 ` okamoto
2003-12-16 3:34 ` mirtchov
2003-12-16 4:41 ` okamoto
2003-12-16 3:57 ` mirtchov
2003-12-12 19:22 ` John Stalker
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=8b73be78c54e2828e77e2397022233ab@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).