So we're going to knuckle under to MicroSloth and change the tags on our list to accommodate one of OE's 'features'? I vote ABSOLUTELY NOT!! How many MicroSloth programmers does it take to change a light bulb?? None. They simply redefine 'darkness' to be the new standard. From below link... " SYMPTOMS If a colon (:) appears in the subject of a message, Outlook Express removes the colon and the text appearing before the colon (up to 4 characters) when you reply to or forward the message. STATUS This behavior is by design. To prevent subjects from being cluttered with unnecessary text when a message is forwarded or replied to multiple times, Outlook Express removes text in the subject that contains from one to four characters and is followed by a colon (for example, "Fw:", "Re:", or "Read:"). Earlier versions of Outlook Express remove only strings of from one to three characters. With the introduction of read receipts (which contain "Read:" in the subject), the string length was increased to four characters. " How long before they extend the feature to 5 then 6 then 7 characters? Leave things the way the are and let those users who choose OE add the extra spaces needed to get their mail to post correctly. Why impose verbosity on those who don't follow the great the MicroSloth way? Can you tell I've been having yet another fight with yet another MS 'non-standard' standard?? "James Newton, webhost" wrote: > > source= http://www.piclist.com/postbot.asp?id=piclist\2003\02\12\214935a > >
> Mystery resolved: > support.microsoft.com/default.aspx?scid=kb;en-us;245199 > > In my humble opinion we should add an extra character in tags with 4 chrs. > eg SX,OT, EE to stop the annoying and chaotic stream of untagged mails. >
> > Oh great... Well, we can change the name of the topics (with difficulty), > but we can't remove the : (lsoft listserv requires it; MIT says they are > going to update to something better "real soon now") > > Can somebody with this version of OE do a quick test and see if it removes > the tag when the colon is *inside* the brackets? e.g. [OT:] rather than According to the article, it would. You'd end up with "] rather than..." Is the lsoft software doing an exact match for the keyword? If so, why not add multiple tags with the same output list. E.G. [OT]: and "..[OT]:" both go to the OT list. Since people have to put in the [OT]: anyway, it can't be that hard for OE users to put in ..[OT]: or [..OT]: or [OT..]: Heck. [..OT]: can be for WAY off topic. If I understand things correctly, all users would have to do is put extra spaces in front of the EXISTING tags, and all would be well Lsoft would strip the whitespace when parsing, and OE wouldn't mess with the colons. Everybody happy? > [OT]: It turns out that lsoft deals with that At first glance, that probably > will not help, but you never know what evil lurks in the minds of men... it > might just honor the brackets. > > Any suggestions for the extra character? M for Microshit? S for Stupid? Or > go for broke: [EEmicrosoftsucks]: [OTmicrosoftsucks]: > > Lsoft says it can NOT be a space, comma, equals, plus, or minus. ( ,=+-) Which leaves period, as I suggested. > Other (bad) ideas: remind people to add a comma or space before the tag. > e.g. ,[OT]: > > And just because I love to hear 500 responses and start big arguments, as > long as we have to change the tags anyway, how about canning the brackets? > e.g. ONPIC: ONSXS: ONAVR: TRONS: OTHER: SELLING: BUYING: > > Rather than replying, please click here to vote: > mailto:james@piclist.com?subject=DROP_BRACKETS > mailto:james@piclist.com?subject=KEEP_BRACKETS You have no provision for suggesting new keywords, should you cave in to Microsloth with this change. Robert -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu