Hotwords encoding for phonemes

[w11wo]

Hi. I have a phoneme-based Zipformer model.

Before this PR, I was able to apply hotwords encoding for phoneme sequences, e.g. ɪ z/dʒ ʌ s t/b ɛ s t, following the older implementation of e.g. Chinese character hotwords encoding. But now, I noticed that the Chinese character hotwords encoding have changed from 深 度 学 习 (whitespace between chars) to 深度学习 (no whitespace). And I assume the string parser will simply iterate through the non-whitespace characters in the string sequence.

This, however, breaks my use case, since phoneme sequence with digraphs, e.g. dʒ ʌ s t will be incorrectly split to d ʒ ʌ s t. The issue is that my model's vocab supports digraph and requires the old implementation.

Is it possible to add another modeling unit, other than the currently supported ones (cjk, BPE, cjk+BPE)? Maybe instead of iterating for every non-whitespace character, split by whitespace first? This new modeling unit can hopefully support other use cases similar to mine.

Massive thanks for all the work and help thus far!

[csukuangfj]

@pkufool Could you have a look?

[pkufool]

Emm, May be I we can add a option like do-not-tokenize, I think it should fix your issue.

[pkufool]

For now, I think you can use the older version, v1.9.24 .

[w11wo]

@pkufool Yes, the do-not-tokenize option sounds good.

I can stick to older versions for now, but I wanted to try the customizable per-word hotwords scores, which comes in the latest releases only, hence the need for this new feature.

[pkufool]

@w11wo OK, will make a PR.

[w11wo]

Hi @pkufool, is there an update on the PR?

[pkufool]

Hi @pkufool, is there an update on the PR?

There is an on-going PR https://github.com/k2-fsa/sherpa-onnx/pull/1039

[w11wo]

Thank you so much @pkufool. Looking forward to it getting merged.

[DavidSamuell]

Hi @pkufool , I'm encountering the same issue as @w11wo . I was wondering if PR #1039, which enables pre-tokenize hotwords, will be merged into the master branch? Thank you! 🙏