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
{{ message }}
This repository was archived by the owner on Nov 6, 2021. It is now read-only.
Apparently, the ptBR locale uses "." for comma separators AND for thousand separators. This makes it much more complicated to detect ANY number properly, even if the current implementation seems to work for higher AK levels.
I'm not really sure what to do about this right now, as there are also issues with trailing zeroes and any workaround I came up with didn't really solve the problem correctly. On the other hand, I also don't want to rewrite the entire scanning algorithm just for this.
Apparently, the ptBR locale uses "." for comma separators AND for thousand separators. This makes it much more complicated to detect ANY number properly, even if the current implementation seems to work for higher AK levels.
I'm not really sure what to do about this right now, as there are also issues with trailing zeroes and any workaround I came up with didn't really solve the problem correctly. On the other hand, I also don't want to rewrite the entire scanning algorithm just for this.