Am 20.04.2010 um 00:18 schrieb Jean-Marc Lasgouttes: > Le 19 avr. 10 à 17:34, Stephan Witt a écrit : >> I can live with it. The code would be less cluttered. >> But if I read the developer docs of mac correct there is a standard. >> It is called "The anatomy of a bundle". > > Indeed. But if we put everything in LyX' resources I think we are still in the > spirit of the standard. I do not think we are forced to put things within the > aspell framework.
Yes, we may use $sysdir instead which is inside the application bundle in "Contents/Resources" when used as installed app. If run from build directory it is the source-dir/lib what is a good thing too. > >> BTW, did you see my change for configure regarding the ASPELL_FRAMEWORK >> macro? >> I couldn't come up with a better solution... Is this one ok? >> >> I would prefer an #undef in config.h if --with-aspell-framework was not >> passed >> but couldn't achieve this. > > I did a smallish clean up, but I realize that I do not know how to test it > out. > Is the bundle supposed to be inside LyX bundle, or not always? Always inside. The goal was to make the lookup of LyX binary and the destination the packager places the data explicitly in sync. > Am I right that this part of code would not be necessary anymore if > dictionaries are > not in the framework? If yes, it would be nice to have other people who know > about > Mac frameworks weigh in in on sense or another. My view is that, since we use > this frmaework only internally, we do not care much. Yes. > If you were to distribute it for other uses, the situation would probably be > different. I don't expect that use case. > One last thing: it seems to me that CFBundleGetBundleWithIdentifier can tell > you > where the Aspell bundle is, once you have linked against it. This would mean > that > there is no need to pass the information through config.h. Ok, CFBundleGetBundleWithIdentifier seems a little bit complicated. Involving Info.plist of the app bundle, I would avoid that. After all, I would follow your proposal to go the $sysdir route. To sum up the current situation: * I'll change the code to use $sysdir/aspell/dict and .../data. * There is some weird cpu architecture problem in aspell code to solved. I've sent an email to Kevin and asked for help. [Basically the aspell library is currently working for x86_64 only. If I compile it for i386 it works only for short words (<11 chars). I've fixed some compiler warnings but it didn't help. One of them I would rate as a real bug.] * Now I've managed to build hunspell support into LyX. That makes already 2 engines. And hunspell seems more usable... * I've installed thesaurus data files and LyX accepted them (marked in option menu). But it keeps saying "no thesaurus for language available". The questions are: * What to do with aspell if I get no answer from Kevin? * Which dictionaries can we provide packaged with LyX? Technical and legal issues here? * What am I missing with my thesaurus? Any ideas? * I'd like to add the lookup scheme to the hunspell wrapper too. Someone against this? Stephan
