From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 3 questions
Date: Tue, 30 May 2006 15:26:12 +0900 [thread overview]
Message-ID: <DF15E3B4-6DDC-4D07-99F0-A9D8D1C634B3@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <447BCB5E.8040206@lanl.gov>
Hello,
I am converting my own style which I call tt format to html format.
The tt format is like below:
H1: main title here
H2: subtitle hera
unordered list is
- something here
- something here
- something here
Program code is
P:!
some program code
...
...
!
H2: Where is the example
All of my web pages are written using tt format.
You can look the examples at
- http://ar.aichi-u.ac.jp
- http://plan9.aichi-u.ac.jp
A special page for tt format is
http://ar.aichi-u.ac.jp/tt/
The converter is written in python. You can download from
http://ar.aichi-u.ac.jp/tt/ptt.py
Kenji Arisawa
On 2006/05/30, at 13:34, Ronald G Minnich wrote:
> lucio@proxima.alt.za wrote:
>
>> Well, what's so bad about editing raw HTML? It is considerably more
>> embarrassing to publish the type of unreadable trash (only its mother
>> could love that HTML!) produced by the average HTML editor. Take a
>> look, sometimes.
>
> It's not me. It's a user. This is a very common problem. I just
> edit html myself. But I was wondering if there was something more
> acceptable under plan 9 than raw html.
>
> thanks
>
> ron
next prev parent reply other threads:[~2006-05-30 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 16:33 Ronald G. Minnich
2006-05-29 16:36 ` quanstro
2006-05-29 16:40 ` quanstro
2006-05-29 16:49 ` jmk
2006-05-29 17:15 ` lucio
2006-05-30 4:34 ` Ronald G Minnich
2006-05-30 6:26 ` arisawa [this message]
2006-05-30 7:35 ` quanstro
2006-05-29 17:57 ` Russ Cox
2006-05-30 0:04 ` geoff
2006-05-29 17:58 ` Russ Cox
2006-05-29 22:55 ` Adrian Tritschler
2006-05-30 3:05 ` Micah Stetson
2006-05-29 17:14 Fco. J. Ballesteros
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=DF15E3B4-6DDC-4D07-99F0-A9D8D1C634B3@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-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).