[REMINDER] IntroComp Intent to Enter Deadline Looming

[Jacqueline A. Lott]

Just a quick reminder: If you're interested in submitting the
beginning of a piece of interactive fiction to this year's IntroComp,
intents to enter are due by March 1. (Egad! that's just one week from
today!)

'Finished' introductions will be due March 21, so there's still time
to code up your introduction, get it beta tested, and dangle your idea
for a larger work of IF in front of everyone in the community. It's a
great way to get feedback on an idea, and who knows? You might even
win a prize!

Rules for the comp can be found at http://www.xyzzynews.com/introcomp/

Intents to enter should be submitted to jacqu...@mountainmemoirs.com

Also, an aside... I will be away on business this week, and due to the
remote location in which I'll be working, my internet access will be
greatly curtailed. So, if you reply to this post or submit an intent
to enter the comp, do not fear if you do not receive an immediate
response from me, as I may have to wait until I get back next weekend
before I reply.

Best of luck!
- Jacqueline A. Lott
_____

The waters of Usenet were once rich in posters. Then the Usenet
trawlers set their nets and devastated the population, leaving the
ecology in serious imbalance.

[Jacqueline A. Lott]

Also, a quick apology on the format of that previous post.

I'm using a new client that *claimed* it would be cutting off the
end of each line so those of you on Google wouldn't have to scroll.
I'm *certain* this was the program's fault and in *no way* could it
be, say, user error, but I thought I'd apologize nonetheless.

Have a great week, and 'see' you all when I'm back home.

[John W. Kennedy]

Jacqueline A. Lott wrote:
> Also, a quick apology on the format of that previous post.
>
> I'm using a new client that *claimed* it would be cutting off the
> end of each line so those of you on Google wouldn't have to scroll.
> I'm *certain* this was the program's fault and in *no way* could it
> be, say, user error, but I thought I'd apologize nonetheless.

Mozilla (and therefore Netscape 6/7) uses the relatively new
"format=flowed" option, which is marked in the "Content-Type" header of
your message. It _does_ break off the message at the column that you
set, but ends each line that it breaks (but you did not) with an extra
space. An up-to-date client will recognize that, and reflow the
original paragraphs according to its own rules; therefore, it looks to
_you_ as though the lines weren't broken at all. But the automatic
breaks will appear in a less-sophisticated reader, which is unaware of
the new option.

In other words, your message will look fine on Google (once it gets there).

Mozilla has been made aware of the fact that this is confusing to people
who don't know about the format=flowed option.

--
John W. Kennedy
"The poor have sometimes objected to being governed badly;
the rich have always objected to being governed at all."
-- G. K. Chesterton, "The Man Who Was Thursday"

[Jacqueline A. Lott]

> In other words, your message will look fine on Google (once it gets there).

Funny thing: I'm on the road now, just found a computer to check my mail,
and decided to check R*IF since I had some down time. Now that I'm not on
my home computer, I'm checking this through Google Groups. I noticed
(before opening your post) that my first post yesterday formatted just fine,
just as you said. Who knew?

Thank you, oh John Who Is Wise in the Ways of Netscape! Chances are,
had I not found this computer to check Google, and you had not posted,
I would now be inserting hard returns throughout my posts in Netscape,
which is, shall we say, a very large pain in a somewhat private area
when editing posts.

Have a great week everyone... and keep those intents for IntroComp coming!