What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 133 Stack Exchange communities.

I just tried to paste this URL in a comment:

http://guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/common/primitives/Ints.html#asList(int...)

but it comes out like this (note the trailing "...)" is no longer included):

http://guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/common/primitives/Ints.html#asList(int...)

Since the . and ) are part of the URL, they should be parsed as such.

This happens in questions and answers too, but in Q&A backslash escapes can be used as a workaround. In comments they cannot.


Loosely related: URLs in comments bugs

However in this case I do want the URL to be linkified. The URL is valid but is incorrectly being truncated.

share|improve this question
    
Try some of the techniques here: meta.stackexchange.com/questions/13501/… –  Jon Seigel Apr 23 '10 at 12:53
    
@Jon Seigel, yes I often use that workaround when linking to javadocs from answers. Sadly it does not work for comments. –  Perpetual Motion Goat Apr 24 '10 at 23:24
1  
The second technique at Jon's reference, percent-encoding the reserved parentheses, #asList%28int...%29, makes the parser understand the non-reserved dots as well: guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/… –  Arjan May 23 '10 at 14:53
    
Oh, this is an old question. Maybe it even works without percent-encoding nowadays, but I doubt that: guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/… –  Arjan May 23 '10 at 16:46

2 Answers 2

up vote 0 down vote accepted

You'll have to encode the parens, or do it in an answer where there is more comprehensive linking support.

share|improve this answer

This is a perennial problem with autolinking, and there's no one good answer. It's quite common to have trailing punctuation that isn't part of the URL (so I can do things like this, linking to http://www.example.com/...). In my experience (albeit on a non-technical forum), trimming the trailing characters fixes more comments than it breaks.

One way forward that works well for me is to count ) as a trailing-character-to-remove only if there's a ( character earlier in the URL. Don't know if that's feasible for how the comment linker works though.

share|improve this answer
    
I don't buy that argument. It's like having the spell checker in MS Word forcibly changing "escapade" to "escaped" without the option to disable it, just because the latter is more frequently used. Your URL is wrong (actually it's valid, because the trailing dots are part of the URL, but the URL you entered is not the one you intended.) and correct URLs shouldn't be made impossible to enter just so that some incorrect ones can be auto-corrected. –  Perpetual Motion Goat Apr 24 '10 at 23:29
    
In principle I agree, but the reality is not trimming the ends breaks a lot of links that normal users type. It's not impossible to enter URLs ending with . using the extended syntax in comments... it's just unfortunate that ) is used as the delimiter in this syntax so you can't have it in a URL at all. –  bobince Apr 27 '10 at 16:45

You must log in to answer this question.