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 troll, I'm just curious about the design rationale of > the code. As Ben suggested earlier in this thread, read <http://www.landfield.com/rfcs/rfc2646.html>. That covers how spaces have special meaning with format=flowed. Also the HTML spec says that multiple consecutive spaces are to be rendered as a single space. (this is why we have ). So a space can have different meanings in different contexts... but an "M" can only have one meaning (to the computer at least). The Amigo
- Re: Various mail/news and editor bugs Robin Whittle
- Re: Various mail/news and editor bugs Ben Bucksch
- Re: Various mail/news and editor bugs barney
- Re: Various mail/news and editor bugs Ben Bucksch
- Re: Various mail/news and editor bugs J.B. Moreno
- Re: Various mail/news and editor bugs Akkana
- Re: Various mail/news and editor bugs Joe Francis
- Re: Various mail/news and editor bugs Ben Bucksch
- Re: Various mail/news and editor bugs Ryan Cassin
- Re: Various mail/news and editor bugs Bob Page
- Re: Various mail/news and editor bugs Josh Harding
- Re: Various mail/news and editor bugs Bob Page
- Re: Various mail/news and editor bugs Daniel Bratell
- Re: Various mail/news and editor bugs Ben Bucksch
- Re: Various mail/news and editor bugs Ben Bucksch
- Re: Various mail/news and editor bugs Bob Page
- Re: Various mail/news and editor bugs Joe Francis
- Re: Various mail/news and editor bugs Joe Francis
