PHP Tutorials: Unicode signature (BOM) issues

WordPress template by the weird code empty line toss half a day.

Because dansion brother's drive, began to Dreamweaver journey. However, there is little concern that when you save using UTF-8 encoding in Dreamweaver, there are two options for Unicode standardized forms and include Unicode signatures (BOM), which are also visible in page properties:

If the "Include Unicode signature" option is checked, a bizarre page rendering problem can occur.

What is a Unicode signature (BOM)?

The BOM (Byte order mark) is the standard tag used to identify the encoding in the UTF encoding scheme. 2 to 4 bytes at the beginning of the text file, which identifies the file as Unicode, and also identifies the byte order of the following bytes. Because UTF-8 does not have byte order, you can choose to add UTF-8 BOM. This is required for UTF-16 and UTF-32.

Because of the existence of this BOM, PHP mistakenly believes that the text content has been exported, so it will affect the page rendering. It is said that the problem has been repaired in PHP6.

How do I prevent the effect of a Unicode signature (BOM) on page rendering?

Take Dreamweaver For example, when you save a UTF-8-encoded document, you do not check the include Unicode signature (BOM) option.