Re: 96 DPI /120 DPI conflict - a possible solution

I'll try and get my head round your HTML solution but my coding skills are
minimal - thats why I started using Publisher. The image degradation you are
experiencing in Firefox are not nessecarily the result of grouping the
objects. Firefox can be very poor at rendering Publisher objects. Subtly
shaded backgrounds in Publisher can end up looking like checkerboxes in
Firefox.

Thanks

Robert

"Shaun.Hurd@xxxxxxxxx" wrote:

Hi All,

I'm just a newbie to this whole website/Publisher business, but after
having some problems displaying our new website on different PC's I
stumbled across this newsgroup - which has been an absolute mine of
information (thank-you all!) I have also been having problems getting
our website to display properly on 120DPI widescreen laptops. I tried
grouping all of the objects on each page as you have suggested, and
although it improved the layout in IE7, I found that it was still not
identical to the original 96DPI layout. The other downside (as you
alluded to, Robert) was that all of the text-based hyperlinks
disappeared in Firefox. The quality of the text and images were also
degraded when viewed in Firefox (something to do with the grouping of
objects?).

However, after a bit of playing around with the HTML code (which I'm
also new to), it looks to me like one of the problems is with the way
that objects are positioned on-screen, using either point or pixel-
based measurements. For example, to display a particular image on our
website, Publisher 2007 generated the following code:

[if gte vml 1]><v:rect
id="_x0000_s1273" style='position:absolute;left:293.25pt;top:
136.5pt;width:312pt;height:57.21pt;
...
</v:rect><![endif]
[if !vml]><span style='position:absolute;z-index:164;left:
391px;top:182px;width:416px;height:76px'>
<img width=416 height=76 src="index_files/image3451.gif"
v:shapes="_x0000_s1273">
</span><![endif]

So from my novice viewpoint, it looks like if VML is used (in IE6 or
IE7, but not Firefox?) then the image is positioned using pt-based
coordinates

("left:293.25pt;top:136.5pt;width:312pt;height:57.21pt")

but if VML isn't used then the image is positioned using pixels

("left:391px;top:182px;width:416px;height:76px").

I found that if I manually went through the HTML code and replaced the
"left" and "top" point coordinates in the VML reference with pixel
coordinates, that the page then displayed correctly at 120DPI. So in
the previous example, I changed the first part of the code to be:

[if gte vml 1]><v:rect
id="_x0000_s1273" style='position:absolute;left:391px;top:
182px;width:312pt;height:57.21pt;
...
</v:rect><![endif]

Note that I didn't change the "width" or "height" scaling factors. I
also didn't have to reposition every object on the page - only the
textboxes and pictures, but not the lines. Obviously this solution
isn't appropriate for a huge site, but for my purposes it only took a
short period of time to complete (our site consists of only 7 pages).
But it looks to me like a simple change to the engine generating the
HTML code would fix a lot of the display problems that are occurring.
And as people have commented before, this is only going to become more
of an issue in the future with an increasing uptake of higher-res
screens.

Shaun


.

Relevant Pages

  • Re: Is Publisher 2003 an effective way of creating and managing a
    ... Why is it bad to use these programs to produce proprietary html code, ... for years -- until Firefox came along. ... Web designers of the world, who were expected to design separate sites ... Word and Publisher are primarily programs for print ...
    (microsoft.public.publisher.webdesign)
  • Re: Is Publisher 2003 an effective way of creating and managing a
    ... But I honestly thought that when I generated "filtered HTML", I was creating standards compliant webpages, and my displeasure comes from now learning that this wasn't the case. ... But if they look like garbage in Firefox, they are really somewhat useless. ... Besides, it isn't just Publisher pages that are having problems, so do some FP pages and code produced by lots of other non MSFT programs. ... and require two different mindsets and design approaches. ...
    (microsoft.public.publisher.webdesign)
  • Re: Is Publisher 2003 an effective way of creating and managing a
    ... programs should not be able to output in html. ... The code produced by Publisher may be more bloated than FP code, ... designed to take advantage of IE technology and in many web design purists ... for years -- until Firefox came along. ...
    (microsoft.public.publisher.webdesign)
  • Re: Is Publisher 2003 an effective way of creating and managing a
    ... changing Publisher or Word to produce more "compliant" code. ... you can get your design and layout to work in those two browsers, ... If you are willing to learn the basics about HTML coding and CSS, ... for years -- until Firefox came along. ...
    (microsoft.public.publisher.webdesign)
  • Re: body text at bottom of page
    ... > make the changes after designing and changing in publisher. ... I recommend against making edits to Pub html because the changes are lost ... > text to the top of the HTML code without changing the screen layout. ... and you have no control over what cell of what table it is coded. ...
    (microsoft.public.publisher.webdesign)
Quantcast