On 2014-04-12 09:34, Marcin Miłkowski wrote: > SRX file can be easily edited and we will happily accept all patches, > also for languages without complete support in LT. Where's the problem?
Today, you can extend the Language class and have a Regex-based tokenizer with your own set of abbreviations (there's a constructor parameter for that). For SRX as it is now, you cannot programmatically add abbreviations. You cannot even add abbreviations at all without modifying the global segment.srx. That's different to all other rule files we have. People will not be interested in sending in patches that are specific to only their own needs. Maybe we should un-deprecate RegexSentenceTokenizer but not use it ourselves? Regards Daniel ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
