Rudolf de Grijs wrote: > > Thank you. That is a very clear answer. > > It does pose a challenge for us from the point of roll out (the compiled > dictionaries are packaged as part of the deployment at the moment). I do > see a solution, but then it must be possible to refer to external > sources from the /default /metafile. I found the following passage in > the documentation: > > A Composite Dictionary appears as a simple text file beginning with the > magic line "@multilink:", followed > by lines containing the URL of sub-dictionaries. *URL are generally > relative to the composite dictionary, but* > *can also be absolute. Referenced dictionaries can in turn be Composite.* > > and I'm hoping that such a URL can also point to a compiled dictionary > outside the composite dictionary, let's say on a server.
This is the case. > Is this going to work? The documentation says that it works. If it does not work, then it is a bug. This being said, I've never personally tested this feature. > What is the downside of this approach (assuming > that this is possible)? Obviously, downloading a compiled dictionary over the net. After doing that, a copy of the compiled dictionary is cached in memory. > If this does not work, what are the alternatives? Why don't you give it a try first?
