Dragoș Tiselice

In the case of Romanian specifically, it seems like only en.wiktionary.org has complete inflection tables compared to the ro.wiktionary.org source that has partial ones. Since I'm not familiar with the...

This is something I thought about but ended up decided against it because it hides a trade-off behind the scenes. A solution could be iterating through all the geometry, finding...

@bcolloran I tried updating to the newest version of Vello and testing it on Linux with Vulkan (Nvidia driver) with mixed results: it seems to run fine but ends up...

I cannot give you a timeline, but I can tell you that this requires some planning before. Integrating our renderer with wgpu will likely require exposing some functionality on the...

`cargo update` should not be needed to run the example. It builds fine with just `cargo build` on aarch64 macOS.

`rive-rs` comes with a Vello back-end implementation included. You could get the path data by listening in on that implementation, but this pretty much means copy-pasting the implementation. Another way...

You could achieve that by listening to [`Renderer::draw_path`](https://github.com/rive-app/rive-rs/blob/main/rive-rs/src/renderer.rs#L124) after calling [`Scene::advance_and_maybe_draw`](https://github.com/rive-app/rive-rs/blob/main/rive-rs/src/scene.rs#L65). This will only give you the path data that changed from last frame though.

@simbleau, thank you for reporting. This shouldn't be too hard to fix since we already support wasm. I'll try to fix this next week. It's likely that we're missing some...

Since we're using C++ stdlib in the C++ runtime, it seems like we'll need to use emscripten to compile the runtime then link it with `rive-rs`. I might take a...

Building `wasm32-unknown-emscripten` instead of `wasm32-unknown-unknown` works fine, it seems. Then, linking with other `wasm32-unknown-unknown` libs should not be a problem.