Clipboard follow-ups: unknown ws ids in the Markdown form, plain-text joiner, unordered forms

Open
  • Is something wrong?
#123 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

Start by tracing TsStringClipboard.ToPayload and the clipboard form registration and PasteOrder handling mentioned in the issue; inspect issue #74 for the unknown writing-system behavior. Check existing tests for clipboard payload text, unknown writing-system ids, and registered forms omitted from PasteOrder. Done means these three follow-ups have defined behavior and regression coverage.

Written by the indexing model from the issue text.

Description

From the field-clipboard batch:

  • The future FieldWorks Markdown clipboard form must keep an unknown writing-system id as-is on read, or the writing-system mapping and notice never fire (#74).
  • TsStringClipboard.ToPayload builds its plain text with "; " while the field joins its own plain text with "\n"; pick one (FieldWorks' own copy uses "; " between fields).
  • A form that is registered but left out of PasteOrder is silently never read; warn or append it.
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.