Skip to content

Feature Request: Improve Character Frequency Sorting and Accent Input Logic #46782

@regisgao0524-svg

Description

@regisgao0524-svg

Description of the new feature / enhancement

eature Request: Improve Character Frequency Sorting and Accent Input Logic

I would like to suggest several improvements regarding the “sort characters by frequency” feature and the accent/alternate character input experience:

  1. Adjustable Learning / Frequency Sensitivity

It would be very helpful to have a way to adjust how quickly the system learns and prioritizes frequently used characters.

For example, while learning Spanish, I frequently need to type the inverted question mark (¿), which is triggered via the “,” key. However, the top suggestion is consistently “√”, which forces me to press an additional key every time. This disrupts typing flow and often leads to mistakes.

It would greatly improve usability if:

Frequently used characters could rise to the top more aggressively, or
Users could manually adjust the learning sensitivity / frequency weighting
2. More Logical Mapping for Accented / Alternate Characters

The current mapping between keys and their associated alternate characters feels unintuitive, especially in the context of language learning.

For instance:

When I want to type “¿”, my natural instinct is to start from the regular question mark (“?”)
However, triggering the accent/alternate menu for that key shows unrelated symbols like “√” and “÷”, which breaks the mental model

Similarly:

The inverted exclamation mark (¡) and inverted question mark (¿) are both grouped under the “<” key
This grouping lacks intuitive association and makes it harder to type fluidly without thinking

It would be beneficial to:

Improve the logical grouping of alternate characters based on semantic relationships
Allow users to customize which accents/symbols are associated with each key
3. Customizable Key-to-Accent Mapping

Providing the ability to customize which alternate characters are mapped to each key would significantly enhance flexibility, especially for multilingual users.

For users who frequently switch between Chinese, English, and other languages, the current fixed mappings can feel limiting and unintuitive.

  1. Reference Guide for Key Mappings

It would also be very useful to have a built-in reference (e.g., a visual chart or help panel) that shows:

Which alternate characters are mapped to each key
How to trigger them

This would:

Help new users get started more easily
Reduce the need to trial-and-error when users forget mappings
Summary

Overall, these improvements would make the feature:

More adaptive
More intuitive
Better suited for multilingual and language-learning use cases

Thank you for your great work on PowerToys!

Scenario when this would be used?

Use Case / When would this feature be used?

This feature is particularly useful for users who frequently switch between multiple languages, especially those learning or using languages with special punctuation such as Spanish.

For example, when typing in Spanish, characters like the inverted question mark (¿) and inverted exclamation mark (¡) are used very frequently. In my case, I need to input these characters many times during writing and practice.

However, due to the current frequency sorting and unintuitive key mappings, these commonly used characters are not easily accessible and often require extra keystrokes. This interrupts typing flow and reduces efficiency, especially during fast input or language practice.

This feature would be used continuously in daily typing scenarios, including:

Language learning and practice (e.g., Spanish)
Multilingual communication
Writing documents that require frequent use of special characters

Improving this would significantly enhance typing fluency and reduce cognitive load.

Supporting information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs-TriageFor issues raised to be triaged and prioritized by internal Microsoft teams

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions