Through HTML 3.2, the eight bit standard was ISO 8859-1. As of HTML 4.0, the default document character set is Unicode. For XML, the absolute default...

For non-default encoding, the XML text declaration should contain an encoding declaration as in the following examples: <?xml encoding='UTF-8'?&...

The default encoding is selected by the JRE based on the host operating system and its locale. For example, in the US locale on Windows, windows-1252 is used. In the Simplified Chinese locale on Solaris, GB2312, GBK, GB18030, or UTF-8 can be the default encoding, depending on the selection made when logging into Solaris. The default encoding is significant because the JRE commonly exchanges text with the host operating system in the default encoding.

URL Encoding is a process of transforming user input to a CGI form so it is fit for travel across the network -- basically, stripping spaces and punctuation and replacing with escape characters. URL Decoding is the reverse process. To perform these operations, call java.net.URLEncoder.encode() and java.net.URLDecoder.decode() (the latter was (finally!) added to JDK 1.2, aka Java 2). URL Rewriting is a technique for saving state information on the user's browser between page hits.

Most modern e-mail programs for the Windows environment allow you to send messages in HTML format. Some of these programs even have this option automatically enabled. When the majordomo system processes the mails for distribution it doesn't notice HTML code and reads this as "normal" text. In order to prevent these cryptic messages from being distributed, the HTML-filter on the majordomo system was enabled.

AmphetaDesk 0.93.2 and above ship with a number of default encodings, which you can see by browsing the lib/XML/Parser/Encodings/ directory. As the name suggests, these all come from the XML::Parser::Encodings Perl module, which also contains some scripts to make your own from encoding maps freely available online. Once you've got the encoding.enc file, drop it into lib/XML/Parser/Encodings/ and test it out on a feed that requires it.

This option determines the value that TOYS uses to set the NLS_LANG environment variable. This variable is used by the Oracle drivers and works as follows. If the character set specified by this variable is the same as the database character set then no character set conversion is performed. This is the most efficient means of operation.

In simple terms, HTML (Hypertext Markup Language) is a system of marking up a document so it can be published on the World Wide Web. Documents prepared in HTML contain reference graphics and formatting tags. Put another way, HTML is a series of predefined tags that primarily focus on describing how content appears on the Web. For example, HTML describes the font, font size, and color of the text in this paragraph should be when viewed by a Web browser.

I have started work on an XML version of HTML Pro, but it’s not easy, and I need convincing it’s worth doing. The Extensible HyperText Markup Language (XHTML) is a W3C project: ‘This specification defines XHTML 1.0, a reformulation of HTML 4.0 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4.0. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4.0.

The apache web server looks in the directory you specify in your web browser for a file to display. If you do not specify a file name apache will look for the following names, in order: In other words, if you browse to http://yourdomain.com, apache will first try to open http://yourdomain.com/index.html, then http://yourdomain.com/index.htm, etc.

XML is a meta-language optimized for use on the Internet. A meta-language provides a way to create other languages or vocabularies. Many applications use XML as a way of sharing data between otherwise incompatible systems.

To "undeclare" the default XML namespace, you declare a default XML namespace with an empty (zero-length) URI reference. Within the scope of this declaration, unprefixed element type names do not belong to any XML namespace. For example, in the following, the default XML namespace is the http://www.foo.org/ for the A and B elements and there is no default XML namespace for the C and D elements. That is, the names A and B are in the http://www.foo.

XStream architecture is based on IO Readers and Writers, while the XML declaration is the responsibility of XML parsers. XStream all HierarchicalStreamDriver implementation respect the encoding since version 1.3, but only if you provide an InputStream.

The .NET Compact Framework implements decoders for UTF8, ASCII and UTF16 (big- and little- endian) encodings in managed code. All other encodings, such as all ANSI codepage encodings involve a PInvoke down to the operating system. So using UTF8, ACII and UTF16 is usually faster. If you don???t use international characters (outside of the ASCII character set) use UTF8 or ASCII (these have approximately equal performance). Try to avoid using Windows codepage encodings.

The best portability. These encodings are more widely supported by XML processors than any others, meaning that your documents will have the best possible chance of being read correctly, no matter where they end up. Full international character support. Both utf-8 and utf-16 cover the full Unicode character set, which includes all of the characters from all major national, international and industry character sets. Efficient.

If you are running Java on English Windows platforms, it is probably Cp1252. If you are running Java on English Solaris platforms, it is most likely 8859_1..

Authors and providers can design their own document types using XML, instead of being stuck with HTML. Document types can be explicitly tailored to an audience, so the cumbersome fudging that has to take place with HTML to achieve special effects should become a thing of the past: authors and designers will be free to invent their own markup elements; Information content can be richer and easier to use, because the hypertext linking abilities of XML are much greater than those of HTML.

No, existing SGML and HTML applications software will continue to work with existing files. But as with any enhanced facility, if you want to view or download and use XML files, you will need to add XML-aware software as it becomes available. Authors should also read the Developers' Section, which contains further information about the internals of XML files. No, XML itself does not replace HTML: instead, it provides an alternative which allows you to define your own set of markup elements.

To import any sort of characters that XML might use itself, such as <, >, &, ', and so forth, you need to use what is called CDATA. It is particularly useful when you want to bring in HTML data, as it allows you to bring in CDATA content as is, without worrying about HTML tags affecting your XML structure.

Use the XMLHTTPRequest object. See here for the documentation. Also look at this thread for some examples. Mayhem notes that this only works for XHTML compliant HTML, but he also offers a neat workaround for non-compliant pages.

Wiping the HPA would surprise and strand people that expect the HPA to have rescue materials. The HPA is a low risk because it is not accessible during normal operations.