Advanced Telex
Advanced Telex ships on all five platforms: macOS, Windows, Linux, iOS, and Android. This page describes the V5 specification the implementation follows.
Advanced Telex is a separately selectable mode. It inherits all behavior from the current Telex mode and adds common Full Telex shortcuts. The current Telex mode remains unchanged.
V5 scope
| Key | Result in Advanced Telex |
|---|---|
] | ư |
[ | ơ |
w while the syllable has no vowel yet | ư |
Vowels created by these shortcuts accept tone marks and participate in all existing Telex rules just like vowels created through canonical sequences.
t] → tư
m[ → mơ
tr][ngf → trường
ng][if → người
w → ư
wf → ừ
thw → thư
giwx → giữ
wngf → ừng
The ] → ư, [ → ơ pair follows what UniKey actually does (the engine shared by
UniKey for Windows and its Linux ports) and OpenKey, so UniKey users still get ươ from
][. Note that the UniKey manual prints
the pair the other way round; Funput follows UniKey's behavior, not its manual. Funput
calls this mode “Advanced Telex” to distinguish it from the safer default Telex mode.
w after an onset
w is the ư key anywhere the syllable has no vowel yet, not only at the start of a
word: thw → thư, nhwng → nhưng. The gi onset counts as having no vowel, since
its i is a medial glide: giwx → giữ, giwax → giữa. Only q is excluded, as
no syllable reads qư.
In exchange, a w typed straight after the onset no longer waits to mark a later vowel
the way it does in standard Telex:
| Keys | Telex | Advanced Telex | Other ways in Advanced Telex |
|---|---|---|---|
cwon | cơn | cươn | conw, cown, c[n |
giwof | giờ | giuờ | giowf, gi[f |
The ươ rhyme still resolves: thwongf → thường, ngwoif → người.
Inherited behavior
Advanced Telex must share the Telex implementation and inherit:
- Free-position
aa,ee, andoowith tone convergence. - Deferred/free-order
wafter a vowel andươ/ưa/ưunormalization (awright after the onset is the exception — seewafter an onset). - Convergence of one deferred
wwith admodifier. - Traditional and Modern tone placement.
- Spell check, smart/eager restore, Vietnamese-first behavior, and Flip.
- Existing raw-key, minimal-diff, and revert semantics.
Flip must restore the exact raw sequence when the user wants Latin or literal [/].
The Latin choice remains sticky across a word boundary as it does in current Telex.
Difference from current Telex
| Situation | Telex | Advanced Telex |
|---|---|---|
] and [ | Literal characters | Produce ư and ơ |
w while the syllable has no vowel | Literal, or waits for a later vowel | Produces ư |
| V1–V3 rules | Included | Included |
Current Telex must remain unchanged to avoid collisions in English and source code. Users who select Advanced Telex accept the broader transform surface and use Flip as the official escape.
Out of scope
V5 does not include deferred tones, arbitrary modifier permutations, a dictionary,
prediction, autocorrect, or changes to default Telex behavior. Mapping { → Ơ and
} → Ư (UniKey's capitals for [/]) requires a separate product decision before
entering the specification.
Architecture contract
funput-coreis the single source of truth for mappings, validation, and transforms.funput-enginecontinues to own sessions, raw keys, Flip, restore, and diffs; it must not duplicate Full Telex rules.- FFI/JNI must represent the new mode with a stable value while preserving existing Telex/VNI values.
- Each platform only exposes the choice, persists/loads it, and passes it to the engine.
- CLI and configuration import/export should use a stable identifier, proposed as
advanced-telex; old configurations retain their existing behavior.
The behavior is therefore implemented once in the Rust core, but the new mode still requires engine-boundary, FFI/JNI, and platform UI/settings wiring before users can select it.