Consider the phrase `るゔぃは`, which corresponds to `r'uviha`. The `る` character is `r'u`, `ゔぃ` is `vi`, and `は` is `ha`.
The current mechanism for Japanese splits the `ゔ (U+3094)` character into two characters, `う (U+3046)` and `U+3099` (the dakuten character).
Alone, `ゔぃ` is converted into `vi` without a hitch. However, since there exists a rule for `るう`, this gets converted into `r'u:`, leaving behind a dangling `U+3099 ぃは`. The leading two characters doesn't have a corresponding rule and defaults to `Japanese letter Japanese letter`.
Thus, instead of `r'uviha`, the result becomes `r'u: Japanese letter Japanese letter ha`.

Disclaimer: I am not a native speaker of Japanese.
Japanese Dakuten separation lead to incorrect conversion
This is a GitHub Issue
repo:espeak-ng
owner:espeak-ng
Title : Japanese Dakuten separation lead to incorrect conversion
Issue date:

--- start body ---
Consider the phrase `るゔぃは`, which corresponds to `r'uviha`. The `る` character is `r'u`, `ゔぃ` is `vi`, and `は` is `ha`.
The current mechanism for Japanese splits the `ゔ (U+3094)` character into two characters, `う (U+3046)` and `U+3099` (the dakuten character).
Alone, `ゔぃ` is converted into `vi` without a hitch. However, since there exists a rule for `るう`, this gets converted into `r'u:`, leaving behind a dangling `U+3099 ぃは`. The leading two characters doesn't have a corresponding rule and defaults to `Japanese letter Japanese letter`.
Thus, instead of `r'uviha`, the result becomes `r'u: Japanese letter Japanese letter ha`.

Disclaimer: I am not a native speaker of Japanese.
--- end body ---
