search

OFFLINE-GmbH / oc-gdpr-plugin

October CMS plugin to make websites GDPR and ePrivacy compliant
https://octobercms.com/plugin/offline-gdpr
MIT License
36 stars 20 forks source link

Split language files in frontend and backend #50

Closed CptMeatball closed 4 years ago

CptMeatball commented 5 years ago

At the moment the frontend also uses the language file to load language dependent strings. As this language file is rather large it's not easy to create new languages for the front-end as you preferrably want to translate the entire file. This makes people hesitant to PR new translations.

Therefore I think it would be best to split the language files into frontend and backend, to speed up possible translations for the frontend. The backend does not need to be translated for every language, but the front-end should be translated into way more languages than the we have now.

tobias-kuendig commented 5 years ago

Great idea! What's your suggested solution for this? Can we create a frontend.php under lang/xy/ to be included automatically? I have never used multiple language files before.

CptMeatball commented 5 years ago

Yes! Will PR something today ;)