On Fri, Sep 4, 2009 at 8:13 AM, Craig Andrews<[email protected]> wrote: > I would like to see a notice has a new field saved with in the database: > it's language. A notice's language is set by (first match wins): > 1. Language hash tag (#.en #.fr etc) > 2. API provided meta data (or web interface selection) > 3. "Language" selection from the user's profile
This logic works for me - there's no "guessing" involved which is good for first attempt at this. Liking this approach very much. > > This way, multilingual users can override the language of a particular > notice per notice. > > I'd also like to see (and this could certainly come later) a way for a > user to indicate what languages they understand, then filter all notices > in languages they don't understand from them (so when I'm logged in, > notices in Chinese don't appear in the public stream, and StatusNet never > sends me XMPP messages from my friends speaking Hindi). yup - We can get fancy and do guessing once we've seen how people are actually using the feature. perhaps we don't even need the guessing feature. _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
