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

Any tip to support multi language for 'response, intro, label' #179

Open
sunjoomoon opened this issue Apr 14, 2016 · 8 comments
Open

Any tip to support multi language for 'response, intro, label' #179

sunjoomoon opened this issue Apr 14, 2016 · 8 comments

Comments

@sunjoomoon
Copy link

For multi language sites, any work around with translation for response, intro, label fields? Anybody has any such experiences?

@Mirator
Copy link

Mirator commented Aug 7, 2016

Hi, did you solved this problem already? If yes, can you please write down how?

@barseghyanartur
Copy link
Contributor

barseghyanartur commented Oct 6, 2016

You're most likely would be using a CMS, right? In any case, create two or more forms - one for each language. That's the solution.

@sunjoomoon
Copy link
Author

Yes, that is what I do - each for language.

@jedie
Copy link
Contributor

jedie commented Jan 19, 2018

create two or more forms - one for each language

Hm. It's more a work-a-round than a good solution, isn't it?

What's about to use django-parler for the form labels and the other Text fields?

@barseghyanartur
Copy link
Contributor

@jedie:

Honestly, I don't think this package delivers a good solution to any of the issues/problems it's supposed to address. :)

@jedie
Copy link
Contributor

jedie commented Jan 22, 2018

I currently work on a solution without parler:

I add a FormTranslationModel() that will contain translations for a form...

The idea is:

  1. create a form in default language (settings.LANGUAGE_CODE)
  2. create a translation for all lables in one of the languages from (settings.LANGUAGES)
  3. render the form will used the translation, if available or fallback to default language

But it's not ready to use, yet. I will create a pull request, if i have a working proof-of-concept...

@jedie
Copy link
Contributor

jedie commented Jan 24, 2018

I add a proof-of-concept with pull #214

And add some screenshots, how it worked:

#214 (comment)

@thongly
Copy link
Contributor

thongly commented Dec 1, 2018

I'll be trying this as well. Anymore graceful solutions you have come up with since this thread died?

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

No branches or pull requests

5 participants