You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
en@boldquot would put terminal escape sequences into messages
en@quot would only change the quotes in 15 of about 1,200 strings, and only for users who explicitly set LANGUAGE=en@quot; gettext never selects it for en_US.UTF-8
In exchange, we would have to deal with:
Untracked po/en@quot.po that builds generate in the source tree
Adjusting the Transifex sync so it doesn't drop the language from LINGUAS
Broken make distcheck with the old gettext infrastructure
Activity
mc-butler commentedon May 2, 2016
en@qout*catalogs to Fix LINGUAS to containen@quot*catalogsmc-butler commentedon Sep 22, 2016
mc-butler commentedon Nov 18, 2017
mc-butler commentedon May 27, 2018
mc-butler commentedon Dec 29, 2018
mc-butler commentedon Jun 16, 2019
mc-butler commentedon Jul 5, 2020
mc-butler commentedon Jan 10, 2021
mc-butler commentedon Apr 8, 2021
zyv commentedon Oct 22, 2026
Closing as won't fix:
en@boldquotwould put terminal escape sequences into messagesen@quotwould only change the quotes in 15 of about 1,200 strings, and only for users who explicitly setLANGUAGE=en@quot; gettext never selects it foren_US.UTF-8In exchange, we would have to deal with:
po/en@quot.pothat builds generate in the source treeLINGUASmake distcheckwith the old gettext infrastructureThe cost isn't worth it.