Re: Various mail/news and editor bugs

In article <[EMAIL PROTECTED]>, Robin Whittle <[EMAIL PROTECTED]> wrote: > I spent a week solid in November trying to characterise, find and > fix bugs to do with whitespace in Composer. Robin, I just landed some stuff that should improve the whitespace handling. Give any build after last

Re: Various mail/news and editor bugs

In article <[EMAIL PROTECTED]>, Bob Page <[EMAIL PROTECTED]> wrote: > Ben Bucksch wrote: > > > the (default) composer is a HTML composer. > > So the HTML composer is compressing the whitespace. It doesn't need to > for internal storage of course, but it needs to for user feedback - > the user

Re: Various mail/news and editor bugs

Ben Bucksch wrote: > the (default) composer is a HTML composer. So the HTML composer is compressing the whitespace. It doesn't need to for internal storage of course, but it needs to for user feedback - the user gets a WYSIWYG experience. Makes sense. But that *shouldn't* matter since we shou

Re: Various mail/news and editor bugs

Bob Page wrote: > Agreed, but text/plain (whether fixed or flowed) isn't HTML so I > don't think the HTML spec applies here. It applies, brcause the (default) composer is a HTML composer. -- This message is protected by ROT0 encryption and the DMCA. Reading is disallowed and will be prosecute

Re: Various mail/news and editor bugs

Josh Harding wrote: > As Ben suggested earlier in this thread, read > . That covers how spaces > have special meaning with format=flowed. Actually, RFC2646 has nothing to do with the space problems in the composer. It's the HTML representation of whi

Re: Various mail/news and editor bugs

> However, considering a SPC character (ascii 0x20) for instance, which has > a specific representation for any particular character set, why is it more > difficult to handle than, say, a capital M character? Why don't we have > lots of issues with "M" handling? I guess it's because during both

Re: Various mail/news and editor bugs

Josh Harding wrote: > . That covers > how spaces have special meaning with format=flowed. Yup .. it also says (last p. in section 4) Note that this memo describes an on-the-wire format. It does not address formats for local file stor

Re: Various mail/news and editor bugs

Bob Page wrote: > However, considering a SPC character (ascii 0x20) for instance, which > has a specific representation for any particular character set, why > is it more difficult to handle than, say, a capital M character? Why > don't we have lots of issues with "M" handling? > > This isn't a

Re: Various mail/news and editor bugs

Joe Francis wrote, re whitespace work landing in 0.9: > Sorry it's taking so long; it's not easy. Just curious -- why is it not easy? I understand TAB characters -- they are evil things with indeterminate representation that should just be converted to space characters by the composer IMHO - bu

Re: Various mail/news and editor bugs

Ben Bucksch wrote: > barney wrote: > >> Turning off f=f for message view has effectively >> resolved the long line problem, so I guess I don't need to file a bug >> now. > > barney, what you raised was a *real*, rational problem, not a > preference. The default will be flowed on, so the proble

Re: Various mail/news and editor bugs

"Akkana" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Robin Whittle writes: > > No spell check. > > It works in the Netscape branded version, but unfortunately the > company who owns the spellchecker code wouldn't agree to release > their source. We've

Re: Various mail/news and editor bugs

Joe Francis wrote: > I already replied privately to Robin, but I should tell the rest of the > world to: work on whitespace issues is still in progress and pretty far > along. It should land for moz 0.9 or possibly sooner. Good to hear, the whitespace issues are under the largest problems wit

Re: Various mail/news and editor bugs

Akkana wrote: > Here's why this happens: The Netscape emphasis has > been on html mail, for good or ill. (If it's wrong, no one has managed > to convince them why plaintext mail should be an important corporate > goal). This means that plaintext work for developers inside > Netscape is a spare-

Sorry (was: Re: Various mail/news and editor bugs)

Ben Bucksch wrote: > too bad. [and similar] Robin, I'm sorry for my aggressive tone. I'm getting far too emotional on these topics. I'll try to stay more rational and friendly.

Re: Various mail/news and editor bugs

In article <[EMAIL PROTECTED]>, Robin Whittle <[EMAIL PROTECTED]> wrote: > It does not seem that any changes have been made to correct > the whitespace problems I reported in November 2000 I already replied privately to Robin, but I should tell the rest of the world to: work on white

Re: Various mail/news and editor bugs

Robin Whittle writes: > No spell check. It works in the Netscape branded version, but unfortunately the company who owns the spellchecker code wouldn't agree to release their source. We've been asking for years for someone to do the (fairly minimal) work it would take to plug an open-source

Re: Various mail/news and editor bugs

In article <[EMAIL PROTECTED]>, Robin Whittle <[EMAIL PROTECTED]> wrote: > I think "flowed" achieves something different - the ability of the > sender to have the recipient's email reader reform text according the > recipient's right margin and according to certain rules in the RFC, > which I as

Re: Various mail/news and editor bugs

barney wrote: > Turning off f=f for message view has effectively > resolved the long line problem, so I guess I don't need to file a bug > now. barney, what you raised was a *real*, rational problem, not a preference. The default will be flowed on, so the problem persists for > 99% of the user

Re: Various mail/news and editor bugs

Ben Bucksch wrote: > barney wrote: > >> I turned f=f off in prefs for outgoing mail > > You can turn it off for incoming mail, too, now. Wow. I haven't looked at defaults/pref in a few weeks. Mail-news prefs are growing by leaps and bounds. Maybe some day there will be some UI to go along with

Re: Various mail/news and editor bugs

barney wrote: > With a high screen resolution and fairly wide window (to get > as much as possible in the thread pane), flowed plain text (and html) > lines can be way too long and difficult to read. Point taken. I bet we can limit the width of the body text via CSS. But it should only be limit

Re: Various mail/news and editor bugs

boy, what a pain to cross post! Ben Bucksch wrote: > Robin Whittle wrote: >> I can't imagine why I would want to use >> this in any email I sent. Generally, there is no point in making more >> characters per line than 72 or 77 or so. Longer lines are needed for >> URLs, tabular data, or perhap

Re: Various mail/news and editor bugs

Robin Whittle wrote: > My reports on these newsgroups (I hope it right to post to both) Yes, it is. > In November, I did at least a week of *intense* work trying to > characterize whitespace bugs in Composer. [...] > To my knowledge, none of my investment and the time taken by people who > re

Re: Various mail/news and editor bugs

Further to the discussion of mangling whitespace in plain text email composer: Manually entering, with an Enter on each line, the following: 1 - blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah bla

Re: Various mail/news and editor bugs

Dear Ben, Here is a partial response to what you wrote. My reports on these newsgroups (I hope it right to post to both) is intended to give insight into how at least one user who would like to be enthusiastic about Mozilla finds it impossible to use for everyday work. In November, I did at

Re: Various mail/news and editor bugs

Here are more unhappy experiences from a user who would dearly like to be enthusiastic. These are not obscure or insignificant problems. I am not looking for bugs - just reporting problems I encounter. The display of message subjects, senders on Mozilla is harder to read than with Netscape. Th

Re: Various mail/news and editor bugs

Robin Whittle wrote: > This relates to Mail/News and to the Editor - so I have posted > this to both Newsgroups. I am posting from Netscape since I can't > get Mozilla to access any newsgroups at news.mozilla.org. > > Mozilla (2001030308) under Windows 2000 (with SP1), Celeron 500, >

Re: Various mail/news and editor bugs

One aspect of Mozilla's current functionality reduces usability - for no good purpose as far as I can see: When reading mail or news, the Subject, From, Date and To etc. remains fixed on screen, taking up valuable space. With Netscape, this would scroll up and away as if it was part of the email