L10n Talk:MLP page structure: Difference between revisions

L10n Talk:MLP page structure (view source)

Revision as of 17:18, 23 February 2005

1,338 bytes added , 23 February 2005

Mark's thoughts on automatically built Downloads pages

MarkTyndall

90

edits

@@ Line 38: / Line 38: @@
 <br>&lt;MadMaks_Laptop&gt; i think we provide a list whit the localizers and witch program are localized
 <br>&lt;KaiRo&gt; so we probably could be pointing to Mozilla Europe/Japan for languages where they have translations, and have our own pages where they don't exist.
+== Mark's thoughts on automatically built Downloads pages ==
+NB: some (or more) of this may be stating the obvious...
+*We want a single source of data.
+*We want many pages, containing downloads for a specific locale (I could see either language or country being useful)
+**Do we want to restrict ourselves to stable products?
+**Do we want these pages to act as a historical repository?
+The fields should be
+  language	// ''[code]''
+  country	// ''[code]''
+  locale		// ''[proper name]''
+  program	// firefox|thunderbird|suite|sunbird
+  version	// ''[number]''
+  platform	// win|linux|mac|none
+  type		// langpack|zip|tar.gz|Installer|Mac Disc Image
+  stable		// yes|no
+  path		// should be computable from above info?
+  (any others?)
+Then a list on a per-locale page would be constructed by
+ SELECT * FROM downloads
+ WHERE language='ab' OR country='CD'
+ ORDER BY program, platform, type
+(I'm expressing myself in database terms because that seems most natural, but it doesn't have to be implemented like that -- a CSV file  would be fine, though it would mean more work on the parsing front)
+=== Questions: ===
+*Do we want to the data-source to be historical (storing all versions of all packages), or should only details of the latest version of each package be kept?
+*Can we use the mozilla.org site's build to run our scripts?