Hi,
I am still seeing two different navbars in IE7 and FF3. In FF3 I have a link
to 'Restaurant reviews' and that is not in the IE7 view. Do you get the two
different navbars? Did you perhaps leave any old Publisher files on the
server? The next time you republish, delete the index.htm file and the
index_files folder from the server before you upload new files. Don't trust
that the old site files are being overwritten. Let's set aside that mystery
for the moment, though I would appreciate it if someone else in the group
would confirm my experience by viewing the home page
http://www.rus-res-rev.ru/ in FF and IE and letting me know if it is only my
experience.
Now as to the reader that is supposedly using IE7 to view you site, I am not
getting the same experience. Your home page looks almost exactly the same in
IE7 and FF3 for me with a slight variation in how large the text and line
spacing is rendered.
I would suggest this general approach to fixing spacing and formatting
issues in text boxes that you might encounter between the different browser
views. Click in the text box and either use the keys Ctrl + A, or go to Edit
Select All to select all the text within a text box. Then > Format >
Styles and Clear formatting. This will strip out any and all special line
spacing or paragraph formatting. Provided that you are using a web friendly
font, this text box will render pretty much the same in all browsers. Test
it in IE and FF to confirm. Once you see how the text is going to render,
then you can adjust your layout accordingly. You can change the font size or
the font to another web friendly font, but if you want to add indents or any
other kind of special formatting, you should test as you go in both IE and
FF. There are things you can do, and some things you can't. Remember that as
I said before there are print formatting techniques that simple will not
translate to cross browser compatible html. However, generally if your pages
look good and work correctly in both IE and FF, then the pages will also
work correctly in Safari, Opera and Chrome which means that the pages will
work in all the major browsers.
So, I would apply this approach to the center column text on your home page
and adjust your layout accordingly, and see if the pages render more closely
in FF and IE.
I also did not see the same thing that your tester did on your Contact Page.
I couldn't see any substantial differences in how the page was rendered in
IE and FF, but once again, you might want to strip out the "styles".
And by the way, it isn't clear to me that you are testing your site with
both IE and FF yourself. If you have not done so before now, download and
install FF:
http://www.mozilla.com/en-US/firefox/ It is a relatively small
download and an easy install. Just be careful that when you are given the
choice, to opt out of making it your default browser. And once you have it
installed, you do not need to upload your Publisher files to test them with
FF. When you Publish to the Web and produce your web files, direct them to
your local computer where you can easily find them. I put them in a
'TestHTML' folder on my desktop. Then you need only right click the
index.htm file > Open with > and choose FF. You can also open the
index_files folder and test the other .htm files/ pages of your site.
Ok, now that you have FF installed, and know how to direct your web files to
your local computer to make them easy to test as you go, you can go to each
page of your site and view and test them. Use the general technique I
suggested above to strip out all paragraph, line and text formatting out of
each text box that does not render as you expect or want. Work through your
publication and you should be able to resolve most of the formatting issues.
As you discover anything that you cannot fix, then post back with the
specifics and we will help.
Also be sure to run the Design Checker under Tools at some point. This will
help identify some potential problems.
One more comment before I go on. I would not use the gradient background if
I were you. Publisher chokes a bit with gradients and you should notice when
you test your site in both IE and FF that while it is acceptable in IE, it
is too dark in FF and makes the text difficult to read. If you want to keep
the black and gray theme, just switch to a sold light gray background. It
may not be as "cool" but it will be a whole lot easier to read and that is
really more important. Sometimes it is better to keep your pages simple...vs
cool.
Now as to your tester that was supposedly testing with IE7. I suspect that
they are actually testing with IE8, because of the comment about not being
able to view the navbar. If you have been reading other posts in the group,
you will know that IE8 does not render any 'grouped' design elements, and
this includes the navbars. That is why I suspect your tester is actually
using IE8. I am running out of time this morning so I am going to paste some
boilerplate about this issue and how to resolve it. If it isn't clear we can
discuss it more later but I hope this at least gets you started on tweaking
your layout and formatting. It may sound like a lot of work, but it really
is not going to take that long to tweak your pages so that you get good
cross browser compatibility.
-----------
The only compatibility issues with Publisher 2003 and 2007 and IE8 RTW
reported thus far are problems associated with 'grouping'. Any design
elements that are 'grouped' together, which includes the Publisher wizard
built navbars, do not render when you view the web page in IE8 . The fix in
general is to ungroup the elements. There is both a manual fix to these
issues and a Service Patch that has been issued to fix it.
Reference: Navigation bars and other content is missing from Publisher HTML
output in Internet Explorer 8:
http://support.microsoft.com/kb/969705
A manual method of fixing this grouping issue:
Prior to uploading your pages find all text boxes and other design elements
that are grouped together and ungroup. You can save those changes to your
publication. Then make a copy of your publication by doing a 'File > Save
As' and in this copy go to each page > Edit > Select All > Arrange >
Ungroup. This will ungroup the Publisher built navbar and disconnect it from
the wizard, and the navbars will render correctly in IE8. 'Publish to the
Web' from this copy of your publication. When you want to make further
changes in your web, go back to the original Publisher file, make the
corrections there, save your changes, and again make a copy, ungroup the
navbars and produce new web files for uploading. The advantage of this
workflow is that you will not have to rebuild the navbar if you choose to
add a page to the navbar. If you do not need to add a page, you can leave
the navbar ungrouped and skip the step of saving a copy.
This is also fixed with the Office 2007 SP2:
Reference: Description of 2007 Microsoft Office Suite Service Pack 2 (SP2)
and of Microsoft Office Language Pack 2007 SP2:
http://support.microsoft.com/?kbid=953195
The usual caveat also applies. While I would never recommend to anyone that
they not install any security or service patch, when you install service
patches there can be unintended consequences. You might fix one thing only
to break something else. While I have not had any problems on my test
partition there have been other people who have posted about problems
opening Pub 2007 files after installing the Office 2007 SP2.
http://support.microsoft.com/?kbid=953195
also lists some of the known issues along with some of the things this patch
fixes in Office 2007 applications.
If it were me, I would probably ungroup the navbars manually rather than
install the SP2 for the short term, and wait until MSFT debugs the Office
2007 SP2, rather than risk not being able to open pre-existing Publisher
files. I have not installed SP2 on my production machines...