Hi Ron and Gordon
please see below:
From: "Ron Klotz Zellhoefer" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: 26 May 2005 18:51
Subject: Re: [LegacyUG] Pedigree webpages.
* RE-Applying a theme to set colors, fonts, backgrounds, borders, etc etc.
This can be pretty much done through legacy.However if one wants the
facilities of an external css then it is necessary to change all colours
(text and background). I do not expect any change in this as many people
would not wish to make the change at all and it is straight forward to do
using batch changes.
(continued below)
* RE-Adding borders, which contain icons and links to many other internal
URLS, and gives uniformity to my website. As my website's left border
contains the bulk of those links, it becomes a real problem when the
Legacy output becomes screwed up just because of adding a left border, so
this is a priority item on my Legacy WishList! As things stand at
present, I forgo using my standard left border because of this. Perhaps
on this thread we'll discover how to correct this, then hand Millennia the
solution and ask them to fix their programming on html output. It's
strange that this occurs only on Legacy's Pedigree output format!
* At last one gets to spend the usual hours checking the new set of
webpages, and fine-tuning.
* Finally it's time to republish, which Frontpage does very nicely now.
Frontpage has a search/replace tool which can (usually) be used to
mass-rewrite segments of the html to all pages (provided it's unique, of
course!). While that does require more processing time, it's not
difficult. My point here is that such would be unnecessary if the Legacy
output were correct in the first place.
I could not agree more. I would appreciate your confirmation that the
changes I suggested work for your site (I have left them in this reply,
below) in the way that you wished.
Unfortunately they do not lend themselves to a batch change as the tags are
common throughout all pedigree style sites and their position varies
depending on the number of antecedents.
There are also some minor errors in the code for sources when they are
included at the end of a page (as I do) but these seem comprise not closing
of tags properly so make no real difference.
Ron Ferguson
Hi Ron,
There seems to be 3 main changes to the Legacy source code which need
to
be made when it is wrapped in another table and from what you have
observed it also seems to apply in other circumstances.
These are difficult to identify in words but I will have a go working
from the bottom up!
1) Just above the line <.td width="590"......> and below the line
<./table> there is a <./tr>. This should be changed to <.table>
2) Moving up: Just above the line <.td width="580"......> and below the
line <./table> there is a <./tr>. This should be changed to <.table>
3) Between there and the arrows there are two lines:
<.tr>
<./tr>
Both should be deleted.
These changes have to be made on every page. I cannot promise that this
makes the code absolutely correct but at least it works for me. You can
have a look at the alterations on any pedigree page on my web site (cf.
with the Legacy code)
Ron Ferguson
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 267.2.0 - Release Date: 27/05/2005
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
