71–80 of 83 posts
Earlier quoted context omitted.
Chinese please.
Hi! I've added Chinese. However i couldn't find a dictionary for it yet, and it might need a custom font for Chinese characters. DeepL works with it as well. If it has issues, I will fix it soon.
Looks great. I would love to give it a try if it had Chinese support. The japanese support looks good though, maybe another reason to try learning.
Hi! I've added Chinese as an "experimental" language. I couldn't find a dictionary for it yet, and it might need a custom font type. DeepL works as well. I will fix the font issue soon.
Nice work! It’s great that you can track your progress in this app! When I was learning German, I used the dictionary lookup on Kindle a lot and made a web app to extract that vocabulary as Anki flashcards. It’s available on https://fluentcards.com . The code is open source on GitHub.
because I didn't see any obvious link to said repo, for convenience: https://github.com/katspaugh/fluentcards and https://github.com/katspaugh/fluentcards-grammar Being the resident licensing pedant, I'll point out that neither of those repos have any licensing information aside from package.json and I doubt gravely that's strong enough for any contributor's comfort level
Earlier quoted context omitted.
You have my full support for your project, as I think natural language processing is a very exciting and underutilised technology for language learning. But if you want a low-tech solution, I've found Wiktionary to be ideal. Wiktionary has all the declensions and prefixes for German verbs; to use your example: https://en.wiktionary.org/wiki/f%C3%A4ngt_an tells you what the word is, and gives a link back to: https://e…
FWIW, English Wikitionary (appears to!) have fewer words than German Wiktionary. I've run into this trying to extract words from eBooks (then converting to the "base" form, to essentially de-duplicate). I think it's mostly compound or more niche words, but I imagine you'd still run into them at least occasionally with most written works. There's a nice project for converting and extracting the data from English Wikti…
- the English Wiktionary has fewer English words than the German Wiktionary has German words, or
- the English Wiktionary has fewer German words than the German Wiktionary does?
This is incredibly cool. I have been trying to do this exact workflow manually by reading something in Kindle and copy/pasting to DeepL and Anki and it sucks. If the author is here, I'm wondering if you would be open to PRs for other languages? I'd like to try this for French or Italian.
Hi! I've added French and Italian.
Earlier quoted context omitted.
FWIW, English Wikitionary (appears to!) have fewer words than German Wiktionary. I've run into this trying to extract words from eBooks (then converting to the "base" form, to essentially de-duplicate). I think it's mostly compound or more niche words, but I imagine you'd still run into them at least occasionally with most written works. There's a nice project for converting and extracting the data from English Wikti…
Interesting to hear that - I'm still at the level of German where I wouldn't know what I'm missing. For clarification: are you saying that: - the English Wiktionary has fewer English words than the German Wiktionary has German words, or - the English Wiktionary has fewer German words than the German Wiktionary does?
Another example is "krächzender", which might also serve to give some idea of the particular pains in processing German text. It's not in English Wiktionary, but krächzen is, and is a verb. So "krächzender" is the adjectival form of the verb, and if you know "krächzen" and the general rules around adjective formation it would probably be obvious. But would you rely on a computer to parse those rules, or would you want a table with all the declensions laid out? And if you're building a vocab list for a book, is it a separate entry in the list, or does it fall under the verb?
Obviously, German Wiktionary only has definitions & explanations in German so it's not great for beginners, but any tool that's trying to automatically do stuff with German text would likely benefit from using German Wiktionary.
I have no idea if it's true for other languages, but I wouldn't be surprised if it's also true for other major languages spoken by Wikipedia users (e.g., French, Spanish, but maybe not Chinese).
Earlier quoted context omitted.
I think the Jellyfin integration could be more than just a niche feature. I've used https://www.languagereactor.com/ , but that only supports Netflix & YouTube, which is a bit limiting. Reasons it's useful: * If you've got both Native & Target Language subtitles, you can see a natural translation if you're struggling to understand something * If there isn't a Native translation, then you can machine-translate one - e…
Hi! I thought of it as a niche feature because I thought most of the users would come from language learning communities, where most people are not into self-hosting. So even if someone would set up a server just for this, chances are they do not have or interested in Jellyfin also. But I've seen several comments about it, and it seems like a lot of people are from the self-hosting community so maybe it's more popula…
I definitely wouldn't expect it to be high on the list of priorities, but I do appreciate that it's under consideration at the very least.
Thank you very much. I think this project would be great for my son who just started elementary school to learn English. Please add English.
Super smart idea. I ostensibly do this sort of thing manually to expand my vocabulary in other languages I speak. What does adding a new language involve other than adding a dictionary? It doesn't seem like there are too many language-specific features at first blush.
1. Languages that have conjugation (I am -> you are -> she is...) need a way to recognize different forms of the same word, as dictionaries typically don't have this information. 2. In some languages, nearby words dramatically modify a word's meaning (in Spanish quito=I take away, me quito=I take off). The modifier words can appear quite far away in the sentence (especially in German I think). 3. Languages that don't put spaces between words are a nightmare. 4. Even for languages that do put spaces, the set of characters that act as a separator can differ slightly. 4. Languages like Chinese and Japanese with their enourmous 'alphabets' need UI changes to help learners with pronounciation of new characters. 5. Fonts and text entry! Does your framework support all 10-jillion Chinese characters and the 5+ different types of on-screen keyboards that people use? Did you remember that Arabic is read right-to-left?
Those are all of the main challenges I encounted implementing Spanish, French, Chinese and Japanese. I have no idea what new challenges would come up in Finish, Hindi, Swahili...