Re: Consecutive spaces not displayed in some cases
John Van Essen <[email protected]>
| Newsgroups | gmane.mail.archives.mail-archive |
|---|---|
| Message-ID | <200532535812.693004@jve-home> |
Jeff, I'm a little slow on the reply... On Sun, 13 Mar 2005, Jeff Breidenbach <[email protected]> wrote: > > Interesting, I'd never noticed that before. I'm looking at the raw > email received by The Mail Archive (note to self, it is #5525) and am > wondering why mhonarc decided not to use the usual pre tag. I think it > is probably because the Content-Type on the message is asking for > reflow. > > Content-Type: text/plain; format=flowed I believe you are correct. Looking at the resulting html reveals a pattern that hints at mhonarc trying to let text that looks like a paragraph wrap on its own. I wondered what it does with a non-flowed plain text email that is not wrapped (paragraphs all on one line). I found such a message, and mhonarc manually wraps the paragraph using a maximum width of 79 and uses <pre> on the resulting text. So if it's doing that for plain text that could have been flowed then why not manually wrap the other plain text? > My guess is you won't see this problem if the content type is just > text/plain, although I don't know how feasible that is for users. I'm > not sure what to do here, and I think the options are: > > a) do nothing > > b) try to modify the CSS so that spaces in the TT tag > are not consolidated > > c) encourage you to take up the issue on mhonarc-user d) use the m2h_text_plain::filter disableflowed setting as described in http://www.mhonarc.org/MHonArc/doc/resources/mimefilters.html#m2h_text_plain > Open to discussion. I'm currently feeling pretty gun shy about "b". I don't blame you. -- John Van Essen Univ of Minn. Alumnus <[email protected]> On 08 Mar 2005, John Van Essen <[email protected]> wrote: > > In some cases, consecutive spaces that are present in a plain text email > (as shown in the mail-archive html source) are not displayed because they > are within a tt container (instead of a pre container) and therefore get > condensed to a single space when rendered. > > For an example, see: > > http://www.mail-archive.com/rsync-w/[email protected]/msg12548.html > > Toward the end of the script source in that email, you'll see this: > > > echo "EEEEEEE RRRRRR RRRRRR OOOOOO RRRRRR" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "EEEEEE RRRRR RRRRR O O RRRRRR" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "EEEEEE R R R R OOOOOO R R" > > > Whereas in the source html, you'll see this: > > > echo "EEEEEEE RRRRRR RRRRRR OOOOOO RRRRRR"<br> > echo "E R R R R O O R R"<br> > echo "E R R R R O O R R"<br> > echo "E R R R R O O R R"<br> > echo "EEEEEE RRRRR RRRRR O O RRRRRR"<br> > echo "E R R R R O O R R"<br> > echo "E R R R R O O R R"<br> > echo "E R R R R O O R R"<br> > echo "EEEEEE R R R R OOOOOO R R"<br> > > > Note that the leading spaces and some internal spaces are not rendered. > What you should be seeing in the web page is this: > > > echo "EEEEEEE RRRRRR RRRRRR OOOOOO RRRRRR" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "EEEEEE RRRRR RRRRR O O RRRRRR" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "E R R R R O O R R" > echo "EEEEEE R R R R OOOOOO R R" > > > There are several other places in that email where copy'n'paste of > Unix output containing leading or embedded strings of spaces are > missing the extra spaces, yet in other places, a pre container is > used that *does* preserve the spaces. > > Can this missing leading/consecutive spaces problem be fixed? > > Thanks. > -- > John Van Essen Univ of Minn. Alumnus <[email protected]> _______________________________________________ Discussion list for The Mail Archive [email protected] http://jab.org/cgi-bin/mailman/listinfo/gossip