You'll find some free Dreamweaver video clips from Total Training that will help you decide whether this is the right program for you. Worried about the future of GoLive? Wondering if you need to learn Dreamweaver? Have a look at our free Dreamweaver tutorials. ![]() If your page already has an encoding type set but GoLive is not recognizing it because it's too far down in the page code (for instance, if there's a lot of server-side code at the top of the document), you can increase the scan limit near the bottom of the encoding preferences. Expand the "Roman" set and enable the Default radio button to the right of iso-8859-1. If you aren't using XHTML and would like to change the default encoding back to iso-8859 like previous versions, go to Preferences > Encodings. As with any major change, be sure to make a back-up of your entire site before running the command. After running that command on your site, you shouldn't have to worry about assigning the encoding when opening your old pages anymore. This command will write the encoding META tag into each page and re-encode all text to match. You can easily encode (or re-encode) all the pages in your site at once (or a group of pages) by using the new Special > Convert > Encoding. GoLive will automatically assign the encoding used to open the file. You can also assign the encoding type after the page has been opened by dragging an Encode object from the Head tab of the Objects Palette into your document head section. NOTE: Do NOT use this feature to change to a different encoding since the page text will not be re-encoded to match your selection. Be sure to choose the encoding type used to create the document (probably iso-8859-1) and you can choose the second option to "set the page to the selected encoding" and let GoLive write the encoding META tag into the head section of your page. When opening a file with no encoding, GoLive should prompt you to specify which encoding to open the file in. If your special characters in documents made in earlier versions of GoLive appear corrupted when opening into GoLive CS2, it may be because there is no encoding type set in your document, and CS2 is opening it with the new default producing unexpected results. Using any other encoding with an XML document requires an XML prolog, which drops IE Win into quirks mode, so UTF-8 encoding is best for producing valid XHTML pages. Also, UTF-8 is the default encoding for XML. Why the change? Aside from just not having to use the HTML character entities, UTF-8 works well for many languages that use characters outside the standard English character set. Entering, for instance, a non-breaking space character in layout view will result in a non- breaking space character in source view instead of the HTML entity. UTF-8 does not require HTML entities to display many special characters. The default text encoding has changed from iso-8859-1 (GoLive CS and under) to UTF-8 (GoLive CS2). The following is from Nate Baldwin of Why Is GoLive CS2 Not Converting Special Characters Entered In Layout View To HTML Entities? NEW - EXCLUSIVE - Adobe GoLive CS2 Video Tutorial Clips Page last updated 20 14-01-01 at 15.11.Adobe GoLive 5, GoLive 6 GoLive CS & GoLive CS2 - Tips & Tutorials
0 Comments
Leave a Reply. |