Home  About Us A-Z Index Search  Inquiries  Register Login Press  Shop

1. Internationalised Terminal Interfaces

Product Information

Environment Specification

Temporary Waivers

None

1.1 Product Scope

1.1.1 Type of Conformance

Question 1: What is the state of conformance of this product?

Response

Soft Conformance

Rationale

Two sets of conformance rules are defined within this Product Standard:

• Soft Conformance

  This comprises a vendor declaration in the Conformance Statement of the differences in behavior of the conformant product and the X/Open Curses, Issue 4, Version 2 Specification, including the Enhanced Curses Extension.

• Hard Conformance

  This involves strict conformance to the X/Open Curses, Issue 4, Version 2 Specification, including the Enhanced Curses Extension, and use of the test suite as the Indicator of Compliance. The running of the relevant test cases is determined by a parameter of the VSU5 Test Suite.

Reference

Internationalised Terminal Interfaces Product Standard Definition.

1.1.2 Coded Character Sets

Question 2: Which coded character sets are supported by the chtype data type?

Response

ISO_646.irv:1991

Rationale

An implementation that claims BASE, BASE 95 or UNIX conformance and Internationalised Terminal Interfaces conformance must support at least octet-based code sets (such as ISO 8859-1), within the chtype data type. Support for other coded character sets is implementation-defined.

Reference

CAE Specification, X/Open Curses, Issue 4, Section 1.2, Conformance.

1.1.3 Character Attributes

Question 3: Which character attributes are supported by the implementation?

Response

A_ALTCHARSET
A_HORIZONTAL
A_LEFT
A_LOW
A_RIGHT
A_TOP
A_VERTICAL

Rationale

An implementation that claims BASE or BASE 95 conformance and Internationalised Terminal Interfaces conformance must support at least the character attributes: A_BLINK, A_BOLD, A_DIM, A_REVERSE, A_STANDOUT and A_UNDERLINE. Support for other character attributes, listed above, is implementation-defined.

Reference

CAE Specification, X/Open Curses, Issue 4, Chapter 5, Headers.

1.2 Supported Terminals

Question 4: Which of the following terminal types are supported by the implementation (if any)?

Response

Synchronous	Yes   No
A character cannot be transmitted by a single key stroke only in blocks	Yes   No
The refresh() routine must redraw the entire screen contents in order to perform any update	Yes   No
It is not possible to disable echo	Yes   No
There are additional limitations defined below	Yes   No




Networked Asynchronous	Yes   No
A character cannot be transmitted by a single key stroke only in blocks	Yes   No
The refresh() routine must redraw the entire screen contents in order to perform any update	Yes   No
It is not possible to disable echo	Yes   No
There are additional limitations defined below	Yes   No




Non-standard Asynchronous	Yes   No
A character cannot be transmitted by a single key stroke only in blocks	Yes   No
The refresh() routine must redraw the entire screen contents in order to perform any update	Yes   No
It is not possible to disable echo	Yes   No
There are additional limitations defined below	Yes   No

Rationale

The General Terminal Interface described in System Interface Definitions, Issue 4, Version 2, and the Curses interfaces defined in X/Open Curses, Issue 4, are provided to control terminals connected to asynchronous communication ports. They may also be used to control synchronous, networked asynchronous or non-standard directly-connected asynchronous terminals, subject to possible implementation-defined limitations.

Reference

CAE Specification, System Interface Definitions, Issue 4, Version 2, Chapter 9, General Terminal Interface.

CAE Specification, X/Open Curses, Issue 4, Section 3.9, Synchronous and Networked Asynchronous Terminals.

1.3 Terminfo Source File Limits

Question 5: What limits does the implementation support for a terminfo source file?

Response

Length of a line
Length of a terminal alias
Length of a terminal model name
Length of a single field
Length of a string value
Length of a string representing a numeric value
Magnitude of a numeric value

Rationale

X/Open Curses, Issue 4, specifies that a conformant implementation must declare its actual limits for the above items and defines minimum values that the implementation must support.

2. Appendix

Copyright©
All rights reserved.

3. Change History

 Copyright © 1998-2020 The Open Group. All Rights Reserved.

 The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.