This project has moved and is read-only. For the latest updates, please go here.

Code tags not working

Jun 1, 2010 at 5:47 PM

Hi Jochan,

Using v20 with "Use plain text converter" ticked I seem unable to able to send leading spaces and/or indents between [vbnet]...[/vbnet]. Please see

Msdn.en-US.msdnsandbox
Subject:: vbnet tag test

Thanks,
Peter Thornton

Jun 2, 2010 at 12:08 PM

Can you test with the latest version again? (V22)

Jun 2, 2010 at 1:26 PM

I've just tried again with v22. Still no spaces or indents between the vbnet tags. However an intial dot now appears (before it was being truncated). So something has changed :-)

http://social.Msdn.microsoft.com/Forums/en-US/msdnsandbox/thread/554bfefa-0734-46ed-a993-c36bceb5bb1c#cbf8fe85-3cbe-46d0-aa5a-5ee8a3207c49

It seems to work for others, could it be I am missing something obvious my end?

Peter

Jun 2, 2010 at 1:53 PM

It does not seem that you are using the plaintext converter... Can you show the debug window and post the output, after you have posted an article!?

Please be sure you check the checkboxes "Converters" and "WebService".

I assume, your client is posting the article as html/text; then the plain/text converter will not be called. It will only be called if you post as "plain/text".

Jun 2, 2010 at 2:15 PM

The Checkbox "Use plain/text converter" is ticked. In advanced settings I it shows UsePlainTextConverter : True

OE, Tools, Send, News Sending Format, Option is set to Plain Text

I've just sent same message again, following from the debu window with all options checked

Received: POSTDATA: From: "Peter Thornton" <pmbthornton@gmail.com>
Newsgroups: Msdn.en-US.msdnsandbox
References: <ce79283b-0f26-443d-8dc9-54267df283b8@communitybridge.codeplex.com> <cbf8fe85-3cbe-46d0-aa5a-5ee8a3207c49@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Wed, 2 Jun 2010 14:06:21 +0100
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original

Same test again -

Using v22 with "Use plain text converter" ticked, OE

[vbnet]This follows the open vbnet tag
    four spaces
        eight spaces
            twelve spaces
    one tab
        two tabs
            three tabs
        two tabs
    one tab
    .dot one tab  ' should be a dot after the tab
[/vbnet]
close vbnet tag in line above


ClientConnected: 4
ClassifyCommand: MODE READER
Received: Command: MODE, Parameters: READER
Received: Response: 200 Community Forums Bridge News Server Ready - posting allowed

ClassifyCommand: GROUP Msdn.en-US.msdnsandbox
Received: Command: GROUP, Parameters: Msdn.en-US.msdnsandbox
Received: Response: 211 3885 1 3885 Msdn.en-US.msdnsandbox group selected

ClientConnected: 5
ClassifyCommand: POST
Received: Command: POST, Parameters:
Received: Response: 340 send article to be transferred.  End with <CR-LF>.<CR-LF>

DataReceived: Client 5 is posting data
CreateReply: ForumId: 007fb9fb-f31d-4cde-a6fa-eae62d56195c, DiscussionId: 554bfefa-0734-46ed-a993-c36bceb5bb1c, ThreadId: cbf8fe85-3cbe-46d0-aa5a-5ee8a3207c49, Content: Same test again -<br /><br />Using v22 with &quot;Use plain text converter&quot; ticked, OE<br /><br />[vbnet]This follows the open vbnet tag<br />    four spaces<br />        eight spaces<br />            twelve spaces<br />    one tab<br />        two tabs<br />            three tabs<br />        two tabs<br />    one tab<br />    .dot one tab  ' should be a dot after the tab<br />[/vbnet]<br />close vbnet tag in line above <br /><br /><br />
Response: 240 article posted ok

ClientDisconnected: 5

Jun 2, 2010 at 2:17 PM

It had be nice, if you also had checked the "Converters" and "WebService" checkbox on the debug window ;) and also "Main"... At best: Every checkbox you find ;)

Jun 2, 2010 at 2:36 PM

I'm confused, I'm sure all 5 checkboxes were ticked before and after sending the message (incl WebService and Converters). Obviously you have a reason for thinkng otherwise so I've repeated and taken a screenshot of the debug window with the 5 options all checked.  The image also shows all the text below -

Received: Response: 340 send article to be transferred.  End with <CR-LF>.<CR-LF>

DataReceived: Client 2 is posting data
Received: POSTDATA: From: "Peter Thornton" <pmbthornton@gmail.com>
Newsgroups: Msdn.en-US.msdnsandbox
References: <cbf8fe85-3cbe-46d0-aa5a-5ee8a3207c49@communitybridge.codeplex.com> <c59dfd3b-19d5-4ac6-8275-528f58f35e04@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Wed, 2 Jun 2010 14:27:38 +0100
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original

Keep on trying!

Using v22 with "Use plain text converter" ticked, OE

[vbnet]This follows the open vbnet tag
    four spaces
        eight spaces
            twelve spaces
    one tab
        two tabs
            three tabs
        two tabs
    one tab
    .dot one tab  ' should be a dot after the tab
[/vbnet]
close vbnet tag in line above


CreateReply: ForumId: 007fb9fb-f31d-4cde-a6fa-eae62d56195c, DiscussionId: 554bfefa-0734-46ed-a993-c36bceb5bb1c, ThreadId: c59dfd3b-19d5-4ac6-8275-528f58f35e04, Content: Keep on trying!<br /><br />Using v22 with &quot;Use plain text converter&quot; ticked, OE<br /><br />[vbnet]This follows the open vbnet tag<br />    four spaces<br />        eight spaces<br />            twelve spaces<br />    one tab<br />        two tabs<br />            three tabs<br />        two tabs<br />    one tab<br />    .dot one tab  ' should be a dot after the tab<br />[/vbnet]<br />close vbnet tag in line above <br /><br /><br />
Response: 240 article posted ok

ClientDisconnected: 2

Jun 2, 2010 at 2:41 PM

Hmmm... I posted exact the same text as you and it worked ;)

 

OK, now I see what the problem is... your newsreader is not specifying any "Content-Type"... therefor I do not know that it is text/plain....  hmmm... what can I do here...

Jun 2, 2010 at 2:42 PM

Newsgroups: Msdn.en-US.msdnsandbox
References: <ce79283b-0f26-443d-8dc9-54267df283b8@communitybridge.codeplex.com> <cbf8fe85-3cbe-46d0-aa5a-5ee8a3207c49@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Wed, 2 Jun 2010 14:06:21 +0100
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original

There is no "Content-Type: text/plain; charset=utf-8" like in any other newsreader...

Hmm... still puzzled...

Jun 2, 2010 at 2:43 PM

I will do the following: If no "Content-Type" is present, I will also assume "text/plain"...

To verify this, can you post as HTML? and see if an "Content-Type" will be present?

Jun 2, 2010 at 3:04 PM

AH HA! OK I changed to HTML, sent a message, then I reverted to Plain Text and sent another message. With the HTML message it shows

Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_008D_01CB0263.1F244680"

But after switching back to Plain Text still no "Content-Type"

Getting somewhere ?


DataReceived: Client 3 is posting data
Received: POSTDATA: From: "Peter Thornton" <pmbthornton@gmail.com>
Newsgroups: Msdn.en-US.msdnsandbox
References: <d5b7c690-4c91-4030-922f-57de5f0abe54@communitybridge.codeplex.com> <ab8cb710-9e24-49d2-b520-1da7ccb7cd01@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Wed, 2 Jun 2010 14:51:45 +0100
Lines: 38
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_008D_01CB0263.1F244680"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931

This is a multi-part message in MIME format.

------=_NextPart_000_008D_01CB0263.1F244680
Content-Type: text/plain;
 charset="utf-8"
Content-Transfer-Encoding: quoted-printable

OE, Tools, Send, News Sending format: HTML

This message is being sent in HTML, BOLD, ITALLIC


------=_NextPart_000_008D_01CB0263.1F244680
Content-Type: text/html;
 charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.6000.17023" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Courier New" size=3D2>OE, Tools, Send, News Sending =
format:=20
HTML</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>This message is being sent in =
HTML,=20
<STRONG>BOLD, <EM>ITALLIC</EM></STRONG></FONT></DIV>
<DIV><STRONG><EM><FONT face=3D"Courier New"=20
size=3D2></FONT></EM></STRONG>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_008D_01CB0263.1F244680--

MIME-Part: HTML selected


<SNIP>

============================================================

OE changed back to Send Plain Text

============================================================


DataReceived: Client 2 is posting data
Received: POSTDATA: From: "Peter Thornton" <pmbthornton@gmail.com>
Newsgroups: Msdn.en-US.msdnsandbox
References: <ab8cb710-9e24-49d2-b520-1da7ccb7cd01@communitybridge.codeplex.com> <23b484ca-fbe3-445e-8bdc-a8b107e06f64@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Wed, 2 Jun 2010 14:57:08 +0100
Lines: 4
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original

OE, Tools, Send, News Sending format: Plain text
This message is being sent in Plain text


CreateReply: ForumId: 007fb9fb-f31d-4cde-a6fa-eae62d56195c, DiscussionId: 554bfefa-0734-46ed-a993-c36bceb5bb1c, ThreadId: 23b484ca-fbe3-445e-8bdc-a8b107e06f64, Content: OE, Tools, Send, News Sending format: Plain text<br />This message is being sent in Plain text<br /><br /><br />
Response: 240 article posted ok

ClientDisconnected: 2


 

Jun 2, 2010 at 3:06 PM

The next release will support _no_ Content-Type and will then use plain/text; and the the text-converter will also work for you ;) just wait a couple of hours ;)

Jun 2, 2010 at 3:14 PM

Fantastic :-)

FWIW I notice each time I use the debug window, after sending a message the connection becomes lost. I need to completely restart the app by pressing Exit. Simply pressing Stop & Start doesn't help.

Jun 2, 2010 at 5:29 PM

I've just got the vbnet tags to work using OE with v22 !!!

OE, Tools, Send, News Sending Format, Plain Text settings, MIME option.
Before I had the Uuencode option checked, it's probably been like that since I installed OE. Not that I understand the difference!

One odd thing, first time I tried to send (after implementing the above change) with the debug window (5 options ticked) I got an error

Outlook Express could not post your message.  Subject 'Re: vbnet tag test', Account: 'Jochan', Server: '127.0.0.1', Protocol: NNTP, Server Response: '441 posting failed', Port: 119, Secure(SSL): No, Server Error: 441, Error Number: 0x800CCCA9

I quit the debug window, re-started the app, then the message went through fine with the tags.

Anyway, I guess other OE users will have the same default Uencode setting, But if they change to MIME looks like "Content-Type: text/plain; charset=utf-8" will be included

Jun 2, 2010 at 10:16 PM

I've updated to v23. Different more serious problem, with Plain Text option Uencode, below is a snippet of post as received

<br />
<pre lang="x-vbnet">This follows the open vbnet tag
&nbsp; &nbsp; four spaces
&nbsp; &nbsp; .dot one tab ' should be a dot after the tab</pre>
close vbnet tag in line above
<br />

With v22 plus option Uencode simply no spaces or visible <br> tags.

If I change Plain text option from Uuencode both v22 and v23 work fine

Another problem as I mentioned before - With the debug window open, after attempting to send a message OE gives this error

Outlook Express could not post your message.  Subject 'Re: vbnet tag test', Account: , Server: '127.0.0.1', Protocol: NNTP, Server Response: '441 posting failed', Port: 119, Secure(SSL): No, Server Error: 441, Error Number: 0x800CCCA9

Jun 3, 2010 at 6:53 AM

I do not understand what you mean with "Uencode..." How do you do that?

Greetings
  Jochen

Jun 3, 2010 at 9:34 AM

OE, Tools, Options, Send, News Sending Format, Plain Text Settings. This opens a new dialog, in section "Message Format" there are two options, MIME and Uencode. Originally my option was set to Uencode. When I changed it to MIME (after our discussion above but before you released v23) everything worked fine with v22, I assume because with the MIME option it produces "Content-Type: text/plain; charset=utf-8". To summarize -

v22 + Uencode, the format tags do nothing (as if  Use plain text converter is not ticked)
v22 + MIME, the format tags work fine
v23 + Uencode, the format tags don't work as expected but introduce visible html codes, see sample above, or see web-view (link in my 2nd post above)
v23 + MIME, the format tags work fine

With both v22 and v23 + MIME + UsePlainTextConverter=True, when the debug window is open OE errors when trying to send the message,

Jun 3, 2010 at 10:58 AM

I am not able to repro this problem with V24... Are there any error messages in the debug window?

Jun 3, 2010 at 11:43 AM

Not sure if you mean, you can't repro the OE error whle using the debug window or incorrect message with Uuencode. Anyway, with v24 now no problem with the debug window :-) But still same problem with the Uuencode option selected.

Following is from the debug with Uuencode option selected, I don't see any errors though

ClientConnected: 4
ClassifyCommand: MODE READER
Received: Command: MODE, Parameters: READER
Received: Response: 200 Community Forums Bridge News Server Ready - posting allowed

ClassifyCommand: POST
Received: Command: POST, Parameters:
Received: Response: 340 send article to be transferred.  End with <CR-LF>.<CR-LF>

DataReceived: Client 4 is posting data
Received: POSTDATA: From: "Peter Thornton" <pmbthornton@gmail.com>
Newsgroups: Msdn.en-US.msdnsandbox
References: <850ba1e2-42c0-4e46-bece-16b485f845ff@communitybridge.codeplex.com> <8d9fe819-1f56-4db9-aa3f-3e79c8cfe6b4@communitybridge.codeplex.com>
Subject: Re: vbnet tag test
Date: Thu, 3 Jun 2010 11:34:19 +0100
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original

This with option Uuencode, using v24

*Bold text* normal /italic text/ normal _underline text_ normal

[vbnet]
This follows the open vbnet tag
    four spaces
        eight spaces
            twelve spaces
    one tab
        two tabs
            three tabs
        two tabs
    one tab
    .dot one tab  ' should be a dot after the tab
[/vbnet]
close vbnet tag in line above

> quoted text


FromClient: Re: vbnet tag test:
This with option Uuencode, using v24

*Bold text* normal /italic text/ normal _underline text_ normal

[vbnet]
This follows the open vbnet tag
    four spaces
        eight spaces
            twelve spaces
    one tab
        two tabs
            three tabs
        two tabs
    one tab
    .dot one tab  ' should be a dot after the tab
[/vbnet]
close vbnet tag in line above

> quoted text

 

FromClient after conversion: Re: vbnet tag test:
This with option Uuencode, using v24
<br />
<br /><strong>Bold text</strong> normal <em>italic text</em> normal <u>underline text</u> normal
<br />
<pre lang="x-vbnet">This follows the open vbnet tag
&nbsp; &nbsp; four spaces
&nbsp; &nbsp; &nbsp; &nbsp; eight spaces
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; twelve spaces
&nbsp; &nbsp; one tab
&nbsp; &nbsp; &nbsp; &nbsp; two tabs
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; three tabs
&nbsp; &nbsp; &nbsp; &nbsp; two tabs
&nbsp; &nbsp; one tab
&nbsp; &nbsp; .dot one tab&nbsp; ' should be a dot after the tab</pre>
close vbnet tag in line above
<br /><blockquote> quoted text
<br />
<br />
<br />
CreateReply: ForumId: 007fb9fb-f31d-4cde-a6fa-eae62d56195c, DiscussionId: 554bfefa-0734-46ed-a993-c36bceb5bb1c, ThreadId: 8d9fe819-1f56-4db9-aa3f-3e79c8cfe6b4, Content: This with option Uuencode, using v24<br />&lt;br /&gt;<br />&lt;br /&gt;&lt;strong&gt;Bold text&lt;/strong&gt; normal &lt;em&gt;italic text&lt;/em&gt; normal &lt;u&gt;underline text&lt;/u&gt; normal<br />&lt;br /&gt;<br />&lt;pre lang=&quot;x-vbnet&quot;&gt;This follows the open vbnet tag<br />&amp;nbsp; &amp;nbsp; four spaces<br />&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; eight spaces<br />&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; twelve spaces<br />&amp;nbsp; &amp;nbsp; one tab<br />&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; two tabs<br />&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; three tabs<br />&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; two tabs<br />&amp;nbsp; &amp;nbsp; one tab<br />&amp;nbsp; &amp;nbsp; .dot one tab&amp;nbsp; ' should be a dot after the tab&lt;/pre&gt;<br />close vbnet tag in line above<br />&lt;br /&gt;&lt;blockquote&gt; quoted text <br />&lt;br /&gt;<br />&lt;br /&gt;<br />&lt;br /&gt;
Response: 240 article posted ok

ClientDisconnected: 4

Jun 3, 2010 at 12:53 PM

I found the bug. It will be fixed in the next release. It has still to do with the missing Content-Type...

Jun 3, 2010 at 6:50 PM
Edited Jun 3, 2010 at 6:58 PM

V24, almost perfect :-)

Two slightly odd things though (I've checked my original sent message)
1. A new empty line is introduced as the first line even if the 2nd line doesn't include any tags

2. Two new last lines are added to my my test message. The first is a blank line and the new last line now includes the characters "[code]" without quotes

Jun 3, 2010 at 9:11 PM

Sorry, ignore what I said about 2, my mistake. I had accidently include a second open [vbnet] tag at the bottom. Also looking at the posting in Web view the additional top line does not appear, only when viewing in my newsreader. Not serious but seems slightly odd