Simplenews with more languages

Right now we tested only one case: use prefered user's language based on language within a user edit page. Works great out of the box in 3.0.0-beta5.

I understand simplenews works great with one language. Cool!

Some plan with multilanguage? So many use cases involved (ie: travel websites)

@afagioli, sure, we have 4 languages :)
Just noted here for users that need to cover same case as we.

Nice, handling more languages!
Sounds promising.
Will checkout
Thanks for your efforts so far

On a fresh D9:

* add a few languages (ger, fra, ita)
* install/enable simplenews 3 beta
* update subscribers list with a few more users.
** Total: 5 subscribers,
** 5 subscribed to "special offers",
** 2 subscribers saved with pref lang: german. [*]
** 1 subscribers saved with pref lang: french. [*]
** 1 subscribers saved with pref lang: eng. [*]
** 1 subscribers saved with pref lang: ita. [*]
* create a simplenews node. Title "Super-Angebot ", language: german., newsletter: special offers.
* goto newsletter node tab

I have "Send newsletter issue to 5 subscribers."
I would expect "Send newsletter issue to 2 subscribers.".

Can anyone confirm?
Thanks

[*] Double-checking, I see subscriber pref lang is *not* saved in the "/admin/people/simplenews/edit/UID" form. Different issue, I believe.

@afagioli
I would say #9 is how it is designed to work. This allows different possible uses:

If the site has a multi-lingual community, the newsletter can be advertised on the site in different languages (the newsletter is a config entity, so its fields can be translated). Each newsletter issue can be translated into multiple languages. But maybe sometimes it was not possible to arrange for one of the translations. In this case the recipients still receive the newsletter in its original language - often this is better than nothing, maybe the people can even understand this language fairly well, or at least use online automatic translation.

Alternatively, if the newsletter is intended to be only in a single language, then the webpage for sign-up can make this clear. In this case, the newsletter issues would not have translations, and everyone would receive the same language.

If you want to be very strict and only send each user their own language, then you could create one newsletter per language. The users sign-up to the newsletter in their own language, and they would only ever receive content in their own language.

I agree it would be possible add an option so that if a translation into the preferred language is not available then the subscriber is skipped. The question is: how many people want this feature? If not many, then it could go into a separate project that enhances this one.

Looks like this is a duplicate of ✨ Make it possible to send nodes of a specific language only to subscribers of a specific langage Needs work