Changes

Jump to: navigation, search

User:Cameron/Dictionary thoughts

318 bytes added, 16:59, 2 November 2006
Thoughts -> Paper... or wiki, whatever.
Here's a collection of ideas regarding dictionaries that I pondered while I was away on holiday. Apparently "nobox and others" is assigned to work on a stop-gap solution to dictionary distribution for the Firefox 2 launch, my help isn't wanted, and we'll work on something better in Remora. I don't know if the page is going to be on mozilla.com or AMO, or what the plan is at all (so much for openness.) My previous recollections were for the first-run pages to include a link to install the dictionary for that locale, and then also include a link to a page on addons.mozilla.org similar to the current search-plugins page (actually at that stage remora was going to make the Fx2 release, so it was going to be a remora page.) So anyway, here's my ideas, whether they be used for the stop-gap pages, or for remora.
Basic page layout:
We reckon you're probably looking for the English (British) dictionary.
: * [https://releases.mozilla.org/etc/etc/ Install now - 200KB]
...or maybe you'd prefer one of these:
* [https://releases.mozilla.org/etc/etc/ English (USA) - 190KB]
Or maybe we just have no idea at all, so here's all the dictionaries we have available.for all languages:
<table border="1" cellpadding="3" cellspacing="0" style="margin-left: auto; margin-right: auto; width: 90%;"><tr><th colspan="2">Language</th><th>Version</th><th>Size</th><th>Last Updated</th></tr>
</tr>
<tr>
<td>Bulgarianetc.</td><td lang="bg">Български<�td/td><td>0.2</td><td>450KB</td><td>June 29, 2005</td>
</tr>
</table>
----
The first guessed add-on dictionary is the locale of the user's application installationif they are accessing the page from their app or if they are accessing it from a link, the first guessed dictionary is the one for the language they are browsing in.
The second-guessed locales are:
* The locales that the user has in their accept-language file, which I understand will be passed to us from the client's URL.
* Any locales which match the first part of the application's locale. eg. if the locale is en-GB, any en-* dictionaries which have en in the locale will be shown.
Some database changes:
If Perhaps a new table called official-dictionaries which has the country/region code, a reference to the add-on's ID, and also the name of the language in the language. eg:<table border="1" cellpadding="3" cellspacing="0"><tr><td>en-US</td><td>3497</td><td>English (American)</td></tr><tr><td>de-DE</td><td>3077</td><td>Deutsch</td></tr></table> Then wehave an admin tool to add, edit and remove those references. I don're going t want people to just be doing able to upload any dictionary and have it appear on that page. If you hadn't gathered already, I don't like the match-by-em:id method, especially as it's not documented anywhere. We'll need a funky way to change the existing dictionaries' add-on type - either during migration, or in the admin CP. Way to edit compatibility info Not sure about how we'd go translating the language names into all other languages - it's different from translating an add-on's description (which we've made developers' responsibilities yeah?) so perhaps when we get the site localised we can localise a bunch of language names and hope for all dictionaries at oncethe best.
126
edits

Navigation menu