Skip to content

Latest commit

 

History

History
95 lines (71 loc) · 5.54 KB

MobileDictionaries.md

File metadata and controls

95 lines (71 loc) · 5.54 KB

Dictionary apps for mobile phones and pads

The Divvun group wants to build a platform for delivering dictionary apps for mobile systems to our users. It is intended to replace our present solution, which requires users to install a third-party dictionary app, and then upload our dictionary content.

In addition to simplifying installation, we also want to build apps that better highlight our strengths both regarding content and linguistic functionality. The apps should be built for easy maintenance, and modularly so that one can easily add new functionality in the future. Also, the code should be written for easy portability (or should be platform independent), so that it will be easy to add support for new platforms if wanted, e.g. macOS, Windows, etc.

It is a primary requirement that the dictionary apps can work without a network connection for all of its basic functionality.

Deliverables

Targeted features

  • must support iOS and Android
  • should use majority language speech recognition (Siri, Google Assistant) to look up words and expressions to translate
  • should use speech synthesis from Acapela (or later: us) to read out loud the translated input words (only SME for now, other languages when voices are available)
  • should use open-source OCR libraries and built-in camera to recognise printed text and provide translations
  • look-up words in text (using morphological analysis (+ disambiguation using libdivvun if context is available) of input string)
    • preferably using OS services if available
  • look-up single words / lemmas in the dictionary (standard search)
  • dictionary content updated via a Páhkat repository
    • default: stable channel, check every week
  • the details of the user interface should be worked out in cooperation between Divvun&Giellatekno and the winning tenderer
  • fuzzy match, possibly based on our speller technology, frequency ranked
  • Korp lookup if corpus for the language is available, and Internet connection is available
  • paradigm/word form generation (off-line, fst-based)
    • key forms
    • full paradigm
    • which one to generate should be a user preference, or possibly a two-step process: always generate the key forms, then if the user taps on an expansion triangle or somesuch the full paradigm should be displayed
  • speedy, fast lookup of dictionary entries
  • clear and easy-to-read typography
  • easy to use
  • should use the same XML format (see here and here) as the other dictionary platforms as input (but the app-internal representation of the dictionary can of course be different)
  • support for audio, video, images as part of dictionary entries
  • search history
  • when looking up compound words in text that are not found in the dictionary, the app should analyse the compound word using the fst analyser, and present the articles for the compound constituents. The same goes for derivations.
  • dictionary cross reference lookup should be supported, so that one can go from one article to another, using cross references
  • hiding / showing different parts of dictionary articles (e.g. etymology, examples, homonyms, synonyms, etc.)

Whether to build one app for each language (containing dictionaries to and from that language), or build one language with all dictionaries installed is presently left unspecified. In any case it must be possible to turn off dictionaries and language pairs the user is not interested in.

See also Mothertoungues.org, and the dictionary app released by Språkcentrum in Östersund.

Compatibility requirements

  • iOS 9+
  • Android 5+

Acceptance requirements

Standard requirements.