> [mailto:
sasxsek@yahoogroups.com] On Behalf Of Florent Garet
> <
li_sasxsek@...> wrote:
> > The only thing I'm really still contemplating is how to set
> up the online dictionary. I can either have a searchable one
> like I currenly have, or I can set up something like
> Wiktionary with entries for each Sasxsek word, followed by
> translations into multiple languages. This will use the
> wiki's search function to find the appropriate article. I
> may even have both concurrently for a while.
>
> Your current dictionary is much faster than the clumsy
> Wiktionary. In the other hand, with a wiki it's easy to
> update content, change layout, and add pictures.
The current dictionary is also stored in an M$-Access .MDB file,
being pulled from a script on IIS, on a server that I pay annual
fees to use. The new site is a Linux machine running Apache
sitting in my living room to play movies, music and streaming
video so there's no recurring financial obligations. That and
it fits in to my de-Microsoftification project. Apache is also
much faster and much more flexible. Oh, and the best part of
all, it's free. Right now I have these options.
1. Leave the current dictionary and use a redirect to
make it appear like it's part of the new site. The current
dictionary may be quick, but it still needs a lot of work to
incorporate multiple languages.
2. Rewrite the entire backend for Apache.
Time-consuming but may be worth it in the long run.
3. Just use Mediawiki and create articles for each
dictionary heading then let the search function of the wiki do
the work. This is where I'm leaning right now because it will
get things up and running much quicker. I could always work on
(2) while this is in place, and have (1) working while I do
this. The other nice feature of the wiki is being able to put
up articles for each language. Eventually I want to have this
site in as many languages as possible.