[^] ACTION-REQUIRED -- ballot of optional whitespace for complex messages

[aphillips]

Per the discussion in the 2024-07-29 teleconference (along with preceding calls on the same topic), there has been a call for voting on the resolution of the issue raised in #809 as part of the LDML46 version of the specification.

WORKING GROUP BALLOT

Please read the instructions CAREFULLY before responding.

Please carefully read the design document before responding.

Balloting Instructions

This is a simple vote. Please choose between options (A) or (B).

The deadline is 1700 (5 PM) in the America/Los_Angeles time zone on Sunday, 4 August 2024 Votes received after the deadline will be considered at the discretion of the chair.

• Anyone MAY submit exactly one vote.
  • Working group participants votes will be counted as a full vote.
  • Working group observers votes are not counted, but can be considered by the working group.
• You MAY edit, change, or delete your vote up until the deadline.
• Votes MUST be submitted as a comment on this github issue.
  Group members who cannot submit a comment on this issue should contact the chair (@aphillips) for assistance.
• Votes MUST contain only a vote for (A) or (B). Write in votes are not acceptable.
• You MUST NOT comment on the votes of others in this issue. "Electioneering" or non-voting commentary is not permitted in the issue except the chair may seek clarification of a vote. Use Discussion issue for #848: balloting of optional whitespace at complex message start #849 to discuss.

Candidates

There are two options.

(A) Complex messages MUST NOT start with whitespace

This is the current WG consensus. Complex messages must start with a declaration (. followed by a keyword) or with pattern quotes ({{). Anything else is a simple pattern.

(B) Complex messages MAY start with whitespace; the first non-whitespace character of a simple-message MUST NOT be .

This would permit optional whitespace before the start of a complex message. Whitespace at the start of a simple message remains significant (part of the pattern). Note that the body of a well-formed complex message is not a valid simple message.

[aphillips]

(chair hat off)

My vote: B

[eemeli]

B

[catamorphism]

B

[lucacasonato]

B

[macchiati]

B

…

On Thu, Aug 1, 2024 at 3:07 PM Luca Casonato ***@***.***> wrote: B — Reply to this email directly, view it on GitHub <#848 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLEMHCZE4VV4K7RNULLR3ZPKWTFAVCNFSM6AAAAABLWSNWCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUGA4TKNJUHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[echeran]

A

[mihnita]

B

[aphillips]

Thanks to everyone who voted. The telecon on 2024-08-05 found a consensus for B (I was not present). Closing this issue.