IEEE Standards Interpretations for IEEE Std 1003.2™-1992 IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX®)--Part 2: Shell and Utilities
Copyright © 1996 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.
Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.
IEEE Standards Department, Copyrights and Permissions, 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA
Interpretation Request #146
Topic: locale -k Relevant Sections: 4.34.3, 188.8.131.52
The specification of locale -k seems unclear. Running locale -k abday day on our implementation outputs: abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday" Whereas other implementations of locale -k abday day output abday="Sun";"Mon";"Tue";"Wed";"Thu";"Fri";"Sat" day="Sunday";"Monday";"Tuesday";"Wednesday";"Thursday";"Friday"; "Saturday" According to our reading of POSIX.2 lines 5525-5554 the former is a possible interpretation of the spec , since the required format is "%s=\"%s\"\n" <keyword name, <keyword value and that we output the keyword values separated in the output by semicolons (as per ll 5540-5541). We cannot see the requirement for additional quoting. The specification would seem to be ambiguous. Please could the committee please consider this matter as to what the correct interpretation is?
The wording surrounding the format for the output of the -k option is clear for single value keywords. The wording describing the output of compound keyword values is ambiguous as to whether quoted strings are to be seperated by semi-colons or semi-colons seperated values within a single quoted string. The standard is unclear on 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 for Interpretation