|
|
Posted by tshad on 05/17/05 00:50
"Beauregard T. Shagnasty" <a.nony.mous@example.invalid> wrote in message
news:dd6he.19139$3b4.7107@twister.nyroc.rr.com...
> tshad wrote:
>> "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> wrote in
>> message news:CfOge.27169$ia6.9287@twister.nyroc.rr.com...
>>
>>> Your 8pt font is also unreadable. We discuss why not to use
>>> Verdana, and not to use px or pt for font every day here. Surely,
>>> you've read a few of those threads?
>>
>> Again, this is what FP puts out there.
>
> Sounds like a good reason to dump it. :-)
>
>> I actually do use fixed sized fonts, but they are all in my style
>> sheets that I can change later. I just found that relative sizes
>> caused me no end of problems when dealing with data input screens
>> and getting things to line up.
>>
>> I actually use 10px, 12px and 14px:
>
> I always use 100% and have no problems at all. You must be doing something
> else wrong. Or, rather of course, FrontPage is doing something else wrong.
>
> Have we mentioned that IE users will not be able to resize your fonts if
> they have vision problems?
>
>> I also have them set at the same size as the graphic images I am
>> using that have the text in them to make them consistant. How do
>> you use a relative size font in a graphic image?
>
> A graphic image of text? Why not just use text? Unless you're showing
> mathematical formulae, or need a particular emphasized header, there is
> little reason to use a graphic of text.
>
>> Using standard out of the box browsers (IE, netscape, firefox) all
>> look fine. I have my screen at 1024.
>
> Screen size is unimportant. Browser window size is. My 1024 monitor
> usually has a browser window around 750-850px wide.
>
>> We have had multiple people look at some of the pages without
>> telling them how to set their browsers and they use different size
>> screen resolutions and they don't seem to have a problem with it.
>
> Again, screen resolution is not important.
>
>> I did figure out my problem, however.
>>
>> My example was missing the <p> tag, so it wasn't showing the
>> problem correctly. Now it does.
>>
>> It was the DOCTYPE that was causing the problem.
>>
>> In http://www.payrollworkshop.com/Samples/ParagraphTest1.htm you
>> can see this at the dop
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>> "http://www.w3.org/TR/html4/loose.dtd">
>>
>> As soon as I took the 2nd line out it works fine in all browsers.
>> As you can see in
>> http://www.payrollworkshop.com/Samples/ParagraphTest1.htm
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
>
> The page still has the complete doctype. In fact, I think I recall that an
> incomplete doctype will still toss browsers into quirks mode.
>
>> I found that not only did it have a large box around it, but the
>> first example doesn't indent the text and the 2nd one does.
>
> ..and there are still no units on your paragraph margin.
> Still 15 cheeseburgers.
>
> --
> -bts
> -This space intentionally left blank.
[Back to original message]
|