Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better support for conjugations #5

Closed
otacke opened this issue Sep 14, 2017 · 3 comments
Closed

Better support for conjugations #5

otacke opened this issue Sep 14, 2017 · 3 comments

Comments

@otacke
Copy link
Owner

otacke commented Sep 14, 2017

In addition to fuzzy comparison, allow wildcards (at the beginning or the end of a keyword) that may be very useful for language learning.

Smartest way? Use the * in the text field? If we do that, we might as well think about replacing the GUI keyword alternative addition with a |

@sr258
Copy link
Contributor

sr258 commented Sep 14, 2017

I guess using wildcards is a possible way, but it is somewhat too simplistic. If you think of how far conjugations can differ from the infinitive in many languages, e.g. in German schaffen can become geschafft, schaffte, schuf, the only viable way is to have modules that generate possible word forms of an infinitive for a specific language.

Ideally these modules would be reusable across various h5p content types (I could use them for my project on an advanved fill the blanks content type as well) and have a common contract, allowing language-agonistic content types. The content author could simply choose from a list of supported languages.

@otacke
Copy link
Owner Author

otacke commented Sep 14, 2017

Wow, thanks for the quick feedback! Didn't know you were folliwing the issues.

The wildcard solution was a request that was mentioned at the H5P conference (I think from someone from Finland where it might be different). Please keep in mind that I'm not trying to "build Rome in one day". You are absolutely right, and your idea would definitely work better, but nothing that I can accomplish right now with the spare time I can invest. I am rather trying to put "everything" in the first release that's necessary to let it work fairly well in practice (hopefully).

@otacke
Copy link
Owner Author

otacke commented Sep 15, 2017

DONE

@otacke otacke closed this as completed Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants