OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-theming medium occasional DISPUTE

Fix Tamil text rendering as boxes in Chromium and Electron apps

omarchyfontconfigchromiumelectronfonts
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Rendered a test page with headless Chromium 152.0.7977.82 (throwaway --user-data-dir in the scratchpad, nothing installed or changed) on stock 4.0.4-1 with noto-fonts 1:2026.09.01-1 and fontconfig 2.18.3-2. Tamil in sans-serif, Arial and system-ui rendered as tofu. Devanagari, Thai, Bengali and Arabic all rendered correctly. So the symptom, title and fix overstate it: Tamil is confirmed, the other named scripts are not. Re-rendered with the append rule through FONTCONFIG_FILE and again through XDG_CONFIG_HOME/fontconfig/conf.d: Tamil rendered in both, so the fix works and the per-user route through 50-user.conf works too (the reporter's claim that user config is not read is wrong, 50-user.conf includes it). fc-match ':charset=0b95' and 'sans-serif:charset=0b95' both return Noto Sans Tamil on stock, and the record's verify fc-match -s sans-serif | grep Tamil already passes without the fix (Tamil at position 74), so it proves nothing. With the fix Tamil moves into the top three. The cause in the record is the reporter's hypothesis and does not explain why Devanagari survives the same assign, so it is restated as unconfirmed. Also note for the operator: a stray 99-naskh.conf left by an earlier auditor in scratchpad/xdg/fontconfig/conf.d was removed so it would not confound this test.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

In Chrome, Brave, Chromium or an Electron app (Slack, Discord, Obsidian), Tamil text shows as empty boxes (tofu). noto-fonts is installed, and fc-match ":lang=ta" finds Noto Sans Tamil. Arabic, Devanagari, Thai and Bengali render fine. Another script may fail the same way. This one is confirmed.

Cause

On 4.0.4-1 with Chromium 152 and noto-fonts 2026.09.01, Tamil set in sans-serif, Arial or system-ui renders as tofu, while Devanagari, Thai, Bengali and Arabic render. Fontconfig on its own resolves Tamil correctly: fc-match ':charset=0b95' and fc-match 'sans-serif:charset=0b95' both return Noto Sans Tamil. The failure is in Chromium's per-character fallback walk with Omarchy's /etc/fonts/conf.d/50-omarchy.conf in place. The reporter attributes it to that file assigning the generic families with mode="assign" binding="strong", which cuts off the noto-fonts alias chain. That is plausible but not confirmed, because Devanagari survives the same assign. What is confirmed is that appending Noto Sans Tamil to every pattern, the same shape as Omarchy's own last-resort Noto Naskh Arabic rule, makes Chromium find it.

Fix

Add a last-resort append for Tamil, mirroring Omarchy's Naskh rule. Check the family name first:


fc-list : family | grep -E '^Noto Sans Tamil$'

Per user, no root needed. /etc/fonts/conf.d/50-user.conf loads this directory right after Omarchy's rules:


mkdir -p ~/.config/fontconfig/conf.d
cat > ~/.config/fontconfig/conf.d/51-noto-script-fallback.conf <<'EOF'
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
  <match target="pattern">
    <edit name="family" mode="append" binding="strong">
      <string>Noto Sans Tamil</string>
    </edit>
  </match>
</fontconfig>
EOF
fc-cache -f

For every user on the machine, write the same content to /etc/fonts/conf.d/51-noto-script-fallback.conf with sudo tee instead.

If another script also shows boxes, add its Noto Sans <Script> family as a further <string> line. Do not add families for scripts that already render: on 4.0.4-1 Devanagari, Thai and Bengali needed nothing.

Fully quit the browser so every process restarts. A new window is not enough:


pkill -x chrome; pkill -x chromium; pkill -x brave

Do not put the rule in ~/.config/fontconfig/fonts.conf, which omarchy font set overwrites.

Plain Arch: Omarchy's generic-family rules are absent, and installing noto-fonts is normally enough. This was not tested on plain Arch.

Verify


fc-match -s sans-serif | head -4

Noto Sans Tamil now appears in the first few lines (on a stock 4.0.4-1 it does not). Then open a page with Tamil text, such as https://ta.wikipedia.org, after a full browser restart: it shows real glyphs.

Sources

chromium-non-latin-scripts-tofu-omarchy-fontconfig