On Nov 7, 2010, at 2:59 PM, Stephan Witt wrote:
>>>>>>>>> ...Am 29.10.2010 um 22:01 schrieb Christopher Menzel:
>>>>>>>>> 
>>>>>>>>>> Greetings LyX users,
>>>>>>>>>> 
>>>>>>>>>> The aspell-based spellchecker in LyX does not appear to be happy 
>>>>>>>>>> checking a document containing a Spanish name that includes the 
>>>>>>>>>> character ú.  Specifically, the name seems throw the checker pretty 
>>>>>>>>>> seriously off balance; it begins to stop on perfectly ordinary words 
>>>>>>>>>> that occur in the document a word or two *after* a word that it 
>>>>>>>>>> apparently isn't recognizing internally -- for example, it asked if 
>>>>>>>>>> I wanted to replace the word "that" with "bisection", where "that" 
>>>>>>>>>> occurred two words after "bijection", which was clearly the word it 
>>>>>>>>>> had stopped on internally.  Is there a solution to this beyond 
>>>>>>>>>> avoiding non-English unicode characters?
>>>>>>>>>> 
>>>>>>>>> Sorry, I've no solution but a question.
>>>>>>>>> You're using LyX 1.6.7? Which platform?
>>>>>>>>> 
>>>>>>>> 1.6.7 on a Mac, latest version of Snow Leopard.
>>>>>>> 
>>>>>>> Interestingly... there are 2 options to use aspell then.
>>>>>>> What's your setup exactly? What did you do to make aspell work?
>>>>>> 
>>>>>> IIRC, I installed a package that added a System Preferences thingy.  
>>>>>> Beyond that I don't recall doing anything.  Spellchecking just worked.
>>>>> 
>>>>> I'd guess it is cocoaSpell...
>>>> 
>>>> Yes, that is correct.
>>>> 
>>>>> After upgrade to Snow Leopard I don't have it anymore.
>>>>> I'll check it on another system...
>>>>> 
>>>>> To be sure: are you able to send me a test case?
>>>> 
>>>> Sent to you directly.
>>> 
>>> I tried it and I cannot reproduce your problem.
>>> 
>>> What I did:
>>> * install cocoaSpell
>>> * start LyX 1.6.7
>>> * open preferences, goto language -> spellcheck
>>> * select aspell and apply
>>> * press F7 then Ignore until end of document
> 
> Sorry, not clear enough... here i had no error. 
> All is working with aspell (NOT library) at this point.
> Than I tried the other route to reproduce the problem.
> 
>>> * reopen preferences, goto language -> spellcheck
>>> * select aspell(library) and apply
>>> * F7 => error message: no word lists for en_US
>>> * paste into the "Alternative language" field of spellcheck preferences:
>>> /Library/Application Support/cocoAspell/aspell6-en-6.0-0/english.alias
>>> * F7 => error message: no word lists for ""
>>> * so aspell(library) seems to not work here
>>> 
>>> Please tell me, which way is yours?
>> 
>> I installed cocoAspell; and, just in case, I just now reinstalled (ver 2.1). 
>>  And, except for documents containing ú and the like, spellchecking works; I 
>> don't get the errors you are reporting.
> 
> I'd like to know which aspell configuration in LyX's preferences you're using.

Well, I've selected "aspell" as the executable and I didn't have anything set 
as the alternative language, though I've also tried setting it to 
/Library/Application Support/cocoAspell/aspell6-en-6.0-0/english.alias, which 
makes no difference.

> Maybe it's impossible to reproduce because I have a 2nd aspell installation 
> from macports...

Right.

>>> To be sure I checked in Terminal.app my LANG value => de_DE.UTF-8
>>> 
>>>> I can't get LyX 2.0alpha6 running on my iMac; crashes almost immediately.  
>>> 
>>> That's bad. Is it Intel Snow Leopard?
>>> What's the first few dozen lines of the crash report contents?
>> 
>> Actually, it now seems to be working, so I'm not sure what the earlier 
>> problem was.
> 
> Good.
> 
>> Moreover, the spellchecker in 2.0alpha6 does NOT have the problem with ú 
>> that I'm having with the spellchecker in LyX 1.6.7.
> 
> Which spell checker did you try? The Native or Aspell or both?

I've tried setting the executable to ispell and aspell.  If I set it to hspell 
I get an error that ispell cannot start.

> ...
>> I tried compiling my own svn version and the compile seemed to complete 
>> without complaining (though this required changing some "unsigned int" 
>> occurrences to "int" in Author.cpp) but the resulting binary crashes when I 
>> try to run it and I don't have the time (and, most likely, the skillz) to 
>> diagnose the problem. :-(
> 
> The compile problem did exist only hours... you have to update your svn 
> checkout.
> 
> Did you follow the recipes in INSTALL.MacOSX and now it crashes?

I updated and compiled without incident and the executable seems to be working 
well.  In particular, no problem is caused by the presence of ú and other such 
characters in the document, so the problem is becoming moot (and it's avoidable 
anyway, if not ideally, simply by inserting \'{u} as ERT in place of ú).

-chris

Reply via email to