While reviewing the implementation of Code93Reader, I noticed that it uses a function called OneToFourBitPattern for pattern decoding. Interestingly, this approach seems to be specific to Code93 and isn't used in Code128Reader, which instead relies on NormalizedE2EPattern and DecodeDigit(PatternMatchVariance) for pattern matching.

This raises a few questions:

1. Is there a particular reason why OneToFourBitPattern is preferred for Code93?

2. Would it be feasible (or even beneficial) to unify the pattern matching logic by using NormalizedE2EPattern and DecodeDigit both in Code93 as well, similar to Code128?

Thanks in advance for any insight.