Browse by Language
Document Actions
Submitted by
maxwell.
on 2006-04-13 19:37.
Mock-ups for browsing content by language
After making "Browse by Latest" mock-ups, Kyle and Ross asked me to make a mock-up for "Browse by Language". So here are some pages I've made:
- The main Content page that lists the top languages, followed by an "All Languages" link so that other language pages could be reached (it probably wouldn't, of course, be the first "browse by" category listed on the page).
- A Browse All Languages page (would lists all languages in order of how many each had).
- A Browse by Language: Italiano example page (I only did Italiano, ไทย (Thai), Português, and Français pages out of time concerns).
Re: Browse by Language
Posted by
reedstrm
at
2006-04-14 17:04
Very cool! I'm commiting the underlying support for language tagging today, so we should have it in testing next week. Addingthe browse interface is probably the next thing to do.
Re: Re: Browse by Language
Posted by
maxwell
at
2006-04-17 11:49
Do we have all the current content tagged yet? BTW, I realized that for some people, the /content/ page might look a little something more like this: http://mountainbunker.org/~maxwell/browse-languages/fonts.htm which might not be so good.
Re: Re: Re: Browse by Language
Posted by
jenn
at
2006-06-21 13:55
Yes, all current content should be tagged. If it's not, or if you find something that's clearly not tagged correctly, let us know. The initial tagging of all content happened with the rollout of content language selection in the author interface.
Re: Browse by Language
Posted by
reedstrm
at
2006-06-21 11:54
Deeper comments:
The all languages view will not have lines for languages w/ no content. Not sure about the lotso content case (english) Probably just batch, and wait for advanced search support (return results in only Swahili)
The all languages view will not have lines for languages w/ no content. Not sure about the lotso content case (english) Probably just batch, and wait for advanced search support (return results in only Swahili)
Re: Browse by Language
Posted by
jenn
at
2006-06-21 14:03
I like it. I agree with Ross's note about not including all the languages with zero counts.
My main concern is that we should have *some* other description of the language in parentheses, other than the native one. Even if we can't get a truly localized translation of the name of the language, providing it in English will help in a significant number of cases. It wouldn't be complete, but enough of the English names of languages are cognate with European ones, or familiar to ESL speakers, that it would be a significant plus.
I'm thinking particularly of the cases where the language's native script is not intelligible to the viewer, not to mention the cases where the viewer doesn't have the fonts installed at all! A Chinese person may have a decent chance of understanding the Roman-alphabet string "Thai", even if his or her browser doesn't render the native version.
My main concern is that we should have *some* other description of the language in parentheses, other than the native one. Even if we can't get a truly localized translation of the name of the language, providing it in English will help in a significant number of cases. It wouldn't be complete, but enough of the English names of languages are cognate with European ones, or familiar to ESL speakers, that it would be a significant plus.
I'm thinking particularly of the cases where the language's native script is not intelligible to the viewer, not to mention the cases where the viewer doesn't have the fonts installed at all! A Chinese person may have a decent chance of understanding the Roman-alphabet string "Thai", even if his or her browser doesn't render the native version.
Re: Browse by Language
Posted by
reedstrm
at
2006-08-18 17:21
inital implementation is now on cooker
