Problem: There are a huge number of translations to do, and current huge unprioritized list is not optimal.
We usually want to prioritize what is visible to end users and leave the admin panel in English. But there is a blurry line between back-end vs front-end.
i18n.tiki.org helps with translations in context. But in some cases, it's more interesting to go with a list of strings...
php console.php translation:getstrings iterates via all the templates.
But how can we prioritize?
Ideas
1.1.1. 3 permission levels
- End user (Can read and add content, but not manage)
- Content editors (Can manage some content sections)
- Admin
How about using our permission system?
If a translation is only visible to tiki_p_admin, it is for Admin.
If translation is visible to someone with tiki_p_admin* like tiki_p_admin_wiki_blog, etc., we may want to translate.
All the other strings are potentially visible to site visitors and should be prioritized.
1.1.2. Preference filters
We have preferences filters like basic, advanced, experimental (and we will likely add more)
Basic features should be prioritized, and experimental features should not.
1.1.3. Current preferences for a specific Tiki instances
Maybe php console.php translation:getstrings could be ran locally and exclude strings for deactivated features?
In general
- Whatever we decide, our translation stats should express a % of completeness per type.