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

[Database] Refactor the database seeder to better allow translating #616

Open
tudoramariei opened this issue Feb 7, 2024 · 0 comments
Open
Assignees
Labels
back-end content enhancement 🚀 New feature or request l10n Localization Languages php Pull requests that update Php code

Comments

@tudoramariei
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently, the seeder JSON files are one JSON file with a different language key for each property.

Describe the solution you'd like
One of the structures below seems like a good choice. The first one is similar to the one in the lang folder:

data/ong
├── ro
│   ├── pages.json
│   └── settings.json
├── en
│   ├── pages.json
│   └── settings.json
├── uk
│   ├── pages.json
│   └── settings.json
└── ru
    ├── pages.json
    └── settings.json
data/ong
├── pages
│   ├── ro.json
│   ├── en.json
│   ├── uk.json
│   └── ru.json
└── settings
    ├── ro.json
    ├── en.json
    ├── uk.json
    └── ru.json

Describe alternatives you've considered
Alternatively, if we can configure Weblate to accept this file format, I think we can skip this.

@tudoramariei tudoramariei added back-end enhancement 🚀 New feature or request php Pull requests that update Php code labels Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end content enhancement 🚀 New feature or request l10n Localization Languages php Pull requests that update Php code
Projects
None yet
Development

No branches or pull requests

2 participants