Problems with 'v' in Latin-Bopomofo (and Latin-NumericPinyin)

Description

In pinyin, the letter 'v' is officially unused, but is often used as an alternate for 'ü'. Either can have tones; there are composed characters for 'ü' plus all tone marks, but not for 'v' plus all tone marks:

  • 1st, "ǖ" U+01D6, or "v̄" v plus U+0304

  • 2nd, "ǘ" U+01D8, or "v́" v plus U+0301

  • 3rd, "ǚ" U+01DA, or "v̌" v plus U+030C

  • 4th, "ǜ" U+01DC, or "v̀" v plus U+0300

However, the Latin-Bopomofo does not handle 'v' plus tone marks correctly, because its filter currently excludes [:Mn:] (it also does not handle input using fully or partly decomposed 'ü with tone marks). We should to the following:
1. In Latin-Bopomofo, change the forward filter from ":: [ [:Latin:][1-5] ];" to ":: [ [:Latin:][:Mn:][1-5] ];".
2. As an efficiency step, we can also add the conversion rule "[ln] { v → ü;" before calling the transform rule ":: Latin-NumericPinyin (NumericPinyin-Latin) ;", then we can eliminate all of the specific one-way conversions for 'v':

3. Finally, in Latin-NumericPinyin’s definition of $vowel, we should change as follows (add 'v', and drop composed 'ü since at this point we a re working with NFD) - adding 'v' does not seem necessary for correct functioning in at least some cases, but it is better for documentation in any case:

xpath

None

locale

None

Priority

major

Assignee

Peter Edberg

Reporter

Peter Edberg

Reviewer

Mark Davis

Labels

None

Components

Fix versions

phase

rc
Configure