Purpose
As a user or Admin (of any type) from a non-English-speaking community interested in EAASI, or as a current EAASI user of any type working with non-English collections and patrons, I need the EAASI system (both interface and back-end processes) to support other languages besides standard U.S. English, including input of non-Latin characters, swapping keyboard mappings to control emulator interaction, and possibly translations of interface elements and documentation.
Gap Analysis
Support within various EAASI back-end processes and components (database, authentication component, storage, etc) for non-Latin characters is not well tested and likely inconsistent. Teleport theoretically offers support for keyboard mapping between a large variety of host configurations and emulators, but these options are likewise not well tested, particularly with regard to interaction with non-English software running in emulation.