Internationalization and Localization

[seiferma]

I would like to have a localized version of dada mail (especially the dada mail interface itself) but there does not seem to be a ready to use translated version. I am willing to contribute a translation for German, which is my first language. However, there seem to be no localization mechanisms in dada mail. I assume that editing the templates is the way to go, right?

This should work for now but I expect problems regarding future updates. It would be beneficial to separate the HTML markup from the strings used in the templates. This should avoid merge conflicts for future updates. Are there any plans to integrate this?

[justingit]

I would like to have a localized version of dada mail (especially the dada mail interface itself) but there does not seem to be a ready to use translated version. I am willing to contribute a translation for German, which is my first language. However, there seem to be no localization mechanisms in dada mail.

You are correct, there is no localization mechanisms in Dada Mail.

I assume that editing the templates is the way to go, right?

Correct - the ones in,

dada/templates

Email themes are already translated in German, although the past few versions have not had a release, so they are outdated:

https://github.com/holzhannes/dada_mail_email_themes-de-formal

https://github.com/holzhannes/dada_mail_foundation_email_templates-translator-tool

Maybe you can help with that?

This should work for now but I expect problems regarding future updates. It would be beneficial to separate the HTML markup from the strings used in the templates. This should avoid merge conflicts for future updates. Are there any plans to integrate this?

I have no roadmap that includes localization/internationalization. It's a very big project.

--

Justin J: Lead Dadaist. url: http://dadamailproject.com email: justin@dadamailproject.com twitter: @dadamail skype: leaddadaist

Dada Mail Announcements: http://dadamailproject.com/cgi-bin/dada/mail.cgi/list/dada_announce/

On Jun 2, 2018, at 4:52 AM, Stephan Seifermann notifications@github.com wrote:

I would like to have a localized version of dada mail (especially the dada mail interface itself) but there does not seem to be a ready to use translated version. I am willing to contribute a translation for German, which is my first language. However, there seem to be no localization mechanisms in dada mail. I assume that editing the templates is the way to go, right?

This should work for now but I expect problems regarding future updates. It would be beneficial to separate the HTML markup from the strings used in the templates. This should avoid merge conflicts for future updates. Are there any plans to integrate this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[holzhannes]

https://github.com/holzhannes/dada_mail_email_themes-de-formal was updated to Version 11.0.1 today.

[justingit]

Thanks, @holzhannes ! I'm closing this, just because this issue is not a bug, and this is not a support forum, Cheers,

[justingit]

Opening back up, and adding, "Feature Request" label

[neijek]

+1 On this, as it's something we spoke about years ago Justin, it would best be handled by moving all text to outside localization tables or files so the community could help translate much like prestshop etc handles it. as I've said years running I'll help with the IT version :)

[justingit]

I'm certainly intrigued at the idea, and I trust the community will help support with donating their time with translations. It'll also help the app find new audiences.

The stumbling block may be simply: which tool should be used to handle translating the app?

It seems an easy thing: separate databases for each language, but the app grows and changes, and those databases need to be updated. Without a simple way to do that, the translations will slowly be unusable.

Localization is also not a simple thing, and it's going to take a few tries to get that right.

I'm wondering if the solution is to just do a "ok" job now, as we'll never get a perfect job done in the future. (See the email theme template translation work as an example of an, "ok" job that's already useful to many people)

[neijek]

Hey justin, ya i get that... i know it's not something "too easy" to do.. and i'm sure there is an "easy quick and dirty way" and a proper implementation.

I personally say, lets do it once and do it right, as it's something we (I at least) been waiting for.. for years so whats a bit more time no ? but once it has localization features the use market will grow quite a lot, so it think it's well worth it :)

[holzhannes]

Justin thank you very much for sharing your Idea an tagging this as feature request :-)

Maybe we could use a online based translating service, therefore translating would be open to a big community in a easy way. I found the following:

• https://weblate.org/de/hosting/
• http://pootle.translatehouse.org/
• https://www.translate5.net/
• http://zanata.org/
• http://jabylon.org/

[justingit]

I'm not really worried about doing the translations, the real work is modifying the app to be able to be localizsed. There would be three separate workflows:

1. Text in the HTML::Template templates
2. Text in the Email Layouts
3. Text in the sourcecode

My main interest is 1., following closely with 2. Right now, there is no workflow developed for HTML::Template, so either I need to move away from it, or...? Perhaps the same can be said for the email templates.

[justingit]

xml2po may be what I need to extract the strings from the HTML::Template templates, and later merge in the changes. Hopefully, the fact that they're simple HTML snippets (and not full XML docs) won't matter, but I feet that it probably will :)

[justingit]

...unfortunately, I haven't been able to install, xml2po - I'll try a full upgrade of my system (which usually leads to some headaches...)