Closed XavierNovella closed 6 years ago
Oh, I didn't realize obsolete messages were included. I am fairly sure that I can fix this by changing the query string. Thanks for reporting!
Thanks! I hope you can solve it as simply as changing the string of the query!
@XavierNovella Now fixed! (v.7.215)
And I'll consider making this an option if I get requests from someone who actually wants to use obsolete messages.
Awesome!!
El mié., 31 oct. 2018 19:46, Eirik Birkeland notifications@github.com escribió:
@XavierNovella https://github.com/XavierNovella Now fixed! (v.7.215)
And I'll consider making this an option if I get requests from someone who actually wants to use obsolete messages.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/EirikBirkeland/gttbooster/issues/85#issuecomment-434797827, or mute the thread https://github.com/notifications/unsubscribe-auth/AIHbhyNnWbH_GkXENUb84G5Uj610u-8Bks5uqe_zgaJpZM4YEWm_ .
Our team uses this extension on a daily basis. We would love to have the option of enabling and disabling obsoletes messages when searching in the Translation console via the right button click in GTT.
Could that be possible? Could it be a section in the setting to improve the handling of the search requests when using this feature? Selecting the "do not include obsolete messages" changes drastically the number of results and improves accuracy when choosing a UI ID.
Million thanks!