trivett/tangochan — pull request #38 by dan987 (2014-06-22 18:14:32+00:00)
Title: Forvo api

Take a look at the new front end, in the created list view, I added kana tweet and kanji tweet (as opposed to just kanji tweet).
also added conditional into the view, figures out if term is kana or kanji for API pronunciation, defaults to kanji first but if there is no kanji term available, it goes to kana. Does this layout make sense for the user? Would the user benefit from selecting between both pronunciations also...? Does he benefit from being able to see tweets for both?

Need to create some kind of msg if a term does not yet exist in forvo database...