Hello Allie Martin,

on Sat, 8 Nov 2003 20:47:18 -0500 (2003-11-09 02:47:18 in .nl) in the
message with reference <mid:[EMAIL PROTECTED]>
you wrote (at least in part):

AM> Peter Ouwehand, [PO] wrote:

PO>> The preferred width comes from some RFC, as someone else mentioned.
PO>> Now what if I would like to read a meaasage in a width which doesn't
PO>> match yours? You (or the RFC) are  now forcing me to use a width
PO>> which you may like, but I may not like.

AM> I don't know if you're hypothesizing or it is that you really have a
AM> problem or do not like reading text wrapped to 76 characters.

I simply say: let the end-use decide.


AM> Be that as it may, one can never hope to please everyone.

True, but you might try.
Let the end-user decide through settings in their email client.
Anything wrong with that ??


AM> When you're writing to a single individual and you do know their
AM> preference, then fine, post to them the way they like.

So, what if the end-user changed his/her mind?


AM> When posting to a discussion list or when sending e-mail to those whose
AM> preference you aren't familiar with, you're far less likely to create
AM> problems by sending the text wrapped, and an optimum limit has been
AM> defined.

All of that is a user-interface question.
Either for the sender or receiver.
Create options/settings:
- send 'long lines' / hard wrap at xx
- display 'long lines' / (soft-)wrap at xx/ display as received
You should look into the ISO structure, like there is (for instance):
- transport
- presentation
Hence: presentation is up to the user-agant.
Ya, this won't adhere to current RFC.
Repeating myself: create (a) new one(s).
Or: stop discussions about wrapping interpretations, they are subjective.


AM> I've just given a VERY practical reason why I don't size the window I
AM> read messages from, according to the text wrap limit I prefer. I size it
AM> according to the message list above which needs a wide window to display
AM> all columns.

Guess you use a 'full account list at the left side', like I do.
Now thats a lame excuse.
The message list representation has absolutely nothing to do with how
the preview of messages below it are presented!
Example: try Forte-Agent (news reader)


PO>> Hence, do not hard-wrap lines.

AM> Bad idea unless you specifically know your other party's preference.

Naw, using my approach, you send text, long lines, no hard-wrap.
Then let the end-user client setting decide how to display it.


PO>> Let the end-user decide what s/he likes. Ya, this means not being
PO>> compliant to RFCs, create a new RFC, and let the end user decide how
PO>> s/he wants to see it, depending on the user-agant setting like: wrap
PO>> at xx, soft wrap at window width, as it has been created,
PO>> ...something else..

AM> You need to see how others work and configure their window widths.
AM> Then run a survey to see which method creates less problems.

What for? (see below)


AM> I'm one of those who intensely dislikes unwrapped lines in e-mail.
AM> Melissa is another. Marck is another. I'm sure there are many
AM> others.

Like I mentioned before: let the end-user client decide.
Wrapped at xx, soft-wrap at window width, as it has been sent,
...other...
It's up to the user-agent programmers to make that available.
It's that simple.


PO>> In HTML-lingo it's called liquid design. Wrapping adjusts to the end
PO>> users' browser width.

AM> Many web pages depart from that liquid design. Only the simply put
AM> together ones still do that. Many, if not most, well developed sites
AM> hardwrap text at a reasonable width for comfortable reading.

Uh?? Most problems I see coming along are about: "my page looks good in
x by y, but gets a horizontal slider when viewed on lower resolution" (or
smaller browser width).
I don't agree with your statement.


-- 
Kind regards,
Peter Ouwehand
E: [EMAIL PROTECTED]
- - -
Created the above using
A program which insists to be : The Bat! V2.01.26
An OS which insists to be     : Windows 2000 5.0 Build 2195 Service Pack 4


________________________________________________
Current version is 2.01.3 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to