read's layer ID attribution doesn't appropriately handle well-formed inkscape layers in some cases

[abey79]

This happens e.g. with layers named xxxx1 and yyyy1. The digit extraction logic merges both layers into layer 1. This logic might make sense based on id attributes, but definitely doesn't make sense when multiple, top-level <g inkscape:groupmode="layer" ...> element exist.

Example file:

Relevant discord discussion: https://discord.com/channels/499297341472505858/748589023731122277/1067315996727181383

[oskay]

If you're making a change, you might consider matching the AxiDraw layer number syntax ( https://wiki.evilmadscientist.com/AxiDraw_Layer_Control#Syntax ), where only leading numbers (after stripping whitespace) are considered, and otherwise the layers are considered independent.

[abey79]

I'm unsure how to deal with this tbh. Surely, having green1 and blue1 merged into a single layer (with ID 1) is surprising. So would be to have 01 layer 01 end up with ID 101, as is currently the case. However, the current design does the right thing with layer 1 and layer 3, which I'm somewhat reluctant to break.

I'm thinking of at least considering "the first group of contiguous digits", as opposed of the current "all digits", for 1.13. This removes one WTF edge case but doesn't address this particular issue.