ThompsonShapiro
commented
3 years ago That's not high on my priority list -- but, with one caveat, would make rewriting those old files that were generated by Word, Excel, or SeaMonkey, easier.
The caveat is that almost always, with only one exception I can think of,
when there's an occurrence of
The one exception I know of is . Removing that removes a blank
line from the screen with most browsers -- which may or may not be
important. The safe thing to do is rather than remove that pair is to
replace it with
.
One thing you could do, which I hesitated to write up as an issue because it seems petty, is a minor cleanup of the cemetery pages (which in their genesis started out as a single, huge webpage created by Excel from a giant spreadsheet.
As a result, many of our CampbellCemetery HTML files contain table cells
such as the following:
1808
The sdval and sdnum clauses are clutter that could be removed with no impact on the screen's appearance. They bug me, but are harmless except for adding a millisecond or two to the page's load time and adversely effecting the data limits a cell phone user may have on their service agreement. But that line could safely be changed to <td align="RIGHT">1808.
All the Cemetery pages need a major overhaul, which I will do in conjunction with moving their data to MySql tables on Bluehost. But that will probably be several months away.
I think my highest priority right now is replacing all our HTML files on RootsWeb with the "redirect" versions. RootsWeb will probably eventually figure out what we're doing and stop hosting the old site, but that's OK. Those who visit while it's there will learn of the move. And the more people who visit our new site, the more it will boost us in their rankings. Maybe only from 10003rd to 9997th, but every bit helps.
Family Tree Links One of the most helpful changes you could do next is to address changing as many as possible family tree links to point to WikiTree rather than wc.rootsweb. My nephew, Charles Shapiro, kindly set up my original GitHub repository for that purpose and wrote a Linux script to change a file, the idea being that once that worked OK a higher level script would run that for all the HTML files in the directory. The simple table lookup I proposed had a data problem. For reasons we can discuss later, I'd like to add an additional column to my spreadsheet, but the first column would continue to be the one used for doing the lookup.The "Try to replace" script should be run periodically (or routinely). The first time it's run in production run, most of the links to wc.rootsweb locations will be replaced. So even though the spreadsheet contains 1,400+ rows, the number of lookups will shrink steadily, Whenever I add someone to WikiTree (or discover they are already there. I update the spreadsheet. Many of the folks in the tree at wc.rootsweb are unlikely to ever be added to WikiTree
On Wed, Apr 28, 2021 at 2:45 AM Robert M Lugg @.***> wrote:
In some cases, there are multiple, unnecessary tags. Remove all but one when nested.
@ThompsonShapiro https://github.com/ThompsonShapiro , should I change the tag into something else automatically? Sorry if you already told me.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/campbellluggblackwell/campbellluggblackwell.com/issues/19, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKVWEB4FTEIWR3HDKI5Q73TK6VI5ANCNFSM43WNQDBQ .
robertlugg
In some cases, there are multiple, unnecessary tags. Remove all but one when nested.
@ThompsonShapiro , should I change the tag into something else automatically? Sorry if you already told me.