Text outside Latin-1 in aux items, messages and status is handled three ways #333
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#333
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Interop audit, 2026-10-24.
Characters outside Latin-1 are handled three different ways.
compose::aux_datawrites UTF-8 when the text doesn't fit Latin-1. The Emacs client decodes aux data aslyskom-server-coding-system(Latin-1;lyskom-aux-item-decode-data,aux-items.el), so its users see mojibake. httpkom/jskom try UTF-8 first, then Latin-1 (komserialization.py), so jskom is fine.Kom::send_message).?(Kom::set_doing).charset=utf-8, which Emacs honours (komtypes.el) and httpkom too.Reactions already store Latin-1 emoticons for this reason (#101).
Options, strict to permissive:
We will go with option 2. It is a feature that is not used often, and we have a strong case that the emacs client is the one not interpreting text correctly since it remains to be the odd one out.
Merged in #384; main run #725 green. Option 2: "Vad gör du?" now refuses characters outside Latin-1, with a message and a disabled button (it used to send '?'). Names and chat messages were already refused; aux data stays UTF-8 when needed. The policy is in DESIGN §3. presence.spec checks it on all profiles.