White Paper T630/T628
Feature | Support in the T630/T628 WAP browser |
|
|
| *) When creating WML applications, it is recommended that you |
| always save the page contents as UTF8, and that this is clearly indi- |
| cated in the pages before publishing. This ensures that the contents |
| of the application can be viewed, regardless of character sets used in |
| gateways and the phone. All characters are not supported in all |
| phones. The software version depends on which market the phone is |
| associated to. Also, please note that the phone may not support input |
| on a WAP Service which uses certain characters (languages), even if |
| those characters are supported for browsing in the phone. |
|
|
WAP browser | WAP 2.0 baseline |
|
|
WAP profiles | Dynamic - up to 5 WAP profiles, each with its own settings |
|
|
WTLS (security) | Yes, |
| WTLS Class 1 - Encoding |
| WTLS Class 2 - Encoding + Server Authentication. Root Certificates |
| needed in phone |
| WTLS Class 3 - Encoding + Server Authentication + Client |
| Certification. Root Certificates needed in phone + special SIM cards |
| Sign text |
|
|
71 | October 2003 |
