Real tables in the field (tracking)

Open
  • Is something wrong?
#152 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
accessibility, desktop

Research direction

Read decisions-2026-11-05-records.md and research 19-tables.md first; they describe the storage and design decisions. The issue outlines table parsing, editing, paste, and accessibility work, but says accessibility still needs design and spans several subsystems. Done means implementing the specified table behavior while keeping older FLEx compatibility and honoring the listed scope limits.

Written by the indexing model from the issue text.

Description

Owner decisions Q73-Q79 and Q77' (decisions-2026-11-05-records.md; design in research 19-tables.md):

  • Storage: one paragraph per row in the existing Table Row style (plus a header-row style); cells separated by a ' | ' run in a Table Cell Separator character style (host-renamable); a caption paragraph in a Table Caption style after the table. No model change; readable in older FLEx.
  • Markdown: standard pipe tables plus Pandoc's 'Table: caption'; grid table when a cell holds a line break; alignment colons read and dropped with an info note.
  • Editing: tables derived from the flat paragraph list (TableMap); Tab next cell / adds a row in the last cell; Enter and Shift+Enter give a line break in a cell; Enter on an empty last row leaves; each table command one undo step; cell selection; add/remove rows and columns.
  • Paste: tab-separated text at a paragraph boundary becomes a table; 'Paste as table' too.
  • Accessibility: one item per cell (Avalonia has no UIA grid/table patterns: to design).
  • Not in scope: widths, alignment, merged cells, borders.
  • Related: block-features setting, #137 (p161), #144 (large tables).
Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
43

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sillsdev/SIL.TextEditing

All issues in sillsdev/SIL.TextEditing

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.