From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] libhtml vs. <pre> tags
Date: Fri, 21 Oct 2005 18:49:29 +0900 [thread overview]
Message-ID: <d248647d293d5a441129e47947ffb228@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <32d987d50510202209h61161a7esb38c8dd5e4b635@mail.gmail.com>
Hi,
> Now abaco handles <pre> text in a different way,
> this a quick and dirty change, since when the line
> width is bigger than the screen width the text is not
> showed.
This font width problem is also seen when Japanese fonts
are used other than the case of <pre> tag.
This is very common also for other applications...
I'm not forcing you to fix this, rather just reporting.
Kenji
next prev parent reply other threads:[~2005-10-21 9:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 4:34 Federico G. Benavento
2005-10-21 5:09 ` Federico Benavento
2005-10-21 9:49 ` Kenji Okamoto [this message]
2005-10-21 9:51 ` Kenji Okamoto
2005-10-21 13:19 ` erik quanstrom
2005-10-21 13:25 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 18:16 Trickey, Howard W (Howard)
2005-10-21 14:37 Federico G. Benavento
2005-10-21 14:21 Federico G. Benavento
2005-10-21 14:40 ` C H Forsyth
2005-10-21 14:02 Federico G. Benavento
2005-10-21 14:16 ` rog
2005-10-21 14:20 ` LiteStar numnums
2005-10-21 15:09 ` Wes Kussmaul
2005-10-21 13:47 Trickey, Howard W (Howard)
2005-10-21 13:55 ` erik quanstrom
2005-10-21 14:06 ` Wes Kussmaul
2005-10-21 14:16 ` C H Forsyth
2005-10-21 15:04 ` Uriel
2005-10-21 18:45 ` Wes Kussmaul
2005-10-21 19:12 ` Uriel
2005-10-21 19:20 ` Wes Kussmaul
2005-10-21 17:35 ` Skip Tavakkolian
2005-10-21 17:51 ` David Tolpin
2005-10-21 13:40 Federico G. Benavento
2005-10-21 13:51 ` erik quanstrom
2005-10-20 1:56 erik quanstrom
2005-10-20 2:17 ` erik quanstrom
2005-10-20 17:04 ` Federico Benavento
2005-10-21 4:01 ` erik quanstrom
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=d248647d293d5a441129e47947ffb228@granite.cias.osakafu-u.ac.jp \
--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).