Better handling of custom markers
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
When the source project defines a custom marker that is not in the target, the marker is not recognized properly in the target when inserting pretranslations.
This is the Serval spin-off of https://github.com/sillsdev/silnlp/issues/602. Following the discussion there, maybe the best thing to do is just to strip/ignore custom markers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion in silnlp issue 602, then trace how custom markers are handled when pretranslations are inserted. Clarify whether source-only markers should be stripped or ignored, and consider the issue complete when those markers no longer prevent correct recognition in the target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100