Opened 3 weeks ago
Last modified 7 days ago
#8416 new enhancement
Add a filter to show translation strings that have a matching glossary reference
| Reported by: | jdab | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Translate Site & Plugins | Keywords: | |
| Cc: |
Description
As someone who translates lots of strings every day, it would be really useful if there were an option in the filters to show strings that have a word/phrase with a matching glossary entry.
In my particular case, I'm converting US English into UK English. As there's so many similarities between the two locales, not every single string will require changes. I imagine this might be the same for the other English-speaking locales like Australia, New Zealand, South Africa, and Canada.
I will typically scan through all the pages of strings looking for any that are underlined to signify a matching glossary entry. I will then fix all those up.
Once those are done, I'll work through the remaining untranslated strings which usually takes much less time as most do not need any changes due to our well-established glossary.
As for non-English locales, it'll be useful for those contributors and editors to ensure that their glossaries are being followed correctly.
I see this being a checkbox, probably under the "Options" heading/column. Possibly "With glossary reference" or something along those lines.
Thanks for your time!
Jamie
Attachments (1)
Change History (3)
This ticket was mentioned in Slack in #polyglots by jdab. View the logs.
11 days ago
#2
@
7 days ago
I added a technical implementation note on the GlotPress GitHub issue:
https://github.com/GlotPress/GlotPress/issues/2107#issuecomment-5653187553
The main point is that glossary highlighting is currently calculated at render time using the existing glossary regex logic, while the translation filters are SQL-level. So a faithful filter likely needs exact PHP matching before pagination, a safe SQL prefilter plus exact PHP verification, or a larger precomputed/cache approach.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Mockup of how the filter could look