You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been considering if it would be feasible to convert an SVG back to the native remarkable file format, so that existing paper notes could be digitized as native notebooks on the remarkable (and support all the existing features).
This project looks like the best home for such a tool, but I wanted to gather your opinion on if it would be at all feasible. The first problem I can think of is that there are a lot of elements in the SVG format that would not neatly map to anything the remarkable supports. However I wonder if a simplified case (using only paths) might be workable for written documents.
The text was updated successfully, but these errors were encountered:
I would consider this probably, due to dependencies on an SVG parser library, a lot of decisions on serialization of SVG elements to the visible grey spectrum on the device, etc. a good dependent project that just uses the API in this project to write the final .rm files.
Now that we have copy/paste on the rM, it would be great to have SVG2rM conversion. It will allow us to have notebooks with stock drawing primitives and such to be copied over to something you're working on.
I've been considering if it would be feasible to convert an SVG back to the native remarkable file format, so that existing paper notes could be digitized as native notebooks on the remarkable (and support all the existing features).
This project looks like the best home for such a tool, but I wanted to gather your opinion on if it would be at all feasible. The first problem I can think of is that there are a lot of elements in the SVG format that would not neatly map to anything the remarkable supports. However I wonder if a simplified case (using only paths) might be workable for written documents.
The text was updated successfully, but these errors were encountered: