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

Use user default language by reply instead of forum default language #120

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GermanBluefox
Copy link

We have users with 4 different languages: de, en, nl and ru.
Mostly the users with one language communicates to 98% only with the users of the same language.
Default forum language is english because the first emails should be in English too.

But russian, nl and german users have now "said in" in the responses.
My PR will fix this problem and to 98% the answers will be valid.
May be it would be interesting to use the language of the quoted user, but this could be solved too if you mean so.

We have users with 4 different languages: de, en, nl and ru.
Mostly the users with one language communicates to 98% only with the users of the same language.
Default forum language is english because the first emails should be in English too.

But russian, nl and german users have now "said in" in the responses.
My PR will fix this problem and to 98% the answers will be valid.
May be it would be interesting to use the language of the quoted user, but this could be solved too if you mean so.
Copy link
Member

@julianlam julianlam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but I'd like @barisusakli to confirm as well, thanks

@julianlam
Copy link
Member

@pitaj @barisusakli Perhaps we can make this a toggleable option in composer-default

@Jey-Cee
Copy link

Jey-Cee commented Feb 15, 2019

@julianlam That would be nice

@GermanBluefox
Copy link
Author

Any news on this PR?

@pitaj
Copy link
Contributor

pitaj commented Feb 25, 2019

If we're going to fix the problem of the string not being translated correctly, it should be fixed in a way that works for everyone.

This could be done by embedding something like

[quote of=username from=title]

And parsing it into the translation token after parse.post

Alternatively, we could make it so the translator always returns safe HTML, and then we'd be able to just embed the translator token directly in the post after enabling translation of post bodies

@GermanBluefox
Copy link
Author

@pitaj nice to know. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants