Add support for questions with a locale set to AAQ. Also, the localization for the AAQ pages isn't very good.
Maybe this should happen before bug 827651? Let's discuss in meeting.
We are displaying candidate articles twice during the AAQ process, right not they are all English, but for the localized version we need them in the native language *and* English. Like we already do on the topic landing pages: https://support.mozilla.org/de/products/firefox/get-started I created a flow chart that comments on the parts that need to be changed for the localized AAQ: https://docs.google.com/drawings/d/1Mm5-kN1jMiVsp4o1cW1AX6p3ZKsdNP4ftv_RKp_rJx0/edit
This will be opt in per locale. Initially it will only be 1-2 locales enabled. So at this point it might just be a setting.
We estimate to be a 3pter. BTW, I think we opt-out the questions app for l10n string extraction. We'll need to remove that.
My plans for this: 1 Opt the questions app back into string extraction. 2 Add a whitelist of locales for AAQ in settings. 3 Make the link in the header go to AAQ for white listed IPs. 4 Make sure the AAQ flow is properly localized. 4.1 Look out for anything that doesn't have a call to gettext (Use poxx for this). 4.2 Link to the localized versions of hot topics. 4.3 Suggest questions and documents that match the locale (with a fallback to English and questions with no locale information) 4.4 Make sure that product titles, categories, topics, etc. all get sent through the localization wringer where appropriate. 5 Add locale to the ES index for questions. I think that's everything.
(In reply to Mike Cooper [:mythmon] from comment #5) Sounds right! > 5 Add locale to the ES index for questions. You might be able to push this out until later when we need to make searching questions locale aware.
> 4.3 Suggest questions and documents that match the locale (with a fallback to English and questions with no locale information) This query is currently done with ES, so to add locale awareness to it, we need to add locales to the index. Besides the dance to make any change to the index, this shouldn't be hard.
This finally landed on master in https://github.com/mozilla/kitsune/commit/6b48e8f90e8a946d1a094cff77545913854bcc06 and https://github.com/mozilla/kitsune/commit/e43b16dedd6a537e9a8fd6aa6d6621ca6df62da8. Strings still need extracted, but it is live and ready to go for pt-BR.