Eloy - I did some quick testing and here is what I found:
*Double quote: Without s, does not autolink. The double quote " character is accepted in the resource name and does not get changed to an html entity. Works with s.
Single quote: Works fine without s. OK when entered as ' in resource name (does not get converted to html entity in resource name). Works with s.
*Ampersand: Without s, does not autolink. The & character is accepted in the resource name and does not get changed to an html entity. Works with s.
Greater than: Works fine without s. OK when entered as > in resource name but gets converted to html entity > which causes it not to work with s.
Less than (html entity required): Works fine without s provided less than is entered as an html entity < otherwise the text is truncated at that point and does not display in the resource name. The html entity gets converted by s and returns < rather than < Since this is truncated by default (without using html entity) I am less concerned with it not working.
In summary, adding the s call will fix the double quote and ampersand problem (provided those characters are not entered in the resource name as html entities which I think would be less common). It does not effect single quotes (provided they are not entered as html entities in the resource name). If the less than character were to have been entered as an html entity then it works without s but adding s breaks it but considering that the less than character when entered normally causes the resource name to be truncated at that point I would say that it is not an accepted character for a resource name and therefore not a condition we necessarily have to worry about. Similarly for the greater than character which can be entered in the resource name but automatically gets converted to an html entity. In that case, without s it works and the s breaks it. I think if we were to document that the resource name should not contain < or > characters we would be OK. Given that the ampersand and double quotes are more likely to be used, I think this would fix more problems than it causes but I leave it to your judgment to sort out how best to deal with this.
Peace - Anthony