Language pack page needs ui improvements.

Bug #367844 reported by Henning Eggers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Unassigned

Bug Description

Quote from beuno:

- Please use a table like in merge proposals for the list of options under "Current language packs"
- Do we need to show the empty box for "Language being tested" when none is?
- The download links should be on the actual text, no? (ie "Full language pack")
- Also, shouldn't the date tell you how long ago? The WST (timezone?) is wierd
- There's a dot at the end?

Revision history for this message
Henning Eggers (henninge) wrote :

This for the public view of +language-packs for a DistroSeries.

tags: added: ui
Revision history for this message
Данило Шеган (danilo) wrote :

Most of the Martin's points are valid. I am not so sure about time and timezone display (WST is probably Henning's or however he's logged in into launchpad.dev local timezone), though. It might be worthwhile to switch export times to UTC, since these are globally relevant dates (i.e. it's most useful to be able to say "we did last langpack export on blah-blah UTC") and comparable to dates in Ubuntu schedule (which will always be in UTC, since Ubuntu development is global as well).

As far as actual layout, I'd do much more on it to make it nice: for instance, full language packs should be listed as top-level entries, and delta language packs made after them (and before the next full language pack, usually, though this is where it gets tricky) should be listed as second-level entries. Eg. we could have a table listing full language packs, and allowing one to optionally choose a delta pack against it as well.

I am pretty sure Martin would come up with a good way to present this data, but I believe we'd need some DB changes to be able to fully track "parenting" of delta language packs properly.

But then again, let's not forget that this page is mostly seen by a single person (or a very small number of them), and is thus not very important to be fixed ASAP. Marking as 'Low'.

Changed in rosetta:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Данило Шеган (danilo) wrote :

This page was heavily modified around 3.0 timeframe. Please open new bugs for new issues with it.

Changed in rosetta:
status: Triaged → Invalid
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.