For the same exact timestamp you posted I get for Arabic “translation not found” for every word in the video. Only some example sentences are found for some of the words. Never, or practically never (not sure), any definition is displayed, however. Color marking also doesn’t work at all (only for the first word in the sentence). Extension version 1.0.1. This has been confirmed by another user as well that I know. Same thing applies to LLN. So, basically, it’s completely broken from my POV for that language.
True, but I have been watching ton of youtube way before that extension emerged, so, nevertheless, i have been able to collect a lot of such content in many languages. If you search for it, you would find it. I have been using the extension “DualSub” for youtube to offer me this functionality thus far.
Ted talks are one example where there are multiple subtitles in may different languages.
A simple counter for each colored word would be a great start. You already have all that information. No need to implement some special frequency logic yet. If you download the JSON and search “green” or “blue” that is the only info you need at the moment. Also the percentage of white in any given text can be easily calculated and displayed to the user.
Otherwise, once you mark a few thousand words, you start to doubt that the database size is even increasing anymore, since it kinda gives you the impression that it “looks the same” each and every time. I would even go as far to say that would be a pretty critical feature for long term user engagement. One of the main indicators motivating you to push forward.
There should be an “ignore list/color” for names of people and literal numbers, for example, and other such useless information. There should be a way to distinguish them separately from other white words and without contaminating your database by saving them.
You currently offer google translation of an entire sentence, but often it’s the case when you want to translate only part of the sentence to increase your comprehension of a difficult portion of it. Goolge translation changes depending on the portion you select, so this comparison ability is very helpful and something that i use constantly. I currently use the sidebar from your extension combined with the “google translate” extension in order to achieve that.
a) You should be able to do all of that only from within your extension
b) You should allow text from the subtitle on the main screen to be selectable, so you can do it there as well (currently you can only click on words there)
c) Reverso context has a pretty awesome phrases detection which is much superior to google translate in most cases. That is another 3rd party extension that I need to use in combination to yours. Either duplicating its functionality or offering better integration with it would also be great. It is one of the best dictionaries out there.
- There should be an ability/color to save complete phrases or “chunks”. It’s quite important.
Other bugs I have seen:
- Punctuation marks break color marking recognition. For example, “so…”, due to the 3 dots, it would think it’s a new word than “so” and thus you would have to recolor it. i have seen that on LLN but probably applies to LLY too. Please strip any punctuation from a word that is being saved (it saves them with the punctuation).
Another related issue, for LLN with “CC” marked subtitles, sometimes you can’t mark one of the words attached to a square bracket. For example: “[wind howling]”, either “wind” or “howling” would not be markable due to the square bracket (not always the case).
Pretty rarely, but you can find instances where you can mark the same exact word with two different colors at the same time. That might happen even in the exact same sentence. They are written exactly the same, and there is no difference between them that I can detect, but the extension thinks they’re different words for some reason. So this functionality isn’t really perfect yet. Just giving you the heads up.
Words written in short form like “we’ll” are counted as two separate words: “we” and “ll”. You can mark each part in different color. Might be intended behavior but not sure… it seems incorrect.