Contribute a Language Translation via GitHub

For those comfortable working with GitHub or looking to provide an entire translation of the application, you can contribute a translation directly via GitHub.

To translate ArchivesSpace using files directly from GitHub, you will need to translate the en.yml in the following five directories. These five files (public, common, enums, frontend, and frontend_help) create all the labels and other text in the interface.

common (for many labels shared across the application): archivesspace/common/locales at master · archivesspace/archivesspace

enums (for controlled value lists entries) archivesspace/common/locales/enums at master · archivesspace/archivesspace

frontend (for many labels and messages in the staff interface) archivesspace/frontend/config/locales at master · archivesspace/archivesspace

frontend help (for context-sensitive help link labels and tooltips) archivesspace/frontend/config/locales/help at master · archivesspace/archivesspace

public (for many labels and messages in the public interface) archivesspace/public/config/locales at master · archivesspace/archivesspace

To translate

1. Create a branch of your own, copying what’s in the en.yml files to a new file title. Title the file using the abbreviation of the language you are translating the English (en) files into.

   • See the ISO 639-1 column on this page from the Library of Congress for the code to use.

2. Translate as many of the entries in the files as you can.

3. Submit a pull request with the translations to Github when you’re ready to contribute the translation to the application.

Alternatively, you could download the en.yml files and translate them outside of GitHub. Once the files are translated, email the files to ArchivesSpaceHome@lyrasis.org.