View Issue Details

IDProjectCategoryView StatusLast Update
00002161003.1(2008)/Issue 7Base Definitions and Headerspublic2013-04-16 13:06
Reportergeoffclare Assigned Toajosey  
PrioritynormalSeverityObjectionTypeOmission
Status ClosedResolutionAccepted 
NameGeoff Clare
OrganizationThe Open Group
User Reference
Section6.4
Page Number129
Line Number3661
Interp StatusApproved
Final Accepted Text0000216:0000402
Summary0000216: Control characters must have single-byte encodings
DescriptionThe design of the general terminal interface is such that the
characters which perform the terminal functions ERASE, KILL,
INTR, etc. have to be single-byte characters, since they are
assigned/obtained using a single numeric value in the
termios.c_cc[] array.

Currently only those control characters that are in the portable
character set (alert, backspace, tab, carriage-return, newline,
vertical-tab, form-feed) have an explicit requirement that they
are represented in a single byte (P128 L3590). However, the
absence of any mention of a way of encoding multiple bytes into
termios.c_cc[] entries means that there is an implicit requirement
for the other control characters as well. The requirement should
be stated explicitly.

In addition, there is a minor editorial problem in the beginning
of section 6.2 where it says "The POSIX locale contains the
characters in Table 6-1 (on page 125), which have the properties
listed in Section 7.3.1 (on page 139)." Since 7.3.1 specifies
properties for both the portable character set (Table 6-1) and the
control character set (Table 6-2) in the POSIX locale, both tables
should be mentioned in section 6.2.
Desired ActionAfter

    "the symbolic names and their corresponding encoding values shall
    be included in the file."

add

    "The encoding values shall each be represented in a single byte."

At page 128 line 3596 change

    "contains the characters in Table 6-1 (on page 125)"

to

    "contains the characters in Table 6-1 (on page 125) and Table 6-2
    (on page 130)"
Tagstc1-2008

Activities

msbrown

2010-03-25 15:21

manager   bugnote:0000402

Interpretation response
------------------------

The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale:
-------------
Existing practice, as described by the Submitter.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Make the changes suggested by the Submitter.

Issue History

Date Modified Username Field Change
2010-01-29 10:36 geoffclare New Issue
2010-01-29 10:36 geoffclare Status New => Under Review
2010-01-29 10:36 geoffclare Assigned To => ajosey
2010-01-29 10:36 geoffclare Name => Geoff Clare
2010-01-29 10:36 geoffclare Organization => The Open Group
2010-01-29 10:36 geoffclare Section => 6.4
2010-01-29 10:36 geoffclare Page Number => 129
2010-01-29 10:36 geoffclare Line Number => 3661
2010-01-29 10:36 geoffclare Interp Status => ---
2010-03-25 15:21 msbrown Interp Status --- => Proposed
2010-03-25 15:21 msbrown Note Added: 0000402
2010-03-25 15:21 msbrown Status Under Review => Interpretation Required
2010-03-25 15:21 msbrown Resolution Open => Accepted
2010-03-25 15:22 msbrown Final Accepted Text => 0000216:0000402
2010-05-28 14:03 ajosey Interp Status Proposed => Approved
2010-09-24 17:00 Don Cragun Tag Attached: tc1-2008
2013-04-16 13:06 ajosey Status Interpretation Required => Closed