Support t-strings in gettext

[barry (Barry Warsaw)]

@yhay81

It renders the source message rather than the damaged template, so the reader gets a correct English sentence instead of Hello $nam.

That’s an interesting spin. Won’t the source message still have the placeholder in it?

@yhay81

The three side by side, with what each hands to the catalog: Why t-strings - gettext-tstrings

Have you considered adding a comparison to $-strings/string.Template/flufl.i18n style?

[yhay81 (Yusuke Hayashi)]

@barry

Won’t the source message still have the placeholder in it?

It does, but it still renders: the fallback substitutes into it, giving Hello Ada. The source message is the t-string in the code, so its names and the values passed can’t disagree — only the translated copy, written elsewhere by hand, can, and that’s the copy being discarded.

@barry

a comparison to $-strings/string.Template/flufl.i18n style?

Not yet — and it belongs there, since $-syntax exists because of the failure you described. I’ll add it.

[barry (Barry Warsaw)]

One orthogonal thing that flufl.i18n handles is multiple stackable language constructs. This can be really helpful for things like a web application where you might need to translate into several different languages in the same request.