8 ms·

This comparison mentions that in gettext, using the source string as a message identifier "makes it impossible to introduce multiple messages with the same sour

This comparison mentions that in gettext, using the source string as a message identifier "makes it impossible to introduce multiple messages with the same source string which should be translated differently." It's rather disingenuous to say this without mentioning that in gettext, the actual identifier is a combination of the source string and the string context, which is blank by default. But the context can and should be provided in cases where disambiguation is required. https://www.gnu.org/software/gettext/manual/html_node/Contexts.html https://www.gnu.org/software/gettext/manual/html_node/Contex...

zbraniecki 8y ago
Thank you! That's a good feedback. In our experience of working with the gettext based localizations we noticed that developers almost always omit the context and in result localizers are stripped of the ability to distinguish the message variant which makes them have to ask the developer to introduce it. This, in turn, breaks the design principle #1 of Fluent - https://github.com/projectfluent/fluent/wiki/Design-Principles https://github.com/projectfluent/fluent/wiki/Design-Principl... I'll update the Wiki to reflect that!