| |
Home • About Us •A-Z Index• Search |
Organization | Huawei |
---|---|
Author | Peng Shen |
Product Identification | Version/Release Number | Product Supplier |
---|---|---|
EulerOS | 2.0 | Huawei Technologies Co., Ltd. |
Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details |
---|---|---|---|---|
Huawei Kunlun Mission Critical Server |
Huawei Kunlun Mission Critical Server |
Internationalised System Calls and Libraries Extended V2 |
None |
Test Suite: N/A
Test Report: N/A |
None
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:
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.
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.
Question 2: Which coded character sets are supported by the chtype data type?
Response
ISO 8859-1 ISO 8859-6 ISO 8859-15 ISO 8859-2 ISO 8859-14 ISO 8859-7 ISO 8859-8 ISO 8859-3
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.
Question 3: Which character attributes are supported by the implementation?
Response
A_ALTCHARSET | Supported |
A_HORIZONTAL | Supported |
A_LEFT | Supported |
A_LOW | Supported |
A_RIGHT | Supported |
A_TOP | Supported |
A_VERTICAL | Supported |
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.
Question 4: Which of the following terminal types are supported by the implementation (if any)?
Response
Synchronous | Yes |
---|---|
A character cannot be transmitted by a single key stroke only in blocks | No |
The refresh() routine must redraw the entire screen contents in order to perform any update | No |
It is not possible to disable echo | No |
There are additional limitations defined below | No |
Networked Asynchronous | Yes |
---|---|
A character cannot be transmitted by a single key stroke only in blocks | No |
The refresh() routine must redraw the entire screen contents in order to perform any update | No |
It is not possible to disable echo | No |
There are additional limitations defined below | No |
Non-standard Asynchronous | Yes |
---|---|
A character cannot be transmitted by a single key stroke only in blocks | No |
The refresh() routine must redraw the entire screen contents in order to perform any update | No |
It is not possible to disable echo | No |
There are additional limitations defined below | 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.
Question 5: What limits does the implementation support for a terminfo source file?
Response
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 4, specifies that a conformant implementation must declare its actual limits for the above items and defines minimum values that the implementation must support.
Copyright © 2016
All rights reserved.
Date | Name | Comment |
---|---|---|
11-Aug-2016 | Peng Shen | EulerOS 2.0 |
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.