|
| ||||||
Subj: At the moment I smell largely of varnish. Low oudor varnish. Posted: Tue Dec 15, 2015 at 09:33:14 am EST (Viewed 789 times) | Reply Subj: It's those sharp plot twists that you can cut yourself on. And then you smell of blood. Posted: Tue Dec 15, 2015 at 08:16:45 am EST (Viewed 4 times) | ||||||
Quote: On a technical matter, I've been trying to update the archived material on The Hooded Hood's Homepage of Doom. I notice that a lot but not all of the pages I call up from older parts of the PVB site have garbled codes instead of speech marks, apostrophes and ellipses; e.g. http://parodyverse.strike-two.com/app/show.php?msg=parodyverse-2011042616263265&layout=thread It looks like these are things like smart quotes (generated by Word, amongst other things). The only thing you can really do is identify the exact binary representation of the character in the offending web page, and do a search and replace using that. Also, you need to replace the longer strings before the shorter ones in case the the shorter string appears within the longer one - that will really muck things up... It may be possible to fix this by switching the page character set but it hasn't worked for me so far in my tests. Quote: Another issue is that the latest pages on the site must call up background in a different way, because ported to my site they all have white default backgrounds; e.g. http://www.chillwater.org.uk/HH/hhstories/untold%20tales%20of%20ll%20348.htmThis one is easy, by the look of it... Each HTML page has a {body} tag in it - this needs to be changed to {body bgcolor="black"}. (The braces should be angle brackets, but they won't render properly, and I can't remember how to force it) When doing the search, make sure the strings are specified with both open and closing angle brackets just in case the body tag already has other elements (which will usually include a bgcolor element) Quote: My attempts to globally edit the rogue text using a find/replace programme have only had moderate success and have actually screwed up other, older, already-working archived pages. Given the problem occurs on an estimated 1,300 of the 4,500 pages on my site I'm not keen to try manual individual fixes. Any ideas?Depends on how you are doing the search and replace, and exactly what is going wrong with the working pages. If it is a straight file-age-related thing then you could copy the offending files to a working directory, update them, then copy them back. As noted, you may also be hitting the case where some of the odd strings are subsets of the other - for example if one code was ABCD and the other was ABC and you needed to map ABCD to WXYZ and ABC to MNO, you would have to remap ABCD first. If you remap ABC first you would end up with a lot of MNODs. | |||||||
