The widths of the glyphs for corresponding character points are the same in both fonts (where the character point is defined in both fonts). The kerning tables contain the same values for both fonts where both of the character points in the pair are present in both fonts. Either the appearance of the glyphs is visually similar or they are valid glyph variants as defined by unicode. 10.2.2 User input Implementations shall provide a mechanism for the end user to generate key events as defined in table 12. Table 12: Key events and their status Button (for conventional Key event Status remote controls) 4 colour buttons (red, green, Mandatory VK_RED, VK_GREEN, yellow, blue) VK_YELLOW, VK_BLUE 4 arrow buttons (up, down, Mandatory VK_UP, VK_DOWN, VK_LEFT, left, right) VK_RIGHT ENTER or OK button Mandatory VK_ENTER BACK button Mandatory VK_BACK Number keys VK_0 to VK_9 inclusive Mandatory Play, stop, pause VK_STOP and either Mandatory VK_PLAY and VK_PAUSE or VK_PLAY_PAUSE Fast forward and fast rewind Mandatory VK_FAST_FWD VK_REWIND Record Mandatory if the PVR VK_RECORD feature is supported, otherwise optional. TEXT or TXT or comparable Not available to applications mandatory button 2 program selection buttons Not available to applications Optional (e.g. P+ and P-) WEBTV or comparable button Not available to applications Optional EXIT or TV or comparable Not available to applications Optional button Key events which have a key code listed in the preceding table shall be available to all applications when requested through the KeySet object. Key events which do not have a key code listed in the preceding table shall be handled by the implementation and not delivered to applications. Support for direct keycodes (i.e. the charCode property of the DOM 2 KeyEvent class) is not required.
The widths of the glyphs for corresponding character points are the same in both fonts (where the character point is defined in both fonts). The kerning tables contain the same values for both fonts where both of the character points in the pair are present in both fonts. Either the appearance of the glyphs is visually similar or they are valid glyph variants as defined by unicode. 10.2.2 User input Implementations shall provide a mechanism for the end user to generate key events as defined in table 12. Table 12: Key events and their status Button (for conventional remote controls) Key event Status 4 colour buttons (red, green, yellow, blue) VK_RED, VK_GREEN, VK_YELLOW, VK_BLUE Mandatory 4 arrow buttons (up, down, left, right) VK_UP, VK_DOWN, VK_LEFT, VK_RIGHT Mandatory ENTER or OK button VK_ENTER Mandatory BACK button VK_BACK Mandatory Number keys VK_0 to VK_9 inclusive Mandatory Play, stop, pause VK_STOP and either VK_PLAY and VK_PAUSE or VK_PLAY_PAUSE Mandatory Fast forward and fast rewind VK_FAST_FWD VK_REWIND Mandatory Record VK_RECORD Mandatory if the PVR feature is supported, otherwise optional. TEXT or TXT or comparable button Not available to applications mandatory 2 program selection buttons (e.g. P+ and P-) Not available to applications Optional WEBTV or comparable button Not available to applications Optional EXIT or TV or comparable button Not available to applications Optional Key events which have a key code listed in the preceding table shall be available to all applications when requested through the KeySet object. Key events which do not have a key code listed in the preceding table shall be handled by the implementation and not delivered to applications. Support for direct keycodes (i.e. the charCode property of the DOM 2 KeyEvent class) is not required.
HbbTV-SPEC15-00001-003-specification_with_errata-integrated.docx