Error Context: 'm 29.999999,966.99995 c 2.165728,0.62971 2,2.92139 2,4 v 6 l 5.500488,2.93602 v -0.94881 h 1.999512 v 1.87166 l 5.500488,2.53858 v 3 l -0.242802,-1.07127 -5.461299,-0.96633 c -0.142213,0.55588 0,0.96633 -0.830021,1.8397 -0.834042,-0.87337 -0.706803,-1.52334 -0.834042,-2.14146 l -3.632812,-0.66064 h -1.999512 c _0,2.46655 -10e-7,4.60254 -0.798688,9.063.'
Unhandled exception:
System.Exception: Unexpected char 'e', expected one of 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, ., +, -
   at SvgPathParser.AcceptChar(Char[] list)
   at SvgPathParser.ParseNumberGeneric(Boolean allow_sign)
   at SvgPathParser.ParseCoordinate()
   at SvgPathParser.ParseCoordinatePair()
   at SvgPathParser.ParseCoordinatePairTuple(Int32 tuple_size)
   at SvgPathParser.ParseCoordinatePairTupleSequence(Int32 tuple_size)+MoveNext()
   at SvgPathParser.ParseCurveTo()
   at SvgPathParser.ParseDrawToCommand()
   at SvgPathParser.ParsePath()
   at SvgPathParser.Parse(String str, IPathRenderer renderer)
   at SvgConverter.TranslateNodes(AnalyzeResult data, TvgStream stream, SvgNode node)
   at SvgConverter.TranslateNodes(AnalyzeResult data, TvgStream stream, SvgNode node)
   at SvgConverter.TranslateNodes(AnalyzeResult data, TvgStream stream, SvgNode node)
   at SvgConverter.ConvertToTvgText(SvgDocument document)
   at Application.Main(String[] args)

Proposed solution: add "e" and "E" to the AcceptChar() check in svg2tvgt.cs, as float.Parse() seems to handle the exponent notation already.

Version: In lieu of a semantic version (why no version numbers?), the Windows executable's SHA1 is f2068828d9ccead7bfdeb0cd950ec23a07e78ec8, downloaded from your site 4/30/2024.

If so, how ?

Could you test the build using latest nightly Zig?

The author of https://github.com/RazrFalcon/resvg said it might be easier to use resvg as a code base for the SVG converter:

https://news.ycombinator.com/item?id=29637778

This is something that would allow tvg-text to also implement the svg => tvg conversion by linking the Rust code as an object file

Currently, no line caps are emitted to SVG. This is wrong as the rendering will differ between TinyVG rendering and SVG rendering.

Currently, the document parser is only accessible from Zig. Add a interface to the C api

Would it be possible to add a partial rendering function to TinyVG?
Typically, on embedded system, we don't have enough memory to store complete picture buffer in memory. So most system simply call the drawing loop multiple time, each time with a different drawing window.

Applied to a vector format, it means adding a "top/bottom/left/right" clipping to the rendering function so the rendering only happen within the same buffer, but a different output area of the image. That buffer is then transferred to the screen, and the rendering is called again with the next window.

Will it by availeble on nuget.org for winforms .net framework

Currently, only a software renderer is provided. This should be changed in a way that the SDK supports exporting GPU usable data (export set of triangles).

This feature should provide:

• Exporting a set of triangle data
• Export a set of material definitions/draw calls
• Allow configurable precision for triangulation of round shapes
• Agnostic to rendering api (support Vulkan, OpenGL, DirectX, …)

Observed this being used in some SVGs saved in Inkscape, might not be something that's actually coming from there specifically but possibly some other conversion (e.g. FontForge). Currently, it's unhandled, which sets the image to use magenta, which can hide some other things like alpha issues when checking against images.