Shorter link representation

[GoogleCodeExporter]

http://www.duh.com is detected automagically and converted, with the html 
target, in 
<A HREF="http://www.duh.com">http://www.duh.com</A>

Would not it be better to have :
<A HREF="http://www.duh.com">www.duh.com</A>

Original issue reported on code.google.com by fgalla...@gmail.com on 22 Mar 2013 at 3:44

[GoogleCodeExporter]

The http:// is part of the URL, we should not hide it by default. Being too 
smart is not a good thing in my opinion, we'll end up doing things the user do 
not want.

In this case, a simple postproc handles it all:

%!postproc: '(?i)(<a href="http://(www.*?)">).*?</a>'    '\1\2</a>'

Filters are the best solution to this kind of simple problems. Those who want 
that feature, simply paste the filter in their main config file.

Original comment by aureliojargas@gmail.com on 22 Mar 2013 at 12:59

[GoogleCodeExporter]

This is a logical evolution :
http://mashable.com/2010/04/18/google-chrome-ditches-http/

I would like txt2tags be useful by default, for a *not* advanced user.

Original comment by fgalla...@gmail.com on 22 Mar 2013 at 1:25

[GoogleCodeExporter]

firefox and chrome annoys me enough with such behavior (and now firefox mobile 
even hide URL and substitute it with the title in the Meta header, it's very 
good to promote phising), sorry I don't think it would be a good idea for 
txt2tags to copy them on this. 

What about ftp? Should we also hide it as well? Or hide only http but not https 
and ftp? It's not very logical. 

The last links on mashable also says this decision is contested by many people 
(and I've also complained myself on the chrome bug tracker)

I don't think it would help txt2tags to be easier for normal user, besides 
markdown has so much more users than txt2tags and see how much badly designed 
it is and so unfriendly it is.

Original comment by eforg...@gmail.com on 22 Mar 2013 at 9:04

[GoogleCodeExporter]

could we close this issue now?

Original comment by eforg...@gmail.com on 13 May 2013 at 2:35