Skip to content

JSE-28: record the Excel for Mac conformance check - #119

Merged
securedeveloper merged 2 commits into
mainfrom
jse-28-conformance-results
Nov 17, 2026
Merged

securedeveloper merged 2 commits into
mainfrom
jse-28-conformance-results

Conversation

@securedeveloper

@securedeveloper securedeveloper commented Nov 17, 2026 •

Copy link
Copy Markdown
Owner

Records the manual conformance check done on 2026-11-17. Only Excel for Mac was checked. Excel for Windows and Apple Numbers were not, and the docs now say so. For those apps only CI's LibreOffice and openpyxl checks apply. No files were saved from Excel, Numbers or Google Sheets for reader fixtures, and no #SPILL! file was made.

Results

Every corpus file opens in Excel for Mac with no repair prompt, and its checks pass.

Open item Result
a. indent maximum 250 Confirmed
b. built-in codes 37–40, 47 Confirmed, with Excel's own codes: #,##0_);(#,##0), #,##0_);[Red](#,##0), #,##0.00_);(#,##0.00), #,##0.00_);[Red](#,##0.00), mm:ss.0. These differ from the ECMA-376 table we use; the engine and corpus are aligned in a separate PR (JSE-F4). 37 was reported as #,##0_);#,##0), read as a transcription slip for the opening parenthesis; to be confirmed.
c. Display rows (§5.7.4) Not verified (differences not recorded)
d. locale ids 27–36, 50–58 Not verified (locale and results not recorded; no East Asian locale tried)
e. theme index order Confirmed
f. indexed 64/65 Confirmed
g. column widths, Calibri 11 Confirmed in characters; pixel widths (Windows values) not checked
h. History; 31-character emoji name Not verified (not recorded)
i. 64,000 cell formats Confirmed (the file opens; a file over the limit was not tried)
#SPILL! storage Open: no file made

Changes

  • test/conformance/corpus.ts: a MANUAL_CHECK record (date, apps checked and not checked) and a result for each open item.
  • test/conformance/checklist.ts → regenerated docs/conformance.md: a Results section, the per-app columns filled in (pass / opened; result not recorded / not checked), and a Result column in the open-items table.
  • docs/api.md: confirmed items say (confirmed in Excel for Mac, 2026-11-17) instead of [to verify]. §11.2 records Excel's codes for 37–40 and 47. §9.2 says which apps were actually checked and that real-app files are not reader fixtures yet. The #SPILL! marker says no Excel 365 file has been checked.

Docs and test metadata only. Nothing shipped changes, so no changeset.

The corpus was checked by hand in Excel for Mac on 2026-11-17: every
file opens with no repair prompt and its checks pass. Excel for Windows
and Numbers were not checked; real-app reader fixtures and a #SPILL!
file were not made.

- corpus.ts: a MANUAL_CHECK record (date, apps checked and not checked)
  and a result per open item.
- checklist.ts / docs/conformance.md: a Results section, the per-app
  columns filled in, and a Result column for the open items.
- Confirmed: indent maximum 250, theme index order, indexed 64/65,
  column widths in characters (Calibri 11), a file with 64,000 cell
  formats. Their [to verify] markers in docs/api.md now say "confirmed
  in Excel for Mac, 2026-11-17".
- Not verified (not recorded): built-in codes 37-40 and 47, the Display
  rows, the locale-dependent ids, the sheet-name renames. For 39, 40
  and 47, LibreOffice's codes differ from the ECMA-376 codes the docs
  use; that is recorded as an open question.
- docs/api.md 9.2 says which apps were checked, and that Excel,
  Numbers and Google Sheets files are not reader fixtures yet; the
  #SPILL! item says no Excel 365 file has been checked.
…40 and 47

Excel uses #,##0_);(#,##0), #,##0_);[Red](#,##0), #,##0.00_);(#,##0.00),
#,##0.00_);[Red](#,##0.00) and mm:ss.0, which differ from the ECMA-376
table; the engine is aligned in JSE-F4. 37 was reported without its
opening parenthesis and is read as a transcription slip, to be
confirmed. Open-item rows in the per-file tables now point to the
open-items table for their result.
@securedeveloper
securedeveloper merged commit 51eb21e into main Nov 17, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant