-
Notifications
You must be signed in to change notification settings - Fork 265
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
Writing locales to nested folders #486
Comments
You can setup rules based on the keys in the files with "data.write" in the config:
|
@davidwessman i see that, but the folder names are not in the yml file. Do you know how can i get the folder name in the write section to write the files at ? For example:
With this configuration the extension_change locale is not written to I would like something to the effect of the following , so that folder_name being written to is dynamic based on where its being read
|
As far as I understand, In my projects we have lots of rules to map the translations into:
for example, but it is all based on the keys in the files. |
The See https://github.com/glebm/i18n-tasks#multiple-locale-files |
Hello,
I have a project where the yaml files are nested in multiple folders, somethng like
.
└── all_translations/
├── tanslations_set1/
│ └── en.yml
└── translations_set2/
└── en.yml
I can read the the files by pattern */ yml to read all the en.yml files. But when i write it it seems like i am restricted to just one path and the translations are all combined to one file .
How do i write back the missing translations to their respective folders ?
Looking for the end result like so
.
└── all_translations/
├── tanslations_set1/
│ ├── en.yml
│ ├── es.yml (generated)
│ └── fr.yml (generated)
└── translations_set2/
├── en.yml
├── es.yml (generated)
└── fr.yml (generated)
The text was updated successfully, but these errors were encountered: