[BUG] Scanner doesn't parse Volume # with decimal in it #103

New issue

Closed

opened 2026-02-20 00:17:09 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 00:17:09 -05:00

Owner

Originally created by @typhooncarr on GitHub (Nov 23, 2021).

Scanning books with a Volume #0.5, or any decimal point, the parser fails and just uses the whole number (ie. 0)

Correct Entry for the example above

Originally created by @typhooncarr on GitHub (Nov 23, 2021). Scanning books with a Volume #0.5, or any decimal point, the parser fails and just uses the whole number (ie. 0) ![image](https://user-images.githubusercontent.com/94880451/143155320-39e9344e-37c8-4cb6-a5cb-86ea77d7505e.png) Correct Entry for the example above ![image](https://user-images.githubusercontent.com/94880451/143155411-7ebbacc8-6af5-445d-a163-8ab723738213.png)

deekerman closed this issue

2026-02-20 00:17:09 -05:00

deekerman commented

2026-02-20 00:17:10 -05:00

Author

Owner

@advplyr commented on GitHub (Nov 26, 2021):

I didn't set it up to parse decimals originally. I just released v1.6.29 that will parse volumes with decimals.

@advplyr commented on GitHub (Nov 26, 2021): I didn't set it up to parse decimals originally. I just released `v1.6.29` that will parse volumes with decimals.