-
Notifications
You must be signed in to change notification settings - Fork 2
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 all static message strings from translations directory #10
Comments
Yes, but you need to create a private file in your templates e.g: In this file please add any translation that you want e.g the string from your dropdown fields:
Go to Enupal Translate and you'll see these translation strings as Best, |
@andrelopez Thanks for reply. Indeed, its possible to use this walkaround, but I was asking if it was possible to just implement this functionality in plugin :) |
Hi @piotrpog Could you please share a better example? I'm not sure if I follow your requirement Best, |
@andrelopez Its just about where plugin should look for translation strings. |
Hi @piotrpog When you say translation files (inside translaion folder) did you mean .php or .twig files? |
@sarianth |
+1 for adding support for translation files inside translation folder. I use freeform for most of my forms and the recommended translation method for form labels is creating a freeform.php translation file. Currently these files can't be translated using enupal translate. |
Can plugin be modified so that it uses all strings used inside 'translations' directory, even if these are not directly used in templates?
Use case: to make dropdown fields labels multilingual, i use them as kays inside static messages translations files. So, no actual translation strings are directly used in template, but like this:
{{entry.dropdown_field.label|t}}
The text was updated successfully, but these errors were encountered: