Preamble
This issue summarizes several issues related aside where you can find plenty of details and eventually improve there.
I wrote this issue to render the widest scenario clear at best. We should discuss here only whether an improved design for multilanguage support is needed.
Problem/Motivation
Simplenews multilanguage support at version 3.0.x has several bugs and - most importantly - an old-fashioned design. Content in different languages should be posted in the same newsletter. When a issue is sent, simplenews tries to match content language with user language to eventually send the issue.
This approach has limitations:
* a subscriber - depending on that match - may not receive issues from a newsletter she/he subscribed to, possibly missing info from that newsletter.
* a multilanguage subscriber can not choose in which languages receive issues. IE: As Italian, I may be interested in reading a French newsletter.
* bugs
Steps to reproduce
Set up a D8 multilanguage with simplenews 3.x
Proposed resolution
We need instead an improved multilanguage support where:
* less code in place with less bugs
* every newsletter has a defined language
* subscriber chooses the newsletter by the "Title" (cucina italiana, italian cooking, italienische Küche)
* issues are sent to every active subscriber, no matter what language has. And her/he will receive *every* news, in the subscribed language. Never miss a bit.
* more information exposed when you are going to send your issue
* more tools and info to improve usability
- Simplenews with improved multilanguage support available at https://github.com/augustofagioli/d8_simplenews_better_ui
Data model changes
Newsletter entity has a new "language" field