# Improvements

##  **Search**

search at sentence level.Hilight words that match a search string  eg <https://markjs.io/>

* ✅ Highlight all instances of a word in a text,
* 𐄂 preferably with slight fuzziness so misspellings and close words are counted (i.e. questions matches with question too)
* 𐄂 Search for a word or phrase and filter only the sections that contain those words or phrases, preferrably fuzzy

## 𐄂 filter

&#x20;𐄂  filter and return only matches in transcription

<http://fusejs.io/><br>

## ✅ **Improve readability in transcription (for speechmatics)**

* speechmatics breaking words into lines for formatting for readability
* as well as break paragraphs into different speakers speechmatics json<br>

{% embed url="<https://github.com/OpenNewsLabs/autoEdit_2/blob/master/lib/interactive_transcription_generator/transcriber/speechmatics/speechmatics_sample_output.json>" %}

\
autoEdit converting speechmatics to autoEdit

{% embed url="<https://github.com/OpenNewsLabs/autoEdit_2/blob/master/lib/interactive_transcription_generator/transcriber/speechmatics/convert_json.js>" %}

[ ](https://github.com/OpenNewsLabs/autoEdit_2/blob/master/lib/interactive_transcription_generator/transcriber/speechmatics/convert_json.js) <br>

## **𐄂  improved paper edit view selection**

Eg

* in autoEdit
* Paper editing by
* click in word
* click out word
* confirm
* moves to paper-edit function

Out of scope for this version<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://autoedit.gitbook.io/documentation/master-1.0.13-1/roadmap/roadmap-features-improvements-next-up.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.