And...... You forgot one.... People will say we shouldn't have used Fp in the first place. And that we are far better off to switch to EW now. But working day and night on web pages is unrealistic, even if we are "devoted" to our work. Oh, and Charles, if you still have charset=windows-1252 in your Fp code, and even if you still want to use Fp, that part should be charset=iso-8859-1 (Look up charset on Google for more info.) It isn't a hard fix to do with Find & Replace. But it means mindless clicking of "OK" to make the change on every page. Expect about 2 hours of click-click-click on a large site. This is another reason to have some things in Frontpage on a template. Hearing your list of all the tasks you have to do to switch to EW, well, it's daunting and sobering to say the least. Judy On Mon, Jan 4, 2010 at 12:18 PM, Charles Barnum <jcnreno@charter.net> wrote: > Experiment in Terror > > Here is what a person may have to go through if converting (I know, the > EW fans will say there is no converting) a FrontPage page in html to an > EW page in xhtml. > > 1—Open the page. Switch to Code View. > 2—Repalce the old head to a new head with > <!DOCTYPE html PUBLIC "-//W3C//Dtd XHTML 1.0 Transitional//EN" > "http://www.w3.org/tr/xhtml1/Dtd/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml"> > > <head> > > <meta content="text/html; charset=windows-1252" http-equiv="Content-Type" > /> > > 3—Remove the tag for any THEME that exists on that page. > 4—Select and Replace every <strong> tag using the Replace command. If > you don’t do this it may (does) produce a code error message for every > <p> tag and <td> tag. > 5—Remove all code for your Table except <table>. > 6—Open Design view. Select the table(s). Go to Table Properties. Select > the Alignment. Select the Float. Select the Cell Padding. Select the > Cell Spacing. Select the Width. Select the Height. Select the Border > size. Select the Border color. Select or do not select Collapse border. > Select the BG color if any. > 7—Then go back to Design View. Select all but one column of Cells. > Select Cell Properties. Select Horizontal Alignment. Select Vertical > Alignment. Select Rows spanned. Select Columns spanned. Select Border > Size. Select Border Color.(Do not forget to select the Border color even > if you selected Border color in the Table, or you may end up with the > old FP color for the cell Borders. Select Width and height or leave > blank. Then go back to Design View and select the last Column of cells > and do it for that batch. (Gosh, why not just select the entire table of > cells? Because EW may think you have selected the Table instead of all > of the cells and it may not make your changes. ) > 8—Return to Design View and select the entire page and click B in the > tool bar to make the text bold if that is what you use. > 9—Click Preview so you can see what the converted page looks like. I use > Mozilla preview setting because I want all Fire Fox users to see my > pages okay. > 10—All done? No. Remember I said I was converting from FP to EW from > html to xhtml. You will now have to click the Code Error detector. There > you will find code errors left over from the old FP days. You will have > to fix all of those errors. THEN, Click Compatibility detector. It will > show you incompatible code like: <div align="center"> saying “The WWW > regards this code as outdated.” You can fix those or leave them as these > types of incompatible code are apparently overlooked by most browsers. > 11--I then Optimize the code. > > I used only the tools supplied by EW to convert this page. There is > nothing done here using EW that I could not do using FP or any other > decent program. I know some will say, you should have had a DWT page or > this or that. But why does EW provide those tools if they are no good? > Building a new page from scratch does not have all of these problems, > but for those poor folks converting from an existing FP site, you will > be up night and day. > > I do not want an answer. I just want to point out some facts. > > Have a great day. > > Charles > > > ------------------------------- > To unsubscribe from the list, please send an email to > ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the > quotes in the subject and the body of the message > -- -- WASHINGTON COUNTY PA WEBSITES::: http://freepages.misc.rootsweb.com/~florian/ Coordinator of the Washington County PAGenWeb: http://www.rootsweb.com/~pawashin/
Judy, Good observations. I have a question however. I have EW set to xhtml. On a completely new page, the head created by EW reads as follows: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type" /> I copy that to Notepad and leave it there and never close Notepad and never turn off my computer so all my little notes are still there. On each old FP page, I open and manually remove the old head and paste the new head. You say I should use charset=iso-8859-1 You may be right as I do not even know what that means. But EW creates the head above mentioned which does not use charset-iso-8859-1. The pages work fine. I have also been told to use a different head. I think I better stick with the head EW uses. Anyway, I've already changed zillions of pages so I am not going to do it again and then upload all over again. Now, even after doing that, this nasty bit of code still remains: <meta name="Microsoft Theme" content="none"> or one of many like this: <meta name="Microsoft Theme" content="aftrnoon 1011, default"> depending on the theme I used on that particular page. Many can be removed on a universal search and replace but some remain to be manually removed when found. One last item for now. In almost all of my tables I have links. Having a link in a Table causes some problems when converting over. I believe that was mentioned in another post by Pat. One thing I have noticed is after resetting a Table's border colors, it looks fine in Design view. But 99.99% of the time when I go to Preview the old Cell border color shows up unless I have manually removed all of the Table characteristics manually in the code view. Then add my own. I have tried copy and paste but it does no good. I am going over my entire web site now looking for those tables that have different cell border colors from the Table border color and there are many. I have been two days trying to fix all the tables in Bernalillo Co. and I'm still not half way done. I just received a big cemetery survey. I'll be working on that for a few days. Have a good evening. I'm done for today. Charles J.A. Florian wrote: > And...... You forgot one.... > > People will say we shouldn't have used Fp in the first place. And that we > are far better off to switch to EW now. > But working day and night on web pages is unrealistic, even if we are > "devoted" to our work. > > Oh, and Charles, if you still have charset=windows-1252 in your Fp code, and > even if you still want to use Fp, that part should be > > charset=iso-8859-1 (Look up charset on Google for more info.) It isn't a > hard fix to do with Find & Replace. But it means mindless clicking of "OK" > to make the change on every page. Expect about 2 hours of > click-click-click on a large site. This is another reason to have some > things in Frontpage on a template. > > Hearing your list of all the tasks you have to do to switch to EW, well, > it's daunting and sobering to say the least. > > Judy > On Mon, Jan 4, 2010 at 12:18 PM, Charles Barnum <jcnreno@charter.net> wrote: > >
People will say we shouldn't have used Fp in the first place. And that we are far better off to switch to EW now. But working day and night on web pages is unrealistic, even if we are "devoted" to our work. elephants are best eat one bite at a time It isn't a hard fix to do with Find & Replace. But it means mindless clicking of "OK" to make the change on every page. Expect about 2 hours of click-click-click on a large site. why do that? first make sure you have a backup. In find and replace in replace tab - 'Find What' pane- insert the charset you want to find eg <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> in 'Replace with' pane <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> make sure under 'Find Where' - 'All Pages' are ticked Under 'Advanced' make sure 'Find in source code' is ticked then hit replace all a box will come up telling you this procedure cannot be undone hit ok and a window pane will come up at the bottom listing all the pages its found on and changed so why are you clicking one by one? If you think you might go wrong simply make a backup at that point in time ... you can always delete the site you just did the procedure on and do it again if something did not work.... thats why its best to back up three times one for experiments to see if they work however this works fine...why are you having a problem with it? Hearing your list of all the tasks you have to do to switch to EW, well, it's daunting and sobering to say the least. it is the way he's doing it! sorry but - spit Its actually fun ... and the housewives will understand this .... you know when you finish cleaning a room? well thats the feeling you get when you finish a site/page or whatever ... great satisfaction on a job well done. I love cleaning up sites... and I love finding faster and better ways to do it ... expression web (and fp 03 to a great extent) provides most of them, however we have found a few that makes quicker work in certain scenerios tina Expression Web Xmas/NY Giveaway 23rd Dec - 15th Jan http://www.frontpage-to-expression.com/expression-web-giveaway.html
My responses are in between. On Mon, Jan 4, 2010 at 6:24 PM, Tina Clarke <TinaClarke@accessfp.net> wrote: > People will say we shouldn't have used Fp in the first place. And that we > are far better off to switch to EW now. But working day and night on web > pages is unrealistic, even if we are "devoted" to our work. > == > > elephants are best eat one bite at a time > My response: Only if you like to eat elephants. ;-) > > It isn't a hard fix to do with Find & Replace. But it means mindless > clicking of "OK" to make the change on every page. Expect about 2 hours of > click-click-click on a large site. > == > why do that? first make sure you have a backup. In find and replace in > replace tab - 'Find What' pane- insert the charset you want to find eg > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> > in 'Replace with' pane > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > make sure under 'Find Where' - 'All Pages' are ticked Under 'Advanced' make > sure 'Find in source code' is ticked then hit replace all a box will come up > telling you this procedure cannot be undone hit ok and a window pane will > come up at the bottom listing all the pages its found on and changed > so why are you clicking one by one? > My response: While Fp2000 will find all occurrences, there is no universal Replace in Frontpage2000. The user must still click OK on each change. I've done it over the years, many times. And it takes 2 to 3 hours. > <snipped> > r list of all the tasks you have to do to switch to EW, well, it's daunting > and sobering to say the least. > === > it is the way he's doing it! sorry but - spit > > Its actually fun ... and the housewives will understand this .... you know > when you finish cleaning a room? well thats the feeling you get when you > finish a site/page or whatever ... great satisfaction on a job well done. I > love cleaning up sites... and I love finding faster and better ways to do it > ... expression web (and fp 03 to a great extent) provides most of them, > however we have found a few that makes quicker work in certain scenerios My response: Some housewives (and men too!) don't care much for housework---LOL And some of us do what we can to fix webpages but kinda hate to do "spring cleaning" for a website. That's what I was commiserating about with Charles. Judy