From: "Federico G. Benavento" <benavento@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] plan9 font service [WAS: abaco @ plan9port]
Date: Thu, 13 Mar 2008 12:13:41 -0300 [thread overview]
Message-ID: <32d987d50803130813jf8038ej902477d33ea4e083@mail.gmail.com> (raw)
In-Reply-To: <20080313143334.GA24834@nibiru.local>
there was a fontfs years ago.
Oleg was working on the abaco port, he tweaked some stuff yesterday
you can get it from http://abaco.oitobits.net
On Thu, Mar 13, 2008 at 11:33 AM, Enrico Weigelt <weigelt@metux.de> wrote:
> * Enrico Weigelt <weigelt@metux.de> wrote:
> >
> > now another problem: abaco expects some fonts in
> > /usr/local/plan9/fonts.
> >
> > Seems we need some convenient way for relocating fonts.
> > Maybe an even an fontserver ? ;-)
>
> I've now manually tweaked the pathes in the source, but this
> isn't really a good solution ;-o
>
> Maybe we should introduce some font server (maybe a little bit
> like X has one). This font server represents all (virtually)
> available raster fonts (even autogenerated or remotely fetched)
> in some convenient namespace, so an client only has to open one
> file to get an complete font. (maybe we should also invent some
> complete-font file format instead of splitting them into subfonts
> in the client's view).
>
> In the end, an client should never directly access font files,
> but instead query the font server.
>
> BTW: an interesting thing would be an high-level display server,
> which is capable of complex operations, eg. viewports, font and
> image rendering (maybe something between X and windows' DCs ?).
> The client would only have to send hi-level ops and leave the
> dirty work to an (maybe hw accelerated) display server.
>
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
>
--
Federico G. Benavento
next prev parent reply other threads:[~2008-03-13 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 3:00 [9fans] Hi and, plan9-native abaco sources? Sean Caron
2008-03-08 3:46 ` Pietro Gagliardi
2008-03-08 4:16 ` Iruata Souza
2008-03-10 11:38 ` Vinícius de Figueiredo Silva
2008-03-11 17:01 ` [9fans] abaco @ plan9port [WAS: Hi and, plan9-native abaco sources?] Enrico Weigelt
2008-03-11 17:12 ` Federico G. Benavento
2008-03-12 21:36 ` Enrico Weigelt
2008-03-13 14:33 ` [9fans] plan9 font service [WAS: abaco @ plan9port] Enrico Weigelt
2008-03-13 15:13 ` Federico G. Benavento [this message]
2008-03-13 14:58 ` [9fans] CSS parser for abaco " Enrico Weigelt
2008-03-13 20:30 ` Iruata Souza
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=32d987d50803130813jf8038ej902477d33ea4e083@mail.gmail.com \
--to=benavento@gmail.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).