Ericsson R320s White Paper page 9

Feature
Tables
WAP/WML
WAP proÞles
*) When creating WML applications, it is recommended to always save the page contents as
UTF8, and that this is clearly indicated 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. Please refer to the R320 Design Guidelines for WAP Services, how to create the applica-
tion correctly.
**) All characters are not supported in all phones. The software version depends on which mar-
ket the phone is associated to. Also, please note that the phone may not support input on a WAP
Service which use certain characters (languages), even if those characters are supported for
browsing in the phone.
Screen characteristics
Rows of text
Height of one row (pixels)
Columns (characters)***
Pixels (Height x Width)
Pixel stretch
Image size
***) Approximate. The screen font is proportional, and ÓWÓ is a wide character, ÓIÓ is narrow.
Support in Ericsson R320s WAP browser
KRC 114 1230, English(EN), Arabic(AR), Czech(CS),
KRC 114 1231, Danish(DA), Finnish(FI), French(FR),
KRC 114 1232, Hungarian(HU), Norwegian(NO),
KRC 114 1186, Polish(PL), Portuguese(PT), Russian,
KRC 114 1187, Slovakian(SK),Swedish(SV)
KRC 114 1188
KRC 114 1161, English(EN), Indonesian(IN),
KRC 114 1162, Thai(TH), Vietnamese(VI), Philippine-
KRC 114 1163 Tagalog(TL), Malay(MS)
Yes
WAP 1.1 compliant, WMLScript
Layers implemented: WAE, WSP (connectionless), WDP
5 WAP proÞles, each with its own settings
Full Input
5 (4+header) 4 (3+header)
13 13
32 I or 7 W 26 I or 6 W
101 x 65
1,24. This means a pixel is 24% higher than it is wide.
Unlimited height, but scrolling required if higher than 4 rows
(4*13 pixels). Truncated at both sides if wider than display.
Selection
4 (3+header)
13
9 normal
9