Add Telemetry for Language Identification in Translations
Categories
(Firefox :: Translations, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox146 | --- | fixed |
People
(Reporter: nordzilla, Assigned: nordzilla)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
In Bug 1859081 we are going to change the way we do language detection in an effort to reduce false positives.
Following this change, we should instrument the Full-Page Translations functionality with telemetry to measure a few aspects about our translations offering process.
We want to measure the following qualities:
- Whether visited pages have specified language tag vs. no language tag.
- Among pages that have a specified language tag which is a supported language, how often did our language detection process agree with the language tag vs disagree?
- How often is our language detection confident about is predictions vs. not confident?
We should ensure that we have this data instrumented for our current CLD2 implementation before we switch to fastText, CLD3, or potentially a different language identification mechanism, so that we can make informed inferences about any improvements or regressions.
Comment 1•2 years ago
|
||
We might not even need Telemetry, we could use CommonCrawl. There could already some analysis of this done by somebody else.
| Assignee | ||
Comment 2•7 months ago
|
||
This patch adds a new Translations telemetry event
for the language identification, such that we can
get a sense of the average performance of our language
detection code in aggregate.
Updated•7 months ago
|
Comment 5•6 months ago
|
||
Backed out for causing tr8ns failures on browser_translations_full_page_telemetry_auto_translate.js
| Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Description
•