I've written a regular expression that automatically detects URLs in free text that users enter. This is not such a simple task as it may seem at first. Jeff Atwood writes about it in his post.
His regular expression works, but needs extra code after detection is done.
I've managed to write a regular expression that does everything in a single go. This is how it looks like (I've broken it down into separate lines to make it more understandable what it does):
1 (?<outer>\()?
2 (?<scheme>http(?<secure>s)?://)?
3 (?<url>
4 (?(scheme)
5 (?:www\.)?
6 |
7 www\.
8 )
9 [a-z0-9]
10 (?(outer)
11 [-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]+(?=\))
12 |
13 [-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]+
14 )
15 )
16 (?<ending>(?(outer)\)))
As you may see, I'm using named capture groups (used later in Regex.Replace()
) and I've also included some local characters (čšžćđ), that allow our localised URLs to be parsed as well. You can easily omit them if you'd like.
Anyway. Here's what it does (referring to line numbers):
if
statement that says: if "sheme" was present then www. part is optional, otherwise mandatory for a string to be a link (so this regular expression detects all strings that start with either http or www)http://
or www.
should be either a letter or a number (this can be extended if you'd like to cover even more links, but I've decided not to because I can't think of a link that would start with some obscure character)if
statement that says: if "outer" (braces) was present capture everything up to the last closing braces otherwise capture allFirst and last line used to have \s*
in them as well, so user could also write open braces and put a space inside before pasting link.
Anyway. My code that does link replacement with actual anchor HTML elements looks exactly like this:
value = Regex.Replace(
value,
@"(?<outer>\()?(?<scheme>http(?<secure>s)?://)?(?<url>(?(scheme)(?:www\.)?|www\.)[a-z0-9](?(outer)[-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]+(?=\))|[-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]+))(?<ending>(?(outer)\)))",
"${outer}<a href=\"http${secure}://${url}\">http${secure}://${url}</a>${ending}",
RegexOptions.Compiled | RegexOptions.CultureInvariant | RegexOptions.IgnoreCase);
As you can see I'm using named capture groups to replace link with an Anchor tag:
"${outer}<a href=\"http${secure}://${url}\">http${secure}://${url}</a>${ending}"
I could as well omit the http(s) part in anchor display to make links look friendlier, but for now I decided not to.
I would like my links to be replaced with shortenings as well. So when user copies a very long link (for instance if they would copy a link from google maps that usually generates long links) I would like to shorten the visible part of the anchor tag. Link would work, but visible part of an anchor tag would be shortened to some number of characters. I could as well append ellipsis at the end of at all possible (and make things even more perfect).
Does Regex.Replace()
method support replacement notations so that I can still use a single call? Something similar as string.Format()
method does when you'd like to format values in string format (decimals, dates etc...).
You can split ${url}
to two capturing groups - urlhead
, with the number of characters you want to display, and urltail
with the rest. Here's an example with 10 characters; this is somewhat simplfied to remove the condition, the last (?<ending>(?(outer)(?=\))))
should take care of that - it backtracks and captures the last )
when needed:
(?<outer>(?<=\())?
(?<scheme>http(?<secure>s)?://)?
(?<url>
(?(scheme)
(?:www\.)?
|
www\.
)
[a-z0-9]
[-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]{1,10}
)
(?<urltail>[-a-z0-9/+&@#/%?=~_()|!:,.;čšžćđ]+)
(?<ending>(?(outer)(?=\))))
Note that I've also changes outer
and ending
to be lookarounds, so they are not captured and replaced. The replace string in this case looks like:
<a href=\"http${secure}://${url}${urltail}\">http${secure}://${url}</a>
You would have to use the Regex.Replace overload that uses a MatchEvaluator
, a delegate that constructs the replacement text for you.
See here: http://msdn.microsoft.com/en-us/library/system.text.regularexpressions.matchevaluator.aspx
Technically, it is possible with just regexes, by doing what Kobi suggests. I'm not sure I'd want to ask anybody (including yourself after a few months) to maintain that regex however.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With