Both 'no' and 'nb' are stored in translation_target_language in the cx shared database.
It confuses the statistics. It must be normalized to a single code.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T102107 Enable Content Translation in Catalan Wikipedia for all logged-in users | |||
| Open | None | T116533 ContentTranslation issues that affect people who aren't editors or translators (tracking) | |||
| Open | None | T126916 ContentTranslation gray interlanguage links issues (tracking) | |||
| Open | None | T105577 use geolocation to show the gray interlanguage link in ContentTranslation | |||
| Open | None | T105578 Incorrect language code handling in ContentTranslation (tracking) | |||
| Open | None | T85903 Resolve the issues with Norwegian macro language code in ContentTranslation (tracking) | |||
| Open | None | T95292 Both nb and no appear as target languages on Special:CXStats | |||
| Open | None | T122497 Both 'no' and 'nb' are stored in translation_target_language in the cx shared database |
Event Timeline
Comment Actions
It's easy to do replace in SQL, but what are the dates for newest entries, i.e. do we need to fix that issue first?
Comment Actions
They keep appearing:
mysql:wikiadmin@db1029 [wikishared]> SELECT
-> translation_target_language,
-> COUNT(*)
-> FROM
-> cx_translations
-> WHERE
-> (translation_status = 'published' OR translation_target_url IS NOT NULL) AND
-> translation_last_updated_timestamp LIKE '201511%' AND
-> translation_target_language in ('no', 'nb')
-> GROUP BY
-> translation_target_language;
+-----------------------------+----------+
| translation_target_language | COUNT(*) |
+-----------------------------+----------+
| nb | 110 |
| no | 18 |
+-----------------------------+----------+
2 rows in set (0.10 sec)So yes, the underlying issue must be fixed - we must only store 'nb'.
Comment Actions
Old codes are no longer appearing in the database. Now we could see if we can map the codes and whether there are conflicts.