Skip to content

Known limitations

ariana-report is young. These are the limits to know about before you build on it.

Persian and Arabic text in PDFs needs a registered font that has those letters (see Fonts). Without one, the standard PDF fonts draw ? for each letter, and a warning is reported.

The bidirectional algorithm used for PDFs covers implicit levels, numbers and paired brackets. Explicit embedding and isolate controls (U+202A to U+202E, U+2066 to U+2069) are ignored; LRM and RLM work. Bracket pairs are mirrored but not matched across a line (rule N0), which rarely matters in report text.

  • A band that does not fit on a page moves to the next page. Bands taller than a page are clipped, with a warning.
  • Text is measured with the standard PDF font metrics or with the fonts you register. If the browser shows a different font than the one measured, line breaks can differ slightly from the PDF.
  • Right-to-left layout of whole reports (mirrored column order) is not automatic. Place the components right to left in the template, as in the Persian examples.

PNG and JPEG only in PDF and Excel. SVG and WebP images are not supported.

  • Dates in non-Gregorian calendars are exported as text.
  • Single-sheet mode leaves out page headers, footers and repeated headers so that data stays contiguous.

The standard font metrics (about 130 kB) are part of the core bundle, because text is measured while the report is laid out. The core package is about 80 kB gzipped. PDF and Excel libraries load only when you export.

  • Components cannot be rotated.
  • Bands cannot be reordered by dragging; use the Report properties to add and remove bands.
  • Multi-selection is limited to components of one band.