Page MenuHomeFreeBSD

PR225692: localedef: mark "space" also as "print" excluding known conflicts
ClosedPublic

Authored by yuripv on Oct 8 2018, 11:04 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 18, 7:49 PM
Unknown Object (File)
Oct 10 2024, 1:48 AM
Unknown Object (File)
Oct 2 2024, 11:10 PM
Unknown Object (File)
Sep 11 2024, 5:15 AM
Unknown Object (File)
Aug 19 2024, 8:23 AM
Unknown Object (File)
Aug 18 2024, 4:59 PM
Unknown Object (File)
Aug 18 2024, 11:02 AM
Unknown Object (File)
Aug 15 2024, 6:08 AM
Subscribers

Details

Summary

PR: 225692

The POSIX locale definition says the following:

print

Define characters to be classified as printable characters, including the <space>.

In the POSIX locale, all characters in class graph shall be included; no characters in class cntrl shall be included.

In a locale definition file, characters specified for the keywords upper, lower, alpha, digit, xdigit, punct, graph, and the <space> are automatically included in this class. No character specified for the keyword cntrl shall be specified.

So it doesn't explicitly say anything about "space" here, though it doesn't NOT explicitly forbid including "space" in the "print" class, and I *think* we can extend the <space> character being included to the entire "space" character class.

Test Plan

Build/install in share/ctypedefs, run the test case attached to PR225692.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

LGTM.
(I currently don't have the time to go over to Release Engineering for this though ::-/ )

This revision is now accepted and ready to land.Oct 8 2018, 3:00 PM

No objection from me, although I am not very familiar with this particular code or POSIX in this area.

Ditto pfg—I don't have time to do re's process to commit this to head while it is frozen.

rebase on top of recent localedef changes; make the change less intrusive keeping the warning and only stripping "print" from "space|control" combination.

This revision now requires review to proceed.Oct 21 2018, 1:00 PM
This revision is now accepted and ready to land.Oct 23 2018, 2:45 PM
This revision was automatically updated to reflect the committed changes.