User:SOTO/Forum Archive/The Reference Desk/@comment-188432-20130505035914: Difference between revisions

From Tardis Wiki, the free Doctor Who reference
m
Bot: Automated text replacement (-'''User:(SOTO/Forum Archive)/(.*?)/\@comment-([\d\.]+)-(\d+)'''\n([\s\S]*)\[\[Category:SOTO archive posts\]\] +\5\2/\4-\3, -'''User:(SOTO/Forum Archive)/(.*?)/\@comment-(.*?)'''([\s\S]*) ?\{\{retitle\|///(.*?)\}\} +{{retitle|\2/\5}}\n'''User:\1/\2/@comment-\3'''\4)
(Bot: Automated import of articles)
 
m (Bot: Automated text replacement (-'''User:(SOTO/Forum Archive)/(.*?)/\@comment-([\d\.]+)-(\d+)'''\n([\s\S]*)\[\[Category:SOTO archive posts\]\] +\5/-, -'''User:(SOTO/Forum Archive)/(.*?)/\@comment-(.*?)'''([\s\S]*) ?\{\{retitle\|///(.*?)\}\} +{{retitle|\2/\5}}\n'''User:\1/\2/@comment-\3'''\4))
 
Line 1: Line 1:
'''User:SOTO/Forum Archive/The Reference Desk/@comment-188432-20130505035914'''
{{retitle|The Reference Desk/What is the Crimson Horror?}}
Gatiss is a little vague on this one.  At time he indicates the Crimson Horror is the [[red leech]].  At other times it's the venom.  And at still others, it's the disease imparted by the venom.  At present, [[crimson horror]] redirects to [[red leech]], and [[the Crimson Horror]] redirects to the episode page.  That's almost certainly not gonna cut it.  How should we best handle these various meanings?  {{retitle|///What is the Crimson Horror?}}
Gatiss is a little vague on this one.  At time he indicates the Crimson Horror is the [[red leech]].  At other times it's the venom.  And at still others, it's the disease imparted by the venom.  At present, [[crimson horror]] redirects to [[red leech]], and [[the Crimson Horror]] redirects to the episode page.  That's almost certainly not gonna cut it.  How should we best handle these various meanings?   
<noinclude>[[Category:SOTO archive posts]]</noinclude>
<noinclude>[[Category:SOTO archive posts|The Reference Desk/20130505035914-188432]]</noinclude>
Tech, Bots, Bureaucrats, emailconfirmed, Administrators
228,839

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.