fix: use min max approach instead of specific keysym range

[WhoAteDaCake]

This fixes the issue of keys with symbols such as $ or £ not being displayed

Changes proposed in this pull request:

• Use min max approach instead of specific keysym range

@lc-soft

[commit-lint[bot]]

Bug Fixes

• use min max approach instead of specific keysym range (cda526c)

Chore

• cleanup formatting and variable layout (a197b2b)

Contributors

WhoAteDaCake

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR: - `@Commit-Lint merge patch` will merge dependabot PR on "patch" versions (X.X.Y - Y change) - `@Commit-Lint merge minor` will merge dependabot PR on "minor" versions (X.Y.Y - Y change) - `@Commit-Lint merge major` will merge dependabot PR on "major" versions (Y.Y.Y - Y change) - `@Commit-Lint merge disable` will desactivate merge dependabot PR - `@Commit-Lint review` will approve dependabot PR - `@Commit-Lint stop review` will stop approve dependabot PR

[codecov[bot]]

Codecov Report

Merging #269 (a197b2b) into v3.0-dev (d422a99) will decrease coverage by 0.01%. The diff coverage is 0.00%.

@@             Coverage Diff              @@
##           v3.0-dev     #269      +/-   ##
============================================
- Coverage     55.08%   55.07%   -0.02%     
============================================
  Files            80       80              
  Lines         14889    14890       +1     
============================================
- Hits           8201     8200       -1     
- Misses         6688     6690       +2     

Impacted Files	Coverage Δ
lib/platform/src/linux/linux_x11keyboard.c	0.00% <0.00%> (ø)
lib/platform/src/steptimer.c	66.66% <0.00%> (-1.59%)	:arrow_down:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update d422a99...a197b2b. Read the comment docs.

[WhoAteDaCake]

Is that better?