FAQ
Frequently asked questions
Short answers for the parts people usually ask about first.
The API is free to try, premium keys are generated from the app, and the browser demo still works without a key.
How do I start the local server?
Run start-swagger.bat from the project root. It builds the Release output if needed, waits for /health, and opens the demo automatically.
Can I point the demo at another API host?
Yes. Use the API host field in the demo to point the preview at another deployment. That keeps the local editor unchanged while the renderer calls the host you provide.
Why aren't my labels rendering at all?
If you are calling the API from a browser on a different origin, make sure the target host allows CORS. Some firewalls and proxies also strip CORS headers, which breaks browser requests even when the backend itself is healthy. If you are not using a browser client, treat a failure here as a bug and include the Ngt when you report it.
How can I render Cyrillic, Greek, Chinese, Japanese, Korean, Arabic, or other text?
Use the NGT text-field escape sequences when you need glyphs outside the plain Windows-1252 range. For example, use \<UNIC(...)> for Unicode symbols in text fields and \<ASC(...)> when you need a literal byte value. You will also need a font that actually contains the glyphs you want to print. The built-in printer fonts cover Latin text well, but most non-Latin scripts need a custom font uploaded to the printer. The browser demo can use fonts with those glyphs, and the same rule applies to physical printers.
What is optimized for throughput?
The native renderer is pooled by profile, response compression is enabled, image bytes are optional, and the batch endpoint processes many jobs in parallel.