From: "Federico G. Benavento" <benavento@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] some changes to abaco
Date: Mon, 28 Jan 2008 11:16:56 -0200 [thread overview]
Message-ID: <68f03aafccf68f573049f160202d880e@yourdomain.dom> (raw)
lotte% contrib/list -c fgb/abaco
fgb/abaco:
Sat Jan 26 15:21:09 ART 2008
Now abaco reads $home/lib/abaco.fonts to get the
font's paths if present, otherwise the default fonts
are used.
Mon Jan 28 07:45:48 ART 2008
Fixed a bug reported by cinap, happened when the server claimed the doc to be a charset, conflicting with the <meta charset= in the doc. Give priority to the one in the doc.
Also improved text selection in the page content.
Mon Jan 28 08:06:50 ART 2008
Fixed a bug reported by Mathieu Lonjaret. Asume content-type==text/html when the server doesn't say anything.
Mon Jan 28 11:12:58 ART 2008
Updated abaco.fonts to use fgb/freefont pkg (people need working examples).
I also created a contrib the Free UCS Outline Fonts
this is how it looks http://plan9.kicks-ass.org/abaco.jpg
next reply other threads:[~2008-01-28 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 13:16 Federico G. Benavento [this message]
2008-01-28 14:14 ` 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=68f03aafccf68f573049f160202d880e@yourdomain.dom \
--to=benavento@gmail.com \
--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).