Page history
Talk:Find URI in text
9 January 2012
8 January 2012
rosettacode>Dgamey
→Expected Output Needed
m+444
rosettacode>EMBee
→Unicode and URIs
m−2
rosettacode>EMBee
→Expected Output Needed
+494
rosettacode>EMBee
→Unicode and URIs
+840
rosettacode>Dgamey
→Expected Output Needed: whats encoded
m+166
rosettacode>EMBee
→Expected Output Needed
+373
rosettacode>Dgamey
→Expected Output Needed: devil in the details
m+229
rosettacode>Dgamey
→Unicode and URIs: - extra word
m−5
rosettacode>Dgamey
→Unicode and URIs: punct
m+1
rosettacode>Dgamey
Unicode and URIs
+1,047
rosettacode>EMBee
→Expected Output Needed
+1,146
rosettacode>Dgamey
→What actually parses as a URI may not be what is intended by the task author: grammar
m+1
rosettacode>Dgamey
→What actually parses as a URI is not what is intended by the task author: tweaked heading is -> may
m+5
rosettacode>Dgamey
→What actually parses as a URI is not what is intended by the task author: and Expected Output Needed
+856
rosettacode>EMBee
→What actually parses as a URI is not what is intended by the task author
+998
rosettacode>Dgamey
Task and RFC are not aligned
+736