635830 - Re-implement locale filter

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Kohei Yoshino [:kohei]]

From nnguyen's to do list:
https://docs.google.com/Doc?docid=0Ad7mAOXgEBZyZGRzNnZ3YjRfOHRyOXptNGdz

By default, users should only see content that has a translation for their own specific locale. Localizers can add or remove content to this view.

We've identified a need in several markets (particularly where English is not generally understood) for the ability to filter AMO for specific locales. For instance, in JA, there should be a checkbox (checked by default but remembered on a per browser basis) that filters all search, collection, and listing content by whether or not they contain JA specific translations.

-----

And fligtar's comment in Bug 505077:

We added support for the first item (being able to filter out add-ons not in
your locale) in bug 532016 last year, but removed it 6 months later because of
a number of issues with it. We need to figure out a better way to surface and
design the feature.

-----

The Chrome Extensions gallery has a drop down menu to filter locale:

https://chrome.google.com/extensions?hl=ja&itemlang=ja
https://chrome.google.com/extensions?hl=fr&itemlang=fr

Comment 2

[Wil Clouser [:clouserw]]

-> Jeff to evaluate how much work this will be.  It's my understanding that it should be possible with ES's facets a lot easier than what we did in the past

Comment 3

[Jeff Balogh (:jbalogh)]

1. How do we judge the translated-ness of an addon? If it has -ja strings for summary and description in our db, or if it has -ja strings in the xpi?
2. How are we exposing this in the UI?

I think it would be a day of plumbing + testing to hook this up, depending on the difficulty of determining whether an add-on is translated.

Comment 4

[Dave Garrett]

(In reply to Jeff Balogh (:jbalogh) from comment #3)
> 1. How do we judge the translated-ness of an addon? If it has -ja strings
> for summary and description in our db, or if it has -ja strings in the xpi?

The translation in the addon itself is a necessary, I would think, but you might want to also require description translation at the same time. That being said, in my experience getting full translations of long descriptions is much harder than getting the addon itself done. (even if there's more to do in the addon) I would suggest considering the minimum to be a translated addon plus a translated short description (summary), but not necessarily a long description. This would ensure consistent readability in all category, collection, and search pages, but still allow for addons that don't have portions of their individual public pages translated.

Comment 5

[Hiroyuki Ikezoe (:hiro)]

Attachment: extract localized descriptions in xpi file

I do not understand how to fix this issue completely, but am convinced that this patch makes some improvements about this issue.

Comment 6

[Hiroyuki Ikezoe (:hiro)]

Attachment: Correct patch

Ooops! That patch was wrong one.

Comment 7

[Wil Clouser [:clouserw]]

Thanks for filing this.  Due to resource constraints we are closing bugs which we won't realistically be able to fix.  If you have a patch that applies to this bug please reopen.

For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/