public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: alternate dictionary server was Re: OT: I lost my dictionary
Date: Tue, 29 Jul 2014 10:50:16 -0700	[thread overview]
Message-ID: <87tx60m4vb.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <alpine.LNX.2.03.1407291303340.1068@ftml.net> (Charles Hallenbeck's message of "Tue, 29 Jul 2014 13:08:22 -0400")

Charles Hallenbeck <chuckh@ftml.net> writes:

> It says the initrc script will scan /etc/dict for local
> dictionaries, but on my system that directory is empty.

Chuck,
You need to install dictionaries separately from the dictd daemon in
order to run a local server.  As far as I can tell, on Arch, they have
to be built from source.  There are PKGBUILDs in the AUR.
Unfortunately, the sources are on dict.org, which isn't responding at
the moment.

As for dict.org itself, I hope the downtime is just temporary.

-- Chris

  parent reply	other threads:[~ UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Charles Hallenbeck
 ` acollins
   ` Charles Hallenbeck
     ` acollins
   ` Charles Hallenbeck
     ` acollins
     ` acollins
       ` Charles Hallenbeck
         ` acollins
           ` Charles Hallenbeck
             ` Kyle
               ` Charles Hallenbeck
               ` Al Sten-Clanton
                 ` John G. Heim
                   ` Scott Henning
               ` Gregory Nowak
     ` alternate dictionary server was " Chris Brannon
       ` Charles Hallenbeck
         ` Kirk Reiser
           ` Charles Hallenbeck
             ` Charles Hallenbeck
               ` acollins
             ` Chris Brannon [this message]
 ` Janina Sajka
   ` Scott Henning
   ` Charles Hallenbeck
     ` Janina Sajka
       ` Willem van der Walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tx60m4vb.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).