- 🇺🇸United States charginghawk
I made an update to potx to support TMGMT here:
https://www.drupal.org/project/potx/issues/361615 ✨ Provide option to record untranslated strings in database Needs review
We have locale support now. But still one of the most troublesome issues with it is to identify what we needs translation and what not.
The current overview provides no good selector in the mass.
For every string, Drupal shows the URL where it first appeared. However, this doesn't help us and almost never really helps.
With Drupal + Contrib + custom code, you end up with lots of untranslated contrib stuff you might not care about.
It's your custom modules' t() you want to put into a job.
How will we find it?
With potx, we can run the .po extractor on code and we will know what file contains what.
Let's create a mapping table that shows
- Module
- Full path + filename
- locale string reference id
The modules we will expose as dropdown to filter.
The parsing will need a batch, or at least need a button to start as it's a very heavy process.
Then it will be easy to select what matters.
For reference, l.d.o server does the same with contrib projects. Time to do s locally.
Active
1.0
Translator: Local
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I made an update to potx to support TMGMT here:
https://www.drupal.org/project/potx/issues/361615 ✨ Provide option to record untranslated strings in database Needs review