User:Cameron/Dictionary thoughts: Difference between revisions

Thoughts -> Paper... or wiki, whatever.
(Half-done, restarting Fx)
 
(Thoughts -> Paper... or wiki, whatever.)
Line 1: Line 1:
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.)
Here's a collection of ideas regarding dictionaries that I pondered while I was away on holiday.
 
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:
Basic page layout:
Line 15: Line 11:
We reckon you're probably looking for the English (British) dictionary.
We reckon you're probably looking for the English (British) dictionary.


: [https://releases.mozilla.org/etc/etc/ Install now - 200KB]
* [https://releases.mozilla.org/etc/etc/ Install now - 200KB]


...or maybe you'd prefer one of these:
...or maybe you'd prefer one of these:
Line 23: Line 19:
* [https://releases.mozilla.org/etc/etc/ English (USA) - 190KB]
* [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.
Or maybe we just have no idea at all, so here's the dictionaries 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>
<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>
Line 41: Line 37:
</tr>
</tr>
<tr>
<tr>
<td>Bulgarian</td>
<td>etc.</td>
<td lang="bg">Български<�td>
<td></td>
<td>0.2</td>
<td></td>
<td>450KB</td>
<td></td>
<td>June 29, 2005</td>
<td></td>
</tr>
</tr>
</table>
</table>
Line 53: Line 49:
----
----


The first guessed add-on is the locale of the user's application installation.
The first guessed dictionary is the locale of the user's application installation if 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 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.
* 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 dictionaries which have en in the locale will be shown.
* Any locales which match the first part of the application's locale. eg. if the locale is en-GB, any en-* dictionaries will be shown.


Some database changes:  
Some database changes:  
If we're going to be doing a funky
 
Way to edit compatibility info for all dictionaries at once.
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 we have an admin tool to add, edit and remove those references. I don't want people to just be 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 way to change the existing dictionaries' add-on type - either during migration, or in the admin CP.
 
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 the best.
126

edits