On 2005-01-30, Christoph Hinterm�ller <[EMAIL PROTECTED]> wrote: > First question which aspell version do you use <= 0.33 0.50.X or > even 0.60.X?
0.50.5-5 as Debian package. > Are the english citations at least in the file spelled delimited > by some recognizeable dleimiters (xml tags) like They tend to be, yes. > Why there is not only xml there are other text file formats > too. Thus i think it would be better to add a multi context filter > to aspell. This filter should be capable of not only distinguishing > visible and invisible but aso handle a visible context within an > invisble and a invisble within a visible one. Are this filters embedded in the aspell binary or external, like say a shell script? If they are embedded, it would be quite difficult to implement them as a crossplatform tool (in fact, I haven't even looked at the possibility of running aspell under win32). Most of the "foreign" text tends to be delimited in special markers, but sometimes we might need to translate it anyway or include both languages at the same time, so it cannot be said that <xxx> tags will always enclose English or Spanish text. Having the advantage of XML as source, it would be possible for us to use additional tags, either in the form <aspell-langcode> or <!-- aspell-langcode --> if the former bothers the xml book conversion tools. The advantage here would be that the translator knows what can be checked or not, and that we can use a custom filter. > [...] As a final question are you able to change aspell to 0.60.X > if you not using it allreadyl. Possibly not. Right now aspell is used once for each chapter when it is finished, so there is not such a hurry in having these functionalities. Also, I tried building aspell from CVS. The first time it didn't want to install, and now I updated again and there are some parse errors in common/speller.hpp. _______________________________________________ Aspell-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/aspell-user
