Conformance Statement

Product Standard: Internationalized Terminal Interfaces V2

This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

Organization
Author

1. Internationalized Terminal Interfaces V2

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product Identification	Version/Release Number	Product Supplier

Environment Specification

Product registration applies to software products operating in a specific hardware or hardware/software environment.
A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

	Waiver Number	Expiry Date

1.1 Product Scope

1.1.1 Type of Conformance

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

Response

Options in this area are "Soft Conformance" or "Hard Conformance". If you select Soft conformance, then you must declare any differences between the branded product and functionality defined for the Terminal Interfaces Product Standard.

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 7 Specification, including the Enhanced Curses Extension.
Hard Conformance
This involves strict conformance to the X/Open Curses, Issue 7 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

Internationalized Terminal Interfaces V2 Product Standard Definition.

1.1.2 Coded Character Sets

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

Response

List the names of coded character sets supported for the data type chtype and specify which of these is octet-based.

Rationale

An implementation that claims Internationalized Terminal Interfaces V2 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

Technical Standard, X/Open Curses, Issue 7, Section 1.2, Conformance.

1.2 Supported Terminals

Question 3: 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 Base Definitions, Issue 7, and the Curses interfaces defined in X/Open Curses, Issue 7, 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

Technical Standard, Base Definitions, Issue 7, Chapter 11, General Terminal Interface.

Technical Standard, X/Open Curses, Issue 7, Section 3.9, Synchronous and Networked Asynchronous Terminals.

1.3 Terminfo Source File Limits

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

Response

Description	Minimum Maximum	Implementation Maximum
Length of a line	1023
Length of a terminal alias	14
Length of a terminal model name	128
Length of a single field	128
Length of a string value	1000
Length of a string representing a numeric value	99
Magnitude of a numeric value	32767

Rationale

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

Technical Standard, X/Open Curses, Issue 7, Section 7.1.1, Minimum Guaranteed Limits.

1.4 Specific Interfaces

1.4.1 tparm()

Question 5: How does the tparm() function handle parameters in string context?

Response

Describe how the corresponding long int argument is handled by tparm() when a parameter is used in a string context.

Rationale

If any of the parameters %p1 through %p9 in a parameterized cap string passed to tparm() is used in a string context (for example, if it is popped using %l or %s), the behavior is implementation-defined. Traditionally the long int argument was converted to a pointer which was dereferenced to obtain the string to be used. However, this behavior is not appropriate on implementations where converting char * pointers to long int and back does not preserve their values.

Reference

Technical Standard, X/Open Curses, Issue 7, Chapter 4, tigetflag(), DESCRIPTION.

2. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.

3. Change History

Date	Name	Comment
New

The Open Group, UNIX and The Open Brand ("X Device") are registered trademarks of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.