> > Wiktionary […] isn't too hard to edit once you've made one or two changes. >
I know <https://guc.toolforge.org/?by=date&user=Alhadis>, don't worry. ;-) Wiktionary often gives translations, is multi-lingual, though they quite > rightly put English first :-), and isn't too hard to edit once you've made > one or two changes. A DICT server for its content keeps being discussed, > but there isn't one last time I checked. > I'd attribute my preference for Oxford to my innate hatred of Yanklish (U.S English), but in truth, it's really because OED is bundled with macOS's Dictionary.app (more proprietary crap, yay!), albeit in one of those undocumented binary formats <https://apple.stackexchange.com/questions/404461/where-are-dictionaries-stored-in-macos/404468#404468> Apple love using in lieu of open-standards. Probably won't stop me from writing a parser for it some day, though (then I can worry about using it on OpenBSD, heh. On Sat, 10 Dec 2022 at 21:00, Ralph Corderoy <ra...@inputplus.co.uk> wrote: > Hi John, > > > > Your emails are the reason I know and often use dict(1). > > > > Branden's e-mails are the reason I consult the Oxford English > > dictionary > > Given the open-source bias of this list's readers, I recommend > Wiktionary. I've used dict(1) for a very long time and OED if I'm > giving a reference for a bug report to fix a British version of English > dictionary, but I typically enter ‘wikt unix’ into the browser and the > ‘wikt’ keyword I've created for the site's top-right search box takes me > to https://en.wiktionary.org/wiki/unix > > Wiktionary often gives translations, is multi-lingual, though they quite > rightly put English first :-), and isn't too hard to edit once you've > made one or two changes. A DICT server for its content keeps being > discussed, but there isn't one last time I checked. > > -- > Cheers, Ralph. > >
