Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | new thesaurus not robust | ||
---|---|---|---|
Product: | Writer | Reporter: | jstro <jstro> |
Component: | editing | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, ooolist2007 |
Version: | OOo 1.0.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
jstro
2005-12-03 20:20:33 UTC
Reassigned to SBA. SBA: Confirmed with OOo 2.04. Reassigned to nemeth. The new thesaurus supports WordNet (http://wordnet.princeton.edu/) categories. It's possible to use the old thesaurus in OpenOffice.org, if we will convert the old one to OpenOffice.org 2.0 format. Daniel: What do you think, could we convert the old thesaurus (where is its source, for example?), or could we make a "robust" (similarly redundant) dictionary from WordNet for creative writers? Thanks. Laci Laci: I don't know about the source, it might be needed to check out the old files from cvs and access them using the API (one file is binary, one is not, i.e. using the plain text as input for the API accesses). Using WordNet for a "more robust" -- I'd call it less precise -- thesaurus might be feasible, but I'm not sure. If at all, an English native speaker would need to do that. Daniel: Thanks. Conversion is simpler. I'd like to convert it with the Hungarian thesaurus next month. Reset assigne to the default "issues@openoffice.apache.org". |