Casual Articles
#1 in Business Subscribe Email Print

You are here: Home > Internet and Businesses Online > Web Design > Webpage Creation in Dreamweaver - How I Deal With Font Conflicts

Tags

  • sheet
  • cascading
  • sometimes
  • clean definition
  • unsullied contain
  • online marketing

  • Links

  • Do You Talk Too Much?
  • Muscles Don't Turn Into Fat!
  • Writing For The Web: How Good Copy Becomes Bad Marketing
  • Casual Articles - Webpage Creation in Dreamweaver - How I Deal With Font Conflicts

    One Bad Apple
    One Bad Apple I know what you are thinking but no, I am not doing a tribute to Michael Jackson and the Jackson 5.  Although I will admit that their hit song from the 70's keeps rolling around in my mind as I type this.  While the Jackson Five might have believed that "One bad apple can't spoil the wholent-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers

    Learn More About The Evolution Of Blog And Bloggers
    Ever since the introduction of blog development tools like Blogger, Pitas etc. in 1999, the personal publication tool weblog or simply blog has undergone many transformations. In the infant stages, until 2001, blogs were viewed as personal publishing platform where one can post his or her experiences, complaints, happy moments and pet peeves. Since it world business community has identified the potential of blogs to harness as a powerful marketing tool. Today blogs don’t confine to letters and words. You can find photo blogs (where one can publish photos), audio blogs, also called radio blogs where users can download and listen to audio messages or music and video blogs or vlogs where video files are published.Majority of blogger platforms today allows the users to publish syndication feeds (RSS or Atom). The feeds are especially helpful for ardent blog readers to keep in touch with the latest updates of a blo
    Dreamweaver would seem to have become the platform of choice for website designers. Simple enough for beginners to master to a workable level and sophisticated enough to keep the master designers coming back.

    But it has some very, very annoying conflict issues that can test your hold on sanity.

    I ran across this again today so I thought I'd write about it in case someone else finds it useful.

    I am by no means a master web designer. I am in fact an Internet MLM Marketer. Websites are a tool to me, not a profession. I fumble my way around bringing websites to life and in the process I run into some very frustrating issues that just don't seem to want to get fixed. Things like: how do I get an mpeg video clip to run in a webpage; my text formats differently in Firefox versus Internet explorer; font changes refusing to take; tables getting screwed up etc. etc.

    And there just doesn't seem to be anyone out there who can help me without paying an immense fee for their service. So I struggle along on my own until I finally crack the code thinking: "There must be a better way."

    Ever been there?

    Well I can't help you with really intricate stuff, but here are some of the things that I have found will save me, and hopefully you, a lot of headaches.

    If you're a pro then this article isn't for you.

    This is for the beginner like me who still from time to time struggles to get a website up and running smoothly. So if you're a beginner read on.

    So there you are--you're sitting there with the blank Dreamweaver page in front of you.

    What are you going to do first? Getting it to work right is all about doing it right the first time. Begin as you intend to continue.

    Here's what I do ,and don't for a moment think this is gospel (maybe there's an easier way)--its just what I find keeps me out of trouble.

    Where fonts for your text are concerned you are best to start by creating a CSS Style Sheet. CSS stands for Cascading Style Sheet and can help keep you out of trouble with fonts that can suddenly go crazy on you. Now this is not the only use of CSS--in fact its amazingly versatile in regard to graphics etc.-- but lets just stick to fonts.

    Well get to how to set up a CSS sheet in a follow up article, but the main thing is to NEVER, and I mean never, designate a font that is not listed in your CSS sheet unless you know how to get out of the ensuing mixup. This will help keep you out of lots of trouble with fonts.

    There is a great difference between what you see on your HTML editor (which is what Dreamweaver really is--although very sophisticated) and what you see on your web page when you test it as an HTML file on your screen.

    And it can get worse when you actually publish it to the web. The layouts of webpages viewed in Internet Explorer always seem to be slightly (and sometimes a lot) different to webpages in Firefox.

    Always attach your CSS sheet to the page you are working on and always define your text fonts in your style sheet. If you need a new font then define it in your CSS sheet first and then use it. Some of my style sheets are monsters.

    One of the frustrating issues with Dreamweaver is that when you change a font by highlighting it and changing it in the properties window, Dreamweaver doesn't always erase the old font. This can cause conflicts that show up as very unpredictable font changes when you publish your webpage.

    What do I do?

    As soon as I notice that my fonts or layouts have gone crazy I position my cursor at the beginning of the inconsistency and search in the code at that point for doubled up font definitions.

    If you have imported the document or copied and pasted it from somewhere else it will bring all of its old baggage with it, including all of the formatting and fonts from the original document or webpage.

    What I do at this point is "cleanse" the document.

    I go into code view, select all of the code, copy it to the clipboard and then paste it into a Notebook page. I then go to "edit" and select "find" from the dropdown menu (I can't seem to make "find" work properly in Dreamweaver).

    I enter the word "style", position my cursor at the top of the document and click "find next". I then systematically erase every existing style definition in the document (hopefully its not too long).

    Your document should now be pure and unsullied, contain no style definitions and be ready for you to attach your CSS Style Sheet.

    You then copy and paste the cleansed text back into your code page, making sure to save the original code first in case there's a snafu in your changes.

    If you find "font" conflicts arising again, you can simply repeat the process if you can't obviously find the villian at the first couple of tries.

    You will know you have problems if you find "non-CSS" styles showing up in your font list in the properties inspector.

    A valid CSS style definition will look like this in your font listings:

    "Para12ptBlack" or something similar,

    while a style that could cause problems looks like this: "style1" and needs to be removed if you want your page to be free of font conflicts.

    So look for a line in your code that looks something like this at the point where the problem is showing up:

    "style1- Sample Text to Demonstrate Font conflicts."

    Dreamweaver defines the "style" in both the "head" and the "body" of your webpage code. Both need to be removed.

    Here's an example:

    NOTE: Due to constraints form Ezine Articles whereby using HTML tags in the body of my article causes publication issues this is not exactly syntactically correct code but gives you the idea.

    ----------------------------------------------------------

    "head"

    style1 (font-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers

    Office Equipment Supplies
    With numerous companies catering to the demand of office equipment supplies, it becomes tough to make a prudent choice. However, it also offers several advantages. With so many companies competing with each other to sell you the office equipment supplies, you can expect competitive prices, excellent service both before and after the purchase and of course, top quality products. There are a number of parameters that may help you decide to opt for one office equipment supplier over another. The time taken for delivery, the delivery locations, the quality of their products, how knowledgeable their staff is, their billing policies and their return policy & warranty agreements are certain important issues that usually help you distinguish between companies and make a choice.Online shopping for office equipment has gained precedence over actual shopping. Not only is it more convenient, but also the range of products
    ly. So if you're a beginner read on.

    So there you are--you're sitting there with the blank Dreamweaver page in front of you.

    What are you going to do first? Getting it to work right is all about doing it right the first time. Begin as you intend to continue.

    Here's what I do ,and don't for a moment think this is gospel (maybe there's an easier way)--its just what I find keeps me out of trouble.

    Where fonts for your text are concerned you are best to start by creating a CSS Style Sheet. CSS stands for Cascading Style Sheet and can help keep you out of trouble with fonts that can suddenly go crazy on you. Now this is not the only use of CSS--in fact its amazingly versatile in regard to graphics etc.-- but lets just stick to fonts.

    Well get to how to set up a CSS sheet in a follow up article, but the main thing is to NEVER, and I mean never, designate a font that is not listed in your CSS sheet unless you know how to get out of the ensuing mixup. This will help keep you out of lots of trouble with fonts.

    There is a great difference between what you see on your HTML editor (which is what Dreamweaver really is--although very sophisticated) and what you see on your web page when you test it as an HTML file on your screen.

    And it can get worse when you actually publish it to the web. The layouts of webpages viewed in Internet Explorer always seem to be slightly (and sometimes a lot) different to webpages in Firefox.

    Always attach your CSS sheet to the page you are working on and always define your text fonts in your style sheet. If you need a new font then define it in your CSS sheet first and then use it. Some of my style sheets are monsters.

    One of the frustrating issues with Dreamweaver is that when you change a font by highlighting it and changing it in the properties window, Dreamweaver doesn't always erase the old font. This can cause conflicts that show up as very unpredictable font changes when you publish your webpage.

    What do I do?

    As soon as I notice that my fonts or layouts have gone crazy I position my cursor at the beginning of the inconsistency and search in the code at that point for doubled up font definitions.

    If you have imported the document or copied and pasted it from somewhere else it will bring all of its old baggage with it, including all of the formatting and fonts from the original document or webpage.

    What I do at this point is "cleanse" the document.

    I go into code view, select all of the code, copy it to the clipboard and then paste it into a Notebook page. I then go to "edit" and select "find" from the dropdown menu (I can't seem to make "find" work properly in Dreamweaver).

    I enter the word "style", position my cursor at the top of the document and click "find next". I then systematically erase every existing style definition in the document (hopefully its not too long).

    Your document should now be pure and unsullied, contain no style definitions and be ready for you to attach your CSS Style Sheet.

    You then copy and paste the cleansed text back into your code page, making sure to save the original code first in case there's a snafu in your changes.

    If you find "font" conflicts arising again, you can simply repeat the process if you can't obviously find the villian at the first couple of tries.

    You will know you have problems if you find "non-CSS" styles showing up in your font list in the properties inspector.

    A valid CSS style definition will look like this in your font listings:

    "Para12ptBlack" or something similar,

    while a style that could cause problems looks like this: "style1" and needs to be removed if you want your page to be free of font conflicts.

    So look for a line in your code that looks something like this at the point where the problem is showing up:

    "style1- Sample Text to Demonstrate Font conflicts."

    Dreamweaver defines the "style" in both the "head" and the "body" of your webpage code. Both need to be removed.

    Here's an example:

    NOTE: Due to constraints form Ezine Articles whereby using HTML tags in the body of my article causes publication issues this is not exactly syntactically correct code but gives you the idea.

    ----------------------------------------------------------

    "head"

    style1 (font-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers

    Accept Credit Cards Online Without a Merchant Account
    There are two major ways to accept credit cards on your website. The first and most expensive is to have your own merchant account. Not only is this option expensive, it also requires extensive credit checks, lots of paperwork, and usually takes days or weeks before you get approved. Fortunately, there is an alternative.Third party payment processors who will accept credit card payments on your behalf exist in growing numbers. These third party processors will take a percentage of your sale for their troubles, then pass on the rest to you. Rates vary greatly from one payment provider to another so doing your homework is important in order to get the right fit for you. Some payment providers will accept all kinds of goods and services while others specialize in only digital products, or hard goods, or services.General Purpose Payment Providers include:Paypal – Owned by Ebay, Paypal offers on
    s in Firefox.

    Always attach your CSS sheet to the page you are working on and always define your text fonts in your style sheet. If you need a new font then define it in your CSS sheet first and then use it. Some of my style sheets are monsters.

    One of the frustrating issues with Dreamweaver is that when you change a font by highlighting it and changing it in the properties window, Dreamweaver doesn't always erase the old font. This can cause conflicts that show up as very unpredictable font changes when you publish your webpage.

    What do I do?

    As soon as I notice that my fonts or layouts have gone crazy I position my cursor at the beginning of the inconsistency and search in the code at that point for doubled up font definitions.

    If you have imported the document or copied and pasted it from somewhere else it will bring all of its old baggage with it, including all of the formatting and fonts from the original document or webpage.

    What I do at this point is "cleanse" the document.

    I go into code view, select all of the code, copy it to the clipboard and then paste it into a Notebook page. I then go to "edit" and select "find" from the dropdown menu (I can't seem to make "find" work properly in Dreamweaver).

    I enter the word "style", position my cursor at the top of the document and click "find next". I then systematically erase every existing style definition in the document (hopefully its not too long).

    Your document should now be pure and unsullied, contain no style definitions and be ready for you to attach your CSS Style Sheet.

    You then copy and paste the cleansed text back into your code page, making sure to save the original code first in case there's a snafu in your changes.

    If you find "font" conflicts arising again, you can simply repeat the process if you can't obviously find the villian at the first couple of tries.

    You will know you have problems if you find "non-CSS" styles showing up in your font list in the properties inspector.

    A valid CSS style definition will look like this in your font listings:

    "Para12ptBlack" or something similar,

    while a style that could cause problems looks like this: "style1" and needs to be removed if you want your page to be free of font conflicts.

    So look for a line in your code that looks something like this at the point where the problem is showing up:

    "style1- Sample Text to Demonstrate Font conflicts."

    Dreamweaver defines the "style" in both the "head" and the "body" of your webpage code. Both need to be removed.

    Here's an example:

    NOTE: Due to constraints form Ezine Articles whereby using HTML tags in the body of my article causes publication issues this is not exactly syntactically correct code but gives you the idea.

    ----------------------------------------------------------

    "head"

    style1 (font-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers

    Helpful Sites to Help Online Business Marketing Owners
    In today's world of online business it seems to be harder to find good sites that are beneficial to online marketing and business development. We will review a few sites with good content for online marketing for small business.The Marketing Man is a good website full of marketing tools for online entrepreneurs, consultants and business owners. It has a wide variety of business forms, programs, software, ebooks, advice and tips that are always current and relevant to today's online marketing needs. Help with designing sales letters, web video presentation tools and tips about ezine and cart services.http://www.marketingman.comSite Pro News provides a good resource for web site owners with tips on SEO and a wide variety of articles to help small business online. They have various advertisements for programs on how to build your traffic base as well. It is also a really good resource for learning t
    too long).

    Your document should now be pure and unsullied, contain no style definitions and be ready for you to attach your CSS Style Sheet.

    You then copy and paste the cleansed text back into your code page, making sure to save the original code first in case there's a snafu in your changes.

    If you find "font" conflicts arising again, you can simply repeat the process if you can't obviously find the villian at the first couple of tries.

    You will know you have problems if you find "non-CSS" styles showing up in your font list in the properties inspector.

    A valid CSS style definition will look like this in your font listings:

    "Para12ptBlack" or something similar,

    while a style that could cause problems looks like this: "style1" and needs to be removed if you want your page to be free of font conflicts.

    So look for a line in your code that looks something like this at the point where the problem is showing up:

    "style1- Sample Text to Demonstrate Font conflicts."

    Dreamweaver defines the "style" in both the "head" and the "body" of your webpage code. Both need to be removed.

    Here's an example:

    NOTE: Due to constraints form Ezine Articles whereby using HTML tags in the body of my article causes publication issues this is not exactly syntactically correct code but gives you the idea.

    ----------------------------------------------------------

    "head"

    style1 (font-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers

    Fourteen Tips on Conquering the Presentation
    When presenting, you need to hold your audience's attention, convey information, and persuade people to act, while all the time guarding against anything that could derail your performance. To help you master this balancing act, here are a few pointers:* Know your subject inside out. This is the single most important thing you can do to ensure a high-impact presentation. Be the absolute expert on whatever it is that you'll be talking about. Nobody in the room should know as much about the topic as you do.* Understand your audience. Speak at their level of knowledge. Know their needs. What do they want from you, and what do you want from them?* Rehearse. Run through the presentation in front of a mirror, in front of a spouse or friend, or in front of your team. Use a cassette recorder or camcorder. Time yourself and add on a few minutes for Q&A.* Anticipate questions. As you rehearse, stay
    nt-family: Verdana, Arial, Helvetica, sans-serif;

    font-size: 14px;

    font-weight: bold; )

    "/head"

    "body"

    style1 class - Para12ptblueBOLD - Sample Text to Demonstrate Font conflicts.

    "/body"

    -----------------------------------------------------------

    When you changed your font to "12 pt Blue Bold" using an attached "CSS Style sheet" you will notice there are now two styles defined for the same text.

    When you re-defined your style from the CSS Style sheet Dreamweaver didn't delete the "style1" from the class definition. This is how the conflict happens - your computer gets confused.

    It is these instances of "style 1" and similar, in both the "body" and the "head" that you will need to delete to keep your webpage clear of font conflicts --as long as this is the only issue..

    Remember to leave your CSS font definitions intact. You don't want to remove these. These are the good guys.

    The line should now look something like this:

    class "Para12ptblueBOLD" Sample Text to Demonstrate Font conflicts.

    This is a nice clean definition that won't cause problems.

    Since you have attached a CSS Style Sheet there will be no Style definition in the "head".

    If you've been house cleaning as you go along this will usually fix the issue.

    I hope this has been helpful.

    Keep a lookout for followup articles on "Setting up simple CSS style sheets" and "Using "Layers to format your page layout".

    HTTP = HTML link (for blogs, profiles,phorums):
    <a href="http://www.casualarticles.com/article/83951/casualarticles-Webpage-Creation-in-Dreamweaver--How-I-Deal-With-Font-Conflicts.html">Webpage Creation in Dreamweaver - How I Deal With Font Conflicts</a>

    BB link (for phorums):
    [url=http://www.casualarticles.com/article/83951/casualarticles-Webpage-Creation-in-Dreamweaver--How-I-Deal-With-Font-Conflicts.html]Webpage Creation in Dreamweaver - How I Deal With Font Conflicts[/url]

    Related Articles:

    Beehives: How to Attract these New Market Segments

    Using a Sales Process - The Gatekeepers

    Are You a Jumper or a Planner?

    Bookmark it: del.icio.us digg.com reddit.com netvouz.com google.com yahoo.com technorati.com furl.net bloglines.com socialdust.com ma.gnolia.com newsvine.com slashdot.org simpy.com shadows.com blinklist.com