1

Closed

Paintext converter (http detection without http)

description

Hi!
 
See this post (en français) :
http://social.answers.microsoft.com/Forums/en-US/answerssandbox/thread/7eef37d1-6243-44be-a62e-3acca4e3eba7#28ff0b2f-1e5d-4e61-b54c-e205629dd484
 
1) "Problem" with web signature already defined on the forum (in newsreader)
2) Broken link (character "!")
 
and
 
3) 1 not bold : "*" is the first character of the line?
4) ... always flowed format -> ":" go to the next line (type quote)
 
Thanks. Pierre TORRIS (FR)

file attachments

Closed Jun 3, 2010 at 10:11 PM by
Fixed in V26

comments

jkalmbach wrote Jun 1, 2010 at 2:47 PM

  1. I do not understand your first problem... either you use your web-signature or your newsreader signature. The bridge can not detect if you have enabled your web signature! So deactivate one of these.
  2. I added the "!" as a valid URL character; will be fixed in the next release
  3. WHCIH version of the bridge are you using? Be sure you use V20!
  4. We are still working on the "flowed" format; in V20 the line wrapping is disabled by default; you can enabled it in the Tools|Advanced options...| AutoLineWrap"

ptorris wrote Jun 1, 2010 at 3:51 PM

1) One signature is used (Forum) and it is correct on the web. But it is already defined in clickable Web format! The bridge makes 2 clickables links into the newsreader (in the function ConvertHtmlBodyToText).

2) Thanks

3) V20 (1.1.20.0) - In this post, "*" is the first character of the line! See 1 and 2

4) Ok Thanks

PapyNet wrote Jun 1, 2010 at 3:52 PM

Example of signing a post made since the News Reader.
The signature from the profile

Example in the News Reader :

PapyNet wrote Jun 1, 2010 at 3:55 PM

Results in News Reader

kaisch wrote Jun 1, 2010 at 3:59 PM

Please do not remove the line wrapping completely once the flowed format works! My newsreader doesn't like the flowed format. Please allow switching between flowed and normal plain text. Thanks!

kaisch wrote Jun 1, 2010 at 4:11 PM

ptorris: by looking at your link I think I understand what your problem is concerning 1) It is not making "two clickable" links. What happens is that the forum provides a clickable URL (a href). The converter converts this to "name ". In your case name and URL are the same. This is working as designed. The usual format of a link in the forums is quite often name!=URL. Bear in mind this is meant to translate all kinds of links from the forum, not bare URLs. Jochen; it might be worthwhile to check if name==URL and then convert only to URL or .

ptorris wrote Jun 1, 2010 at 5:19 PM

@kaisch: No, in my case, name != URL (www.ptorris.com != htpp://www.ptorris.com)
"ConverTo" function compares name (plaintext) and URL (href)
If != plaintext += " " -> www.ptorris.com
If these are the same the function adds nothing

jkalmbach wrote Jun 1, 2010 at 5:28 PM

Currently the PlainText converter only add a separat if the url != text!

kaisch wrote Jun 1, 2010 at 5:58 PM

ptorris: so, it is working exactly as designed and desired. name . Perfectly ok. There is nothing to complain. If you want to have it different than add the protocol. That's better anyway.

jkalmbach wrote Jun 2, 2010 at 11:03 AM

Does this mean, that I can close this issue?

ptorris wrote Jun 2, 2010 at 11:26 AM

Joken: the text can be different from the url, and be of the form "www.xxx.xxx" - It works with my newsreader (MesNews), but also with Windows Live Mail, Thunderbird...

Kaisch: yes, it is not making "two clickable" links. But the form "www.xxx.xxx" is recognized (http protocol is not necessary) with "modern" newsreader and this creates two links. It is the same with the mailto protocol.

IMHO, this could be solved with regex. For example (cf. EditPad) :
http://www.regexguru.com/2008/11/detecting-urls-in-a-block-of-text/

NB : Optionally, this could be disabled in options

jkalmbach wrote Jun 2, 2010 at 12:11 PM

And how should I detect, if the names are different? Just always reoved the protocol and compare?

ptorris wrote Jun 2, 2010 at 1:51 PM

The comparison is correct, but if the text (plaintext) is simple forme "www." (for example) does not add because the newsreader can handle it himself (option can be disabled to suit everyone), no ?

jkalmbach wrote Jun 2, 2010 at 2:11 PM

If the comparsion is ok, then the link
www.codeplex.de
SHOULD result in:
www.codeplex.de
!?

ptorris wrote Jun 2, 2010 at 3:58 PM

In this case, the result is (attachment):
result_plaintext_converter.jpg

jkalmbach wrote Jun 3, 2010 at 9:59 PM

It will be fixed in the next release ;)

jkalmbach wrote Jun 3, 2010 at 10:09 PM

V26 now released. Can you check it again?

ptorris wrote Jun 4, 2010 at 8:25 AM

YES it's ok for URL! Thanks Joken! ;)
V26 test is the same address
But bold (*) has a problem at the beginning of the line (even if space)

jkalmbach wrote Jun 4, 2010 at 8:41 AM

What do you mean with "*" at the beginning of the line?
Can you show me an example?

ptorris wrote Jun 4, 2010 at 9:25 AM

jkalmbach wrote Jun 4, 2010 at 10:11 AM

I do not understand... WHAT do you mean? WHAT is wrong?

ptorris wrote Jun 4, 2010 at 11:48 AM

The convert does not (seen in debug windows)!

ptorris wrote Jun 4, 2010 at 11:49 AM

The result is (attachment):
result_plaintext_converter_2.jpg

jkalmbach wrote Jun 4, 2010 at 3:15 PM

Are you sure that you are posting as "text/plain"?
Only in this case is the text/plain converter used!
You can show the debug windoe and only check the "Converters" checkbox. It should display something if you post an article! Please post this text here. If it does not display anything, you are posrting in text/html! And html will not be converted into html....

Also you can check the NNTP checkbox, then you will see WHAT your client is posting!

ptorris wrote Jun 4, 2010 at 7:32 PM

Post Ok with V27:

http://social.Answers.microsoft.com/Forums/en-US/answerssandbox/thread/7eef37d1-6243-44be-a62e-3acca4e3eba7#df18a015-c59a-4fcc-acf9-677a6088239e

FromClient: Re: V20:
V27 V27 /V27/

...

FromClient after conversion: Re: V20:

V27 V27 V27
...

// end

Post not Ok with V27:

http://social.Answers.microsoft.com/Forums/en-US/answerssandbox/thread/7eef37d1-6243-44be-a62e-3acca4e3eba7#56ffb51e-2fdc-4456-94e8-595c8c15fc40

FromClient: Re: V20:
with V27
3 : caractère gras en début de ligne (convert text/plain vs HTML)

3 : caractère gras en début de ligne (convert text/plain vs HTML)

FromClient after conversion: Re: V20:

with V27
3 : caractère gras en début de ligne (convert text/plain vs HTML)3 : caractère gras en début de ligne (convert text/plain vs HTML)



// end

Post not Ok with V27:

http://social.Answers.microsoft.com/Forums/en-US/answerssandbox/thread/7eef37d1-6243-44be-a62e-3acca4e3eba7#0b10aadc-6f8c-44ca-8d39-44c186b9ec00

FromClient: Re: V20:
3 : caractère gras en début de ligne (convert text/plain vs HTML)

[x] Retour ligne auto normalement cochée (MesNews text/plain

editor)

FromClient after conversion: Re: V20:

3 : caractère gras en début de ligne (convert text/plain vs HTML)



  [x] Retour ligne auto normalement cochée (MesNews text/plain editor)



// end

ptorris wrote Jun 8, 2010 at 8:45 AM

The problem seems to be resolved with the latest versions. Thanks. :)