On Mon, Feb 12, 2018 at 06:10 pm, Mark Fletcher wrote:

I agree that localizing Groups.io into different languages would be great,
and it's on the TODO list. Unfortunately I can't dedicate the time to make
it happen right now. One of the reasons is that once a site is localized,
it's more difficult to add/change features. It slows development down a
bit, for the rest of time. Also, no paid groups have asked for it (but have
asked for other features not yet supported). Again, I think it's absolutely
worthwhile. But I can't do it right now.

Thank you for considering our request. I do appreciate it.
I'll be glad to help with the Italian translation, whenever you decide to go ahead with the project.
As for date localization, I am not sure what we're talking about, but the date format we're familiar with over here is definitively day-month-year.

All the best,
Marina

Hi Mark,
Unfortunately, I don't know your stack, but basically if you use GNU
GetText for localization, the curve won't be too large: you just wrap
every text string in _() call, then you give the localizers a POT
file, and you receive from them PO/MO files. Then, if something is
changed on your side, it just is displayed in English, no errors, no
"unknown variable" or some stuff like that.
Again, I would be glad to help if needed. I've been working in
localization for six years now, so I believe I could be of some help.


--
With best regards from Ukraine,
Andre
Skype: menelion_elensule
Twitter: @m_elensule; Facebook: menelion

Hi Mark,

Checking in to see if the chance of Groups.io in languages other than English has increased at all since this last post?

Really appreciate it,

Jess

We took some time with it and determined we would need quite a few of the pieces to be in Spanish (email footers, side bar, fields within each side bar option, Group Settings, Group Emails; the whole shebang) in order for it to be useful for our Spanish-speaking users. We will need to look for another platform for our Spanish listserv.

Hello everyone,
As a resident of a non-English speaking country in Eastern Europe, I'd like to make my contribution about language localization of GIO. In my opinion, localization should begin with subscribe/unsubscribe processes. Let me illustrate this with my own example.

I am running (well, actually, just starting!) a group for a local condominium. Laws about Internet privacy in my country are famous for the broad wording and uncertain, ambiguous definitions. In essence, any new subscriber must be explained in their native language what exactly they are doing. They are giving their personal email address to someone and this someone will start using this address to send something to subscriber. Any misunderstanding may result in subscriber's frustration, telling that he/she was fooled by a foreign language text and is now being spammed.

When  someone tries to subscribe to any GIO group from an email, completely unknown to GIO, they will receive the standard message in English, asking them to reply and confirm subscription. This mechanism and this message is hard-wired into GIO platform and can not be edited or replaced by owner/moderator.

After receiving some help from GroupManagersForum (thanks, Duane!) I implemented a bypass: made the group Restricted and created Pending Membership message in my own language. But this is a poor solution: angry subscriber may clam that they have already supplied their address in exchange of an uncertain explanation in the language, they don't really understand... You know how severe may be punishment for breaking privacy laws...

Sorry for the long story, but I wrote this to explain that localisation of subscribe process is vital due to legal requirements, not just because of comfort and convenience. Same applies to unsubscribe: former customer must be explained that they are leaving the group, now further messages will be delivered to him/her and the address will be totally removed from the group's database.

Will be grateful for any thoughts on this topic!

Regards,
Gregory

On Wed, Nov 30, 2022 at 05:52 PM, Grigorii Semenov wrote:

localisation of subscribe process is vital due to legal requirements, not just because of comfort and convenience.

When you start using Groups.io you agree to the Terms of Service. If they are not legally acceptable to you in your location, then perhaps an alternative platform that meets your requirements would be best at this time.

Same applies to unsubscribe: former customer must be explained that they are leaving the group, now further messages will be delivered to him/her and the address will be totally removed from the group's database.

If a member unsubscribes from a group, they will still have a Groups.io account, they just won't receive emails from that group any more. If you have a Premium or Enterprise group, details of past members are retained on the Past member list and you can see when and why they left, so those details are not 'totally removed' from the group. Some details will also appear in the group's Activity Log too.

Regards
Andy

 

Hi Andy,

When you start using Groups.io you agree to the Terms of Service. If they are not legally acceptable to you in your location, then perhaps an alternative platform that meets your requirements would be best at this time.

No doubt, the old principle "don't use it if you don't like it" still has a value these days. But we are here to find technical means to expand usage of GIO as much as possible. The products that we all like!

If a member unsubscribes from a group, they will still have a Groups.io account, they just won't receive emails from that group any more. If you have a Premium or Enterprise group, details of past members are retained on the Past member list and you can see when and why they left, so those details are not 'totally removed' from the group. Some details will also appear in the group's Activity Log too.

In 2016, the EU adopted the General Data Protection Regulation, which came into force in 2018. Among other things, this Act in Article 17 stipulates that "The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay ".

GIO's Terms and Conditions say the same things.

Are there any technical tools in GIO that past subscriber can easily use to do so?

Regards,

Gregory

On Thu, Dec 1, 2022 at 03:27 PM, Grigorii Semenov wrote:

No doubt, the old principle "don't use it if you don't like it" still has a value these days. But we are here to find technical means to expand usage of GIO as much as possible. The products that we all like!

I don't disagree

In 2016, the EU adopted the General Data Protection Regulation, which came into force in 2018. Among other things, this Act in Article 17 stipulates that "The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay ".

Ah yes, Article 17 (1) of GDPR (the so called 'right to be forgotten'). Being in the UK, I am fully aware of this. I hear this mentioned now and then and what most people fail to mention is the conditions under which article 17 (1) applies. And then of course, we have Article 17 (3) which lists exceptions to Article 17 (1).  The only thing you can guarantee about this is that the people that make money from it will be the lawyers, but then who do you think wrote it.

Given that we are using a system that emails messages to multiple people, some or all of whom maybe unknown and we have no control over what they do with those emails, your chances of being truly 'forgotten' are slim to none existent.

Regards
Andy