All notable changes to the "atf" extension will be documented in this file.
Check Keep a Changelog for recommendations on how to structure this file.
- Glossary files (
*.glo) have now a context menu for executing commands on the current project, when the file is open on the Oracc server.
- Lemmatisation and validation of files with Line Feed (LF) line ending, for example those typically created on Unix systems, now works on Windows without throwing errors.
- Glossary files (
*.glo) have now a searchable and clickable outline of letters and entries. - Validation and lemmatisation of ATF files support files with multiple texts, as long as they share the same project code.
- Basic syntax highlighting for glossary files (
*.glo)
- Low-level validation/lemmatisation log messages are no longer shown to the user whithin the console output in VS Code, but they are still saved to the log file.
- Word wrapping is enabled by default for ATF and glossary files
- Submitting an ATF file for validation/lemmatisation requires the file to have
*.atfextension. This is consistent with the expectation of the server for the file to have this extension, and prevents users from accidentally forgetting to set the right extension - More detailed logging messages are saved to the log file during server communication, for easier debugging
- More generous waiting time is set during server communications
- Some dependencies of Nisaba have been updated to address security vulnerabilities
- Initial release