Interpolation Behaviour Message Format

[maennchen]

Implements #294

Merge #296 first

This is only a draft and not a final implementation.

It looks like it is expected to configure the extract via the mix.exs options and not via the backend. Why is that?

If we actually went this way, it would probably make more sense to yield the format when extracting. This way the extractor itself would not need to know about what format to use.

[josevalim]

Hi @maennchen, thanks for the PR!

I believe the changes could be simpler. Change flags: MapSet.new([extracted_translations_flag]) to be the flag we got from the interpolator and call it a day? :)

[maennchen]

@josevalim Wouldn't that mean, that no messages would be purged if extracting with another interpolator?

(Calling PO.Translations.autogenerated?)

Is it ok to use the backend config in extraction? If yes: why are there configs via the mix.exs and not only via the backend module?

[josevalim]

The configs in mix.exs are because we don't know what are the backends until that moment, iirc.

[josevalim]

@maennchen should we use another flag for auto generated? What does gettext use?

[maennchen]

@josevalim I'm not aware if gettext itself does something like that. It seems like there's no (documented) flag for that: https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#index-msgstr

[maennchen]

But I think we can just make one up as long as we prefix it. (To make sure it doesn't collide)

Something like elixir-generated.

If you would want to go down that path, I would also offer a PR and do that before this PR.

[josevalim]

Let's go with elixir-generated, yeah. 👍

[josevalim]

Can you please rebase? And then I think this should be good!

[maennchen]

@josevalim Done

[josevalim]

💚 💙 💜 💛 ❤️