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 Incorporate third-party software, such as Ikivo Animator or Beatware Mobile Designer, into this solution to animate your SVG Tiny content before you publish it.Adobe GoLive 5, GoLive 6 GoLive CS & GoLive CS2 - Tips & Tutorials For example, you can design mobile SVG graphics and interfaces in Illustrator, add interactivity and client or server-side scripts in GoLive, and then publish the content to mobile devices. A flexible solution through Adobe integration: GoLive CS2 integrates tightly with Adobe Illustrator CS2 to provide a versatile solution for producing SVG Tiny content, which you can distribute directly or incorporate into MMS slideshows.Built-in Small Screen Rendering and device emulation help you preview and refine your mobile content before you take it live. Now you can develop mobile content with the same flexibility, moving easily from making visual design choices to verifying and adjusting your code. A visual development environment for mobile content: GoLive CS2 has long been known for combining a visual layout environment with extensive coding and site management controls. ![]() That’s why GoLive CS2 offers extensive support for such mobile standards as CSS, XHTML, SMIL, SVG Tiny, MPEG-4, and 3GPP, all of which have been endorsed by global standards committees as well as leading companies, including Sony Ericsson, Nokia, Opera, Access, Openwave, Ikivo, and others. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |