What Balise does not do

Deliberate limits, so you do not look for a feature that is missing.

This page saves you time. A limit known in advance is less costly than one discovered in the middle of a task.

What Balise will not do to your files

  • Balise does not convert a data file to a proprietary format to edit it.
  • Balise does not apply a repair without showing you a preview.
  • Balise does not normalize an entire file when one cell changes.
  • Balise does not remove Markdown syntax it cannot render.
  • Balise does not overwrite a file modified by another application.
  • Balise does not reconnect a recovered session to its original file until you save it yourself.
  • Balise does not apply display preferences to a data file whose content no longer matches.
  • Balise does not claim a very large file is editable when it has only loaded a preview.

Features Balise does not have

Balise does not write to Git. There are no commits, remote pushes or branch management. Review and commit your changes with your usual Git tools.

Balise is not a calculation spreadsheet. There are no chains of recalculated formulas, charts or pivot tables. The grid is for inspecting, correcting and preparing data, rather than modeling.

Balise does not edit imported office formats. It can read DOCX, XLSX or ODS to create a Markdown or CSV copy, but it does not modify the source or save to those formats.

Balise does not remember the layout of a Mermaid diagram. The engine calculates the layout because the format cannot express arbitrary positions.

Balise does not synchronize anything. There is no remote service, real-time collaboration, shared comments or document sharing.

Balise does not generate images.

What remains your responsibility

Balise keeps local history and recovery copies. Neither replaces a backup.

History is bounded, lives on this Mac and does not follow the file when you send it elsewhere. Continue using Git or a backup for anything that matters.

See Local versions and recovery.