[1003.1(2016/18)/Issue7+TC2 0001548]: Addition of a POSIX.utf-8 locale (likely as 7.3 "POSIX.utf-8 locale")
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1548 == Reported By:steffen Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1548 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: steffen Organization: User Reference: Section:chapter 7 Page Number:135 ff. Line Number:3933 ff. Interp Status: --- Final Accepted Text: == Date Submitted: 2022-01-11 16:04 UTC Last Modified: 2022-06-23 16:24 UTC == Summary:Addition of a POSIX.utf-8 locale (likely as 7.3 "POSIX.utf-8 locale") == -- (0005868) Don Cragun (manager) - 2022-06-23 16:24 https://austingroupbugs.net/view.php?id=1548#c5868 -- This was discussed during the 2022-06-23 conference call. We would welcome an addition to the standard that provides a standard UTF-8 locale. Please provide a fully fleshed out proposal. Issue History Date ModifiedUsername FieldChange == 2022-01-11 16:04 steffenNew Issue 2022-01-11 16:04 steffenName => steffen 2022-01-11 16:04 steffenSection => chapter 7 2022-01-11 16:04 steffenPage Number => 135 ff. 2022-01-11 16:04 steffenLine Number => 3933 ff. 2022-06-23 16:24 nick Note Added: 0005867 2022-06-23 16:24 Don Cragun Note Added: 0005868 ==
[1003.1(2016/18)/Issue7+TC2 0001548]: Addition of a POSIX.utf-8 locale (likely as 7.3 "POSIX.utf-8 locale")
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1548 == Reported By:steffen Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1548 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: steffen Organization: User Reference: Section:chapter 7 Page Number:135 ff. Line Number:3933 ff. Interp Status: --- Final Accepted Text: == Date Submitted: 2022-01-11 16:04 UTC Last Modified: 2022-06-23 16:24 UTC == Summary:Addition of a POSIX.utf-8 locale (likely as 7.3 "POSIX.utf-8 locale") == -- (0005867) nick (manager) - 2022-06-23 16:24 https://austingroupbugs.net/view.php?id=1548#c5867 -- This was discussed during the 2022-06-23 conference call. We would welcome an addition to the standard that provides a standard UTF-8 locale. Please provide a fully fleshed out proposal. Issue History Date ModifiedUsername FieldChange == 2022-01-11 16:04 steffenNew Issue 2022-01-11 16:04 steffenName => steffen 2022-01-11 16:04 steffenSection => chapter 7 2022-01-11 16:04 steffenPage Number => 135 ff. 2022-01-11 16:04 steffenLine Number => 3933 ff. 2022-06-23 16:24 nick Note Added: 0005867 ==
[Issue 8 drafts 0001587]: exec special built-in should list PATH as environment variable
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1587 == Reported By:calestyo Assigned To: == Project:Issue 8 drafts Issue ID: 1587 Category: Shell and Utilities Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:2.14 Special Built-In Utilities Page Number:2366 Line Number:76656 Final Accepted Text: Resolution: Accepted Fixed in Version: == Date Submitted: 2022-05-22 02:09 UTC Last Modified: 2022-06-23 15:35 UTC == Summary:exec special built-in should list PATH as environment variable == Issue History Date ModifiedUsername FieldChange == 2022-05-22 02:09 calestyo New Issue 2022-05-22 02:09 calestyo Name => Christoph Anton Mitterer 2022-05-22 02:09 calestyo Section => 2.14 Special Built-In Utilities 2022-05-22 02:09 calestyo Page Number => 2366 2022-05-22 02:09 calestyo Line Number => 76656 2022-06-23 15:35 Don Cragun Status New => Resolved 2022-06-23 15:35 Don Cragun Resolution Open => Accepted ==
[1003.1(2016/18)/Issue7+TC2 0001538]: what -s is poorly described, uses the word "quit"
The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1538 == Reported By:andras_farkas Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1538 Category: Shell and Utilities Type: Error Severity: Editorial Priority: normal Status: Interpretation Required Name: Andras Farkas Organization: User Reference: Section:what Page Number:3437 Line Number:116041 Interp Status: Pending Final Accepted Text:https://austingroupbugs.net/view.php?id=1538#c5857 == Date Submitted: 2021-12-05 06:48 UTC Last Modified: 2022-06-23 15:29 UTC == Summary:what -s is poorly described, uses the word "quit" == Relationships ID Summary -- related to 0001563 Wording for what seem to imply odd beha... == Issue History Date ModifiedUsername FieldChange == 2021-12-05 06:48 andras_farkas New Issue 2021-12-05 06:48 andras_farkas Name => Andras Farkas 2021-12-05 06:48 andras_farkas Section => what 2022-02-17 09:02 Don Cragun Page Number => 3437 2022-02-17 09:02 Don Cragun Line Number => 116041 2022-02-17 09:02 Don Cragun Interp Status => --- 2022-02-17 15:57 geoffclare Note Added: 0005674 2022-02-17 17:00 geoffclare Note Added: 0005675 2022-02-17 17:02 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1538#c5675 2022-02-17 17:02 geoffclare Status New => Interpretation Required 2022-02-17 17:02 geoffclare Resolution Open => Accepted As Marked 2022-02-17 17:03 geoffclare Interp Status--- => Pending 2022-02-17 17:03 geoffclare Tag Attached: tc3-2008 2022-02-18 09:14 kreNote Added: 0005680 2022-02-18 09:39 geoffclare Note Added: 0005681 2022-02-18 14:39 andras_farkas Note Added: 0005682 2022-02-18 15:07 andras_farkas Note Added: 0005683 2022-02-18 19:20 kreNote Added: 0005687 2022-02-18 19:27 kreNote Added: 0005688 2022-03-25 17:08 agadminInterp StatusPending => Proposed 2022-03-25 17:08 agadminNote Added: 0005764 2022-04-26 11:08 geoffclare Note Added: 0005821 2022-06-20 15:02 kreNote Added: 0005854 2022-06-20 15:17 kreNote Edited: 0005854 2022-06-20 16:57 kreNote Edited: 0005854 2022-06-20 17:00 kreNote Edited: 0005854 2022-06-21 08:54 geoffclare Relationship added related to 0001563 2022-06-21 09:16 geoffclare Note Added: 0005857 2022-06-21 09:18 geoffclare Note Edited: 0005675 2022-06-21 09:20 geoffclare Note Edited: 0005857 2022-06-22 07:55 geoffclare Note Edited: 0005857 2022-06-23 15:29 geoffclare Interp StatusProposed => Pending 2022-06-23 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1538#c5675 => https://austingroupbugs.net/view.php?id=1538#c5857 ==
[1003.1(2013)/Issue7+TC1 0000906]: Ambiguity of abort() behavior racing with sigaction
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=906 == Reported By:dalias Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 906 Category: System Interfaces Type: Clarification Requested Severity: Editorial Priority: normal Status: Resolved Name: Rich Felker Organization: musl libc User Reference: Section:abort Page Number:560 Line Number:19406-19414 Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=906#c5851 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2014-12-18 02:10 UTC Last Modified: 2022-06-23 15:23 UTC == Summary:Ambiguity of abort() behavior racing with sigaction == Issue History Date ModifiedUsername FieldChange == 2014-12-18 02:10 dalias New Issue 2014-12-18 02:10 dalias Name => Rich Felker 2014-12-18 02:10 dalias Organization => musl libc 2014-12-18 02:10 dalias Section => abort 2014-12-18 02:10 dalias Page Number => unknown 2014-12-18 02:10 dalias Line Number => unknown 2015-03-26 15:38 Don Cragun Note Added: 0002607 2015-03-26 15:41 Don Cragun Page Number unknown => 560 2015-03-26 15:41 Don Cragun Line Number unknown => 19406-19414 2015-03-26 15:41 Don Cragun Interp Status => --- 2022-05-12 15:29 geoffclare Tag Attached: c99 2022-06-16 16:15 geoffclare Tag Detached: c99 2022-06-16 16:22 Don Cragun Note Edited: 0002607 2022-06-16 16:23 Don Cragun Note Edited: 0002607 2022-06-17 14:22 geoffclare Note Added: 0005851 2022-06-17 14:24 geoffclare Note Edited: 0005851 2022-06-23 15:23 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=906#c5851 2022-06-23 15:23 geoffclare Status New => Resolved 2022-06-23 15:23 geoffclare Resolution Open => Accepted As Marked ==
[1003.1(2016/18)/Issue7+TC2 0001590]: requirement for pr on an empty file doesn't match implementations
The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1590 == Reported By:geoffclare Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1590 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: Interpretation Required Name: Geoff Clare Organization: The Open Group User Reference: Section:pr Page Number:3109 Line Number:103939 Interp Status: Pending Final Accepted Text:See https://austingroupbugs.net/view.php?id=1590#c5866. == Date Submitted: 2022-06-20 10:57 UTC Last Modified: 2022-06-23 15:15 UTC == Summary:requirement for pr on an empty file doesn't match implementations == Issue History Date ModifiedUsername FieldChange == 2022-06-20 10:57 geoffclare New Issue 2022-06-20 10:57 geoffclare Name => Geoff Clare 2022-06-20 10:57 geoffclare Organization => The Open Group 2022-06-20 10:57 geoffclare Section => pr 2022-06-20 10:57 geoffclare Page Number => 3109 2022-06-20 10:57 geoffclare Line Number => 103939 2022-06-20 10:57 geoffclare Interp Status => --- 2022-06-20 16:20 Don Cragun Note Added: 0005855 2022-06-20 16:20 Don Cragun Status New => Interpretation Required 2022-06-20 16:20 Don Cragun Resolution Open => Accepted 2022-06-20 16:22 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=1590#c5855. 2022-06-20 16:22 Don Cragun Tag Attached: tc3-2008 2022-06-20 16:49 kreNote Added: 0005856 2022-06-21 09:30 geoffclare Note Added: 0005858 2022-06-21 09:30 geoffclare Status Interpretation Required => Under Review 2022-06-21 09:30 geoffclare Resolution Accepted => Reopened 2022-06-21 09:34 geoffclare Note Added: 0005859 2022-06-21 11:07 kreNote Added: 0005860 2022-06-21 13:46 geoffclare Note Added: 0005861 2022-06-21 14:00 geoffclare Note Edited: 0005861 2022-06-21 14:12 geoffclare Note Added: 0005862 2022-06-21 14:15 geoffclare Note Edited: 0005862 2022-06-21 14:16 agadminInterp Status--- => Proposed 2022-06-21 14:16 agadminNote Added: 0005863 2022-06-21 15:35 kreNote Added: 0005864 2022-06-21 15:37 agadminNote Deleted: 0005863 2022-06-21 15:49 agadminInterp StatusProposed => --- 2022-06-21 15:49 agadminNote Added: 0005865 2022-06-23 15:11 Don Cragun Note Added: 0005866 2022-06-23 15:13 Don Cragun Final Accepted Text See https://austingroupbugs.net/view.php?id=1590#c5855. => See https://austingroupbugs.net/view.php?id=1590#c5866. 2022-06-23 15:13 Don Cragun Status Under Review => Interpretation Required 2022-06-23 15:13 Don Cragun Resolution Reopened => Accepted As Marked 2022-06-23 15:15 Don Cragun Interp Status--- => Pending ==
[1003.1(2016/18)/Issue7+TC2 0001590]: requirement for pr on an empty file doesn't match implementations
The following issue NEEDS AN INTERPRETATION. == https://austingroupbugs.net/view.php?id=1590 == Reported By:geoffclare Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1590 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: Interpretation Required Name: Geoff Clare Organization: The Open Group User Reference: Section:pr Page Number:3109 Line Number:103939 Interp Status: --- Final Accepted Text:See https://austingroupbugs.net/view.php?id=1590#c5866. == Date Submitted: 2022-06-20 10:57 UTC Last Modified: 2022-06-23 15:13 UTC == Summary:requirement for pr on an empty file doesn't match implementations == Issue History Date ModifiedUsername FieldChange == 2022-06-20 10:57 geoffclare New Issue 2022-06-20 10:57 geoffclare Name => Geoff Clare 2022-06-20 10:57 geoffclare Organization => The Open Group 2022-06-20 10:57 geoffclare Section => pr 2022-06-20 10:57 geoffclare Page Number => 3109 2022-06-20 10:57 geoffclare Line Number => 103939 2022-06-20 10:57 geoffclare Interp Status => --- 2022-06-20 16:20 Don Cragun Note Added: 0005855 2022-06-20 16:20 Don Cragun Status New => Interpretation Required 2022-06-20 16:20 Don Cragun Resolution Open => Accepted 2022-06-20 16:22 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=1590#c5855. 2022-06-20 16:22 Don Cragun Tag Attached: tc3-2008 2022-06-20 16:49 kreNote Added: 0005856 2022-06-21 09:30 geoffclare Note Added: 0005858 2022-06-21 09:30 geoffclare Status Interpretation Required => Under Review 2022-06-21 09:30 geoffclare Resolution Accepted => Reopened 2022-06-21 09:34 geoffclare Note Added: 0005859 2022-06-21 11:07 kreNote Added: 0005860 2022-06-21 13:46 geoffclare Note Added: 0005861 2022-06-21 14:00 geoffclare Note Edited: 0005861 2022-06-21 14:12 geoffclare Note Added: 0005862 2022-06-21 14:15 geoffclare Note Edited: 0005862 2022-06-21 14:16 agadminInterp Status--- => Proposed 2022-06-21 14:16 agadminNote Added: 0005863 2022-06-21 15:35 kreNote Added: 0005864 2022-06-21 15:37 agadminNote Deleted: 0005863 2022-06-21 15:49 agadminInterp StatusProposed => --- 2022-06-21 15:49 agadminNote Added: 0005865 2022-06-23 15:11 Don Cragun Note Added: 0005866 2022-06-23 15:13 Don Cragun Final Accepted Text See https://austingroupbugs.net/view.php?id=1590#c5855. => See https://austingroupbugs.net/view.php?id=1590#c5866. 2022-06-23 15:13 Don Cragun Status Under Review => Interpretation Required 2022-06-23 15:13 Don Cragun Resolution Reopened => Accepted As Marked ==
[1003.1(2016/18)/Issue7+TC2 0001590]: requirement for pr on an empty file doesn't match implementations
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1590 == Reported By:geoffclare Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1590 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: Under Review Name: Geoff Clare Organization: The Open Group User Reference: Section:pr Page Number:3109 Line Number:103939 Interp Status: --- Final Accepted Text:See https://austingroupbugs.net/view.php?id=1590#c5855. == Date Submitted: 2022-06-20 10:57 UTC Last Modified: 2022-06-23 15:11 UTC == Summary:requirement for pr on an empty file doesn't match implementations == -- (0005866) Don Cragun (manager) - 2022-06-23 15:11 https://austingroupbugs.net/view.php?id=1590#c5866 -- 2022-06-20 16:20 Interpretation response The standard states the behavior of pr with an empty file, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: - The standard does not match existing practice. Notes to the Editor (not part of this interpretation): --- Make the changes in https://austingroupbugs.net/view.php?id=1590#c5862. Issue History Date ModifiedUsername FieldChange == 2022-06-20 10:57 geoffclare New Issue 2022-06-20 10:57 geoffclare Name => Geoff Clare 2022-06-20 10:57 geoffclare Organization => The Open Group 2022-06-20 10:57 geoffclare Section => pr 2022-06-20 10:57 geoffclare Page Number => 3109 2022-06-20 10:57 geoffclare Line Number => 103939 2022-06-20 10:57 geoffclare Interp Status => --- 2022-06-20 16:20 Don Cragun Note Added: 0005855 2022-06-20 16:20 Don Cragun Status New => Interpretation Required 2022-06-20 16:20 Don Cragun Resolution Open => Accepted 2022-06-20 16:22 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=1590#c5855. 2022-06-20 16:22 Don Cragun Tag Attached: tc3-2008 2022-06-20 16:49 kreNote Added: 0005856 2022-06-21 09:30 geoffclare Note Added: 0005858 2022-06-21 09:30 geoffclare Status Interpretation Required => Under Review 2022-06-21 09:30 geoffclare Resolution Accepted => Reopened 2022-06-21 09:34 geoffclare Note Added: 0005859 2022-06-21 11:07 kreNote Added: 0005860 2022-06-21 13:46 geoffclare Note Added: 0005861 2022-06-21 14:00 geoffclare Note Edited: 0005861 2022-06-21 14:12 geoffclare Note Added: 0005862 2022-06-21 14:15 geoffclare Note Edited: 0005862 2022-06-21 14:16 agadminInterp Status--- => Proposed 2022-06-21 14:16 agadminNote Added: 0005863 2022-06-21 15:35 kreNote Added: 0005864 2022-06-21 15:37 agadminNote Deleted: 0005863 2022-06-21 15:49 agadminInterp StatusProposed => --- 2022-06-21 15:49 agadminNote Added: 0005865 2022-06-23 15:11 Don Cragun Note Added: 0005866 ==
Re: POSIX xgettext: -K option description
Bruno Haible wrote, on 23 Jun 2022: > > https://posix.rhansen.org/p/gettext_draft > Lines 1202..1211 > > In line 1164, the argument to the -K option is called 'pattern'. > > Issue: In lines 1202..1211 it is called 'keyword'. > > Suggestion: Use the same term 'pattern' here as well, instead of 'keyword'. > > Rationale: In the 1st, 3rd, and 4th case, it is a misnomer to call the > argument a "keyword". I take your point about "keyword" not being appropriate when the option-argument is an empty string or has a colon and number(s) after the id. However, "pattern" isn't appropriate either as there is no pattern matching operation performed. I would suggest "keyword-spec", and I have put that in for now. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: POSIX xgettext example
Bruno Haible wrote, on 23 Jun 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 1293 > > Issue: The list of -K options is incomplete, as they don't handle the > dgettext_l, dcgettext_l, dngettext_l, dcngettext_l function invocations. > > Suggestion: Add these options: > -K gettext_l:1 -K dgettext_l:2 -K dcgettext_l:2 -K ngettext_l:1,2 -K > dngettext_l:2,3 -K dcngettext_l:2,3 > This was deliberate, so as to keep the command to a managable length. It is noted on line 1295 that "Additional -K options would be needed for the variants of the functions with an _l suffix if they are used." -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: POSIX msgfmt and newlines in strings
Bruno Haible wrote, on 23 Jun 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 1067 > > "Unlike shell command language strings, double-quoted strings in dot-po files > cannot contain a literal character." > > Issue: This sentence should be part of the specification of the dot-po file > format. > > Suggestion: Move this sentence from the APPLICATION USAGE section to the > EXTENDED DESCRIPTION section. This sentence is in APPLICATION USAGE because it is an observation about dot-po files that we felt was worth pointing out to application writers. The normative text already clearly does not allow newlines in strings, just from the first sentence describing the format (line 983): A dot-po file contains zero or more lines, with each non-blank line containing a comment, a statement, or a statement continuation. (Although I suppose a reader might wonder whether a string could be split across a statement and a statement continuation; they would soon realise it cannot when they read, later in the same paragraph, that a statement continuation is "a double-quoted string on a line by itself".) So I don't see the need to move the sentence as you request. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: POSIX gettext(): lifetime of returned values
Geoff Clare wrote: > We believe that all of your comments have now been addressed. ... Once > you have reviewed this last change, we plan to clean up the document Thanks for the prompt. I have reviewed the specifications of msgfmt and xgettext, and sent 7 comments about them. Bruno
POSIX xgettext: -K option description
https://posix.rhansen.org/p/gettext_draft Lines 1202..1211 In line 1164, the argument to the -K option is called 'pattern'. Issue: In lines 1202..1211 it is called 'keyword'. Suggestion: Use the same term 'pattern' here as well, instead of 'keyword'. Rationale: In the 1st, 3rd, and 4th case, it is a misnomer to call the argument a "keyword".
POSIX xgettext example
https://posix.rhansen.org/p/gettext_draft Line 1293 Issue: The list of -K options is incomplete, as they don't handle the dgettext_l, dcgettext_l, dngettext_l, dcngettext_l function invocations. Suggestion: Add these options: -K gettext_l:1 -K dgettext_l:2 -K dcgettext_l:2 -K ngettext_l:1,2 -K dngettext_l:2,3 -K dcngettext_l:2,3
POSIX xgettext and the -s option
https://posix.rhansen.org/p/gettext_draft Lines 1164, 1166, 1187, 1221-1222 Issue: The option '-s' has been found to be counter-productive in practice, and therefore has been deprecated in GNU gettext. See https://savannah.gnu.org/bugs/?61249 . Suggestion: Remove the '-s' option from the standard.
POSIX xgettext and the initial domain directive
https://posix.rhansen.org/p/gettext_draft Line 1183 "The first directive in each created dot-po file shall be a domain directive giving the associated domain name" GNU gettext currently does not do this. Solaris gettext does it. The msgfmt program allows the initial domain directive to be absent (see lines 996-998). What is the added value of this directive, since for msgfmt it is optional? In 99% percent of the cases, xgettext is used as part of a build system for a single domain. The author of that build system knows the domain perfectly well. There is no need to additionally store it in the dot-po file. Issue: Since this directive was not documented in https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html many PO file consumers will choke on this directive, once GNU xgettext implements the POSIX specification. Suggestion: Declare that it is implementation-dependent whether xgettext writes out a domain directive, when the output contains only entries for a single domain.
POSIX msgfmt and newlines in strings
https://posix.rhansen.org/p/gettext_draft Line 1067 "Unlike shell command language strings, double-quoted strings in dot-po files cannot contain a literal character." Issue: This sentence should be part of the specification of the dot-po file format. Suggestion: Move this sentence from the APPLICATION USAGE section to the EXTENDED DESCRIPTION section.
POSIX msgfmt and escape sequences in msgid and msgid_plural strings
https://posix.rhansen.org/p/gettext_draft Line 1031 "C-language escape sequences in message strings shall be processed as specified for character string literals in the ISO C standard ..." Issue: The way this is written, it is not possible to write, in a dot-po file: msgid "Program terminated.\n" Suggestion: This sentence should be extended to hold for *all* string literals in a dot-po file. So that C escape sequences can be used in particular in message_identifier (line 901) and untranslated_string_plural (line 902). Both GNU msgfmt and Solaris msgfmt do it like this.
POSIX msgfmt and universal-character-name escape sequences
https://posix.rhansen.org/p/gettext_draft
Line 1031
"except that universal-character-name escape sequences need not be supported."
Neither GNU msgfmt nor Solaris msgfmt treat universal-character-name
escape sequences specially. If an msgstr contains e.g. "\\u20AC", the
resulting string in the .mo file is
{ '\\', 'u', '2', '0', 'A', 'C', '\0' }.
Issue: Leaving it undefined whether \u escape sequences are recognized can
lead to mutual incompatibility of msgfmt implementations: Implementations
would differ in their interpretation of the dot-po file.
There is no good reason for leaving it undefined: There is already a
mechanism for specifying an encoding (charset=... in the header), and the
UTF-8 encoding is in widespread use for more than 10 years.
Suggestion: Change
"except that universal-character-name escape sequences need not be supported."
to
"except that universal-character-name escape sequences are not supported."
