9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] New internal command for acme proposal (with implementations)
Date: Wed,  5 Feb 2014 11:10:19 -0500	[thread overview]
Message-ID: <e9e8256a8ddcee3836127d6637464926@mikro.quanstro.net> (raw)
In-Reply-To: <BB2BF613-1D6B-4BAC-B9E8-11D0BCFF00AE@bitblocks.com>

> On Feb 5, 2014, at 3:36 AM, erik quanstrom <quanstro@quanstro.net>
> wrote:
> > once one thinks about major modifications, i think it becomes
> > attractive to think about a new editor.  i miss having graphics.
> If you mean mixed text and image, you will end up with some sort of
> structured markup language and a "word processor"!

oberon certainly managed this with trivial layout.

for example, it could be as simple as an interface that allows
graphical applications inline with text.  for example,
	; lc
	clock.c
	; clock&
	[display of clock here persists until killed]
	; pwd
	/usr/quanstro/src/cmd/clock


> What I want is support for complex text layout rendering (for Indian
> languages among others).  This requires supporting OpenType fonts, not
> an easy task.  Mac's TextEdit seems to do a decent job of this but I
> don't like it as an editor.

i don't see why complex layout rendering -> opentype.  could you explain
this?

- erik



  reply	other threads:[~2014-02-05 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 10:44 Uvelichitel
2014-01-24 10:59 ` Uvelichitel
2014-01-24 11:15 ` dexen deVries
2014-02-05 10:49 ` Alexander Sychev
2014-02-05 11:36   ` erik quanstrom
2014-02-05 16:04     ` Bakul Shah
2014-02-05 16:10       ` erik quanstrom [this message]
2014-02-05 16:26         ` Bakul Shah
2014-02-05 16:39       ` dexen deVries
2014-02-05 17:04         ` Bakul Shah
2014-01-24 12:49 Uvelichitel
2014-01-24 17:32 ` Bence Fábián

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=e9e8256a8ddcee3836127d6637464926@mikro.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).