![]() Requires: Java, Contact: Marcin Miłkowski. ![]() A more advanced version would enable loading the rules from a web-based repository of custom rules.For example, one could implement Chicago Manual of Style checker that is run only for scientific papers: the user would activate the standard English rules along with the custom sets. Enable using multiple rule sets (different XML files) to implement custom sets that implement different style guides.Write a test that makes sure our Morfologik-based speller works as good as Hunspell (both for error detection and making correction suggestions).Compare Morfologik speller with Hunspell.Go to out bug tracker : fix a bug in the browser add-on.Go to our bug tracker, find a bug you can fix, and fix it! Look out for the "easy fix" tag which marks simple issues.These are tasks that can probably be finished in a week or less. Requires: a bit knowledge of XML (which is easy to learn), no programming knowledge For examples of real-world errors, see English Error Collection and German Error Collection. Write a new error detection rule for your native language.See the github bug tracker issues marked with "easy fix".Very simple tasks to help you get started The ideas are roughly sorted by the amount of work they require, and in those categories (short, medium, long) the tasks we consider more important come first. If you have questions, comments, or would like to suggest another task, please send a message to the forum. Here are some ideas of possible LanguageTool features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |