smarter number sequences - 'one one twenty one'

Found another head-scratcher… At first I thought it was merely a limitation, but the issue appears to only pop up if there are an even number of individual digits in front of a multi-digit value.

Hopefully this example explains more clearly:

const nlp = require('compromise')
const arr = str => nlp(str).values().out('array')

// digits leading
console.log(arr('one twenty one')) // ['one', 'twenty one']
console.log(arr('one one twenty one')) // ['one one twenty one'] (x)
console.log(arr('one one one twenty one')) // ['one', 'one', 'one', 'twenty one']
console.log(arr('one one one one twenty one')) // ['one one one one twenty one'] (x)

// digits trailing
console.log(arr('one twenty one one')) // ['one', 'twenty one', 'one']
console.log(arr('one twenty one one one')) // ['one', 'twenty one', 'one', 'one']

I’m merely using “one” and “twenty one” to demonstrate the point, but it occurs with any even number of individual digits in front of a multi-digit value, but not after. 🤔

FYI, our team is trying to use this fantastic library to capture “creative pronunciations” of values.

[hboylan]

I believe the ultimate goal here is to capture nominal values in addition to cardinal and ordinal.

My thought is that the lumping/splitting would still need to be enhanced to capture more advanced number sequences. Then, there might be another step to determine whether the value is nominal. Maybe by using a separate toNominal() function or something…

[hboylan]

Great, I’ll take a look at this.

Enjoy your vaca! 😎