I’ve always supported a sigil_M in ex_cldr_messages for the same reason.
Your implementation is much, much better and cleaner.
With today’s introduction of support for Unicode’s Message Format 2 in ex_cldr_messages I can’t wait to make sure both libraries play well together (I don’t think there should be any issues).
Thanks @kip! We are big fans of ex_cldr and we add it to every project. 
That’s why the included translation skill uses (or proposes adding) it when it sees dates, times, numbers, … in the user-facing part of the application.
… or maybe use || as separator?
~t"One Post||#{count} posts"N
It would
or operator in Elixir
It seems to me that these challenges are more to do with the default message format used by gettext than gettext itself.
Selfishly I’d like to leverage your sigil architecture with Message Format 2 messages supported in ex_cldr_messages.
Therefore I’m hoping there is a way for any syntax design changes you make in the sigil string to be tied only to your own interpolation module?
It feels like pluralization should remain a proper call, because encapsulating all of that in a sigil will likely be less clear than a function call.
The reason I liked the original sigil is because it balanced between conciseness and clarity, but the plural one seems to only be shorter.
Not sure I understand completely because I haven’t used ex_cldr_messages, but I’m definitely interested in making it work with ex_cldr!
Am I correct that you would like to be able to do something like this:
~t"The current time is #{time}!"
And because Gettext is configured to use the Cldr.Gettext.Interpolation (or V2?) backend, it would automatically localize the interpolated time?
If yes, that would be awesome! 
Currently the sigil string is parsed and represented internally as a list like this:
segments = [
"The current time is ",
{:time, time}, # time = AST
"!"
]
and then transformed into this to be passed to Gettext:
{msgid, bindings} =
{"The current time is %{time}!", time: time}
For pluralization in the future, the msgid is then optionally split into two parts (probably by ||) and the count extracted from the bindings:
{msgid, msgid_plural, count, bindings}
= pluralize({msgid, bindings})
For it to work with the ex_cldr_messages backend, it should be transformed into this insted, right?
# V1
{"The current time is {time}", time: time}
# V2 / MF2
{"{{The current time is {$time}!}}", time: time}
If yes, I could make the transformer a behaviour that could be switched out that implements
def transform(segments)
# -> {msgid, bindings}
It could maybe even detect the Gettext interpolation backend, and choose the right transformer automatically (gettext_sigils could probably include adapters for the default interpolation and ex_cldr)
Would this be enough to support V2/MF2 as well? Because the syntax looks a bit more complicated.
Yes, I agree it’s not very elegant unfortunately. But making it explicit with the N modifier would at least let the users opt-in to use it (or use gettext directly)
I’m hoping that the sigil doesn’t do any transformation of the message text - and that it only translates to the correct gettext call with the bindings. The gettext backend configuration includes an :interpolator key so that’s MF2 messages already taken care of.
If you’re planning to adjust the syntax of the messages to have additional capability, then I’m suggesting that would be better done in an interpolation module - not the sigil itself. That way if a user wants to opt in to your enhanced syntax, they configure your interpolator in their gettext backend. Your interpolator can delegate to the standard interpolator for most things except parsing.
This has the added benefit of keeping the sigil code clean, simple and focused (which is what José liked) but still gives you all the flexibility to build any syntax extensions you want.
Thanks for the explanation! While I’m not planning to add anything that goes beyond what gettext offers (domain/context, interpolation, pluralization), I have to transform the msgid, because the sigil receives the AST of the Elixir string interpolation, which is then translated to the Gettext (default) interpolation syntax ("%{foo}") and bindings. These are then always passed as is to gettext along with the bindings (which then uses the default interpolator to do the interpolation).
To support MF2, I’d have to generate a string with MF2 interpolation syntax ("{{{$foo}}}" I think?) and pass this to gettext (because that’s what the MF2 interpolator expects, right?), eg:
foo="bar"
~t"{{#{foo}}}" # -> gettext("{{{$foo}}}", foo: foo)
This would probably work for simple MF2 message strings, but get complicated quickly if you use .input, .match etc, no?
I’m sorry if I did not understand what you meant. Could you maybe make an example how the ~t call would look like?
All good, you’ve been very patient letting me distract this thread a bit. I’ll do some homework and testing and open an issue or discussion on the repo after that.
Thanks for doing this, I think it really helps make localised applications as easy a non-localised ones.