Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translatable Emails #3622

Closed
kolaente opened this issue Mar 3, 2018 · 10 comments
Closed

Translatable Emails #3622

kolaente opened this issue Mar 3, 2018 · 10 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented modifies/translation

Comments

@kolaente
Copy link
Member

kolaente commented Mar 3, 2018

It would be nice if Gitea could have translatable emails.

What do you think would be the best approach to this? Simply putting all emails as strings in the translation files?

@lunny
Copy link
Member

lunny commented Mar 4, 2018

Put the english email as a new file on crowdin and write some scripts or drone plugin to keep sync.

@kolaente
Copy link
Member Author

kolaente commented Mar 4, 2018

You mean a sepereate file for every email?

@lunny
Copy link
Member

lunny commented Mar 4, 2018

No. A single file for every language.

@kolaente
Copy link
Member Author

kolaente commented May 1, 2018

Do you think we'll need a new file or would it be ok to put this in the existing locale file(s)? (under a new section ofc)

@lafriks
Copy link
Member

lafriks commented May 1, 2018

Could we instead use https://github.com/matcornic/hermes for email templates?

@kolaente
Copy link
Member Author

kolaente commented May 1, 2018

@lafriks looks great, I like it! But we still need a way to store the translated strings somewhere.

@lafriks
Copy link
Member

lafriks commented May 1, 2018

If you use this lib we could use same locale file as now for ui

@kolaente kolaente mentioned this issue May 3, 2018
@kolaente
Copy link
Member Author

kolaente commented May 3, 2018

I've created another issue for HTML emails as thats probably something we should integrate seperately and put in the translations after the fact: #3892

@stale
Copy link

stale bot commented Jan 27, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 27, 2019
@lafriks lafriks added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jan 27, 2019
@6543
Copy link
Member

6543 commented Jun 23, 2021

closed by #16200

@6543 6543 closed this as completed Jun 23, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented modifies/translation
Projects
None yet
Development

No branches or pull requests

4 participants