Books for you

For more information about time zones, please refer to http://www.timeanddate.com.
We often use parsers before we display data to make the data safe or
to apply formatting to the data. We need to be careful how we store
data that is going to be parsed. If the data is ever going to be edited,
we must store the data in its RAW state. If the data is going to be
edited extremely rarely and if the parsing is reversible, we may want to
consider building a 'reverse-parser'. This way we can store the data in
its parsed format, eradicating the need for parsing when we view the
data and reducing the load on the server. Another option available to
us is to store the data in both formats. This way we only have to parse
data when we save it.
Dealing with Multilingual Requirements
In the previous chapter we discussed Joomla!s use of the Unicode character set using
UTF-8 encoding. Unlike ASCII and ANSII, Unicode is a multi-byte character set; it
uses more than eight bits (one byte) per character. When we use UTF-8 encoding,
character byte lengths vary.


Pages:
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74