-
Notifications
You must be signed in to change notification settings - Fork 280
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
Comments
Hi, did you solved this problem already? If yes, can you please write down how? |
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. |
Yes, that is what I do - each for 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? |
Honestly, I don't think this package delivers a good solution to any of the issues/problems it's supposed to address. :) |
I currently work on a solution without parler: I add a FormTranslationModel() that will contain translations for a form... The idea is:
But it's not ready to use, yet. I will create a pull request, if i have a working proof-of-concept... |
I add a proof-of-concept with pull #214 And add some screenshots, how it worked: |
I'll be trying this as well. Anymore graceful solutions you have come up with since this thread died? |
For multi language sites, any work around with translation for response, intro, label fields? Anybody has any such experiences?
The text was updated successfully, but these errors were encountered: