> It might be useful, for accessibility[1] reasons, and for allowing > third party tools to offer translations, it might be good if there > were a way to indicate the language of a notice.
I love this idea! > I'm not going to suggest a UI for this, as it would likely only be > annoying for end users. However, here are some ideas: > > * It could be added to the API to allow other tools that do have > language information to pass it on. Definitely. > * A convention could be established using hashtags to indicate > languages. I've done a little experimentation and think that #.en, > #.fr, #.pl, etc might be a good pattern to use. Of course, right now, > the dots are canonicalised out. I think hashtags should be optionally used, if some other method (such as API provided meta data, web interface selection, etc) doesn't provide the information. 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 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). > ____ > 1. http://www.w3.org/TR/WCAG10-TECHS/#tech-identify-changes > > -- > Toby A Inkster > <mailto:[email protected]> > <http://tobyinkster.co.uk> > > > > _______________________________________________ > Laconica-dev mailing list > [email protected] > http://mail.laconi.ca/mailman/listinfo/laconica-dev > _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
