Daniel, for sanity in installation for end users, can we do one of the following:
a) keep the single-unified language file for the distribution, and just stick the component model files in a subdirectory under contrib, with the merge program under tools, but where those files are in MANIFEST.SKIP so they don't end up in the stuff most users download (since they don't really need them). b) instead of the single languages file, have a language_models subdirectory of the config path which includes all the different model files. Probably (a) is better C Daniel Quinlan wrote: DQ> [EMAIL PROTECTED] writes: DQ> DQ> > I found the site that textcat came from on the internet, and it DQ> > includes a set of language models, *.lm that the TextCat requires. DQ> > Does the TextCat.pm module require these .lm modules to run, and does DQ> > the distribution include them? DQ> DQ> The original language models minus a few models that shouldn't be needed DQ> plus several new models that are definitely needed are concatenated in DQ> the "languages" file that is part of the SpamAssassin CVS tree. You DQ> don't need anything from the original TextCat. (It would be documented DQ> differently if you did.) DQ> DQ> I plan on checking in the individual language models and the DQ> concatenation script at some point before 2.30. Since there were so DQ> many files, I didn't want to check them in until I was more confident DQ> that the code would be staying in the tree and that it was relatively DQ> stable. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
