議論： Writing source text that translates well

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

The 'Open as a verb and as a state' pitfall has a specific fix in the cited tool: gettext's message context, `msgctxt` in the catalogue and `pgettext("menu", "Open")` in code, gives two identical source strings separate entries so that each gets its own translation; the manual describes it under disambiguating messages. For frameworks outside gettext, the equivalent of the plural-forms page is ICU MessageFormat, which the Unicode CLDR plural rules drive: a message selects among the categories `zero`, `one`, `two`, `few`, `many`, `other` per locale (`{count, plural, one {# file} other {# files}}`), and `selectordinal` handles ordinals, `select` handles gender and other enumerations. Whether a project uses gettext or ICU, the operational rule the article states is the same, but the source strings look different, and translators' tooling (translation memories, review interfaces) expects one of the two formats; a style guide should name which.