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 following five en.yml files. These five files (public, common, enums, frontend, and frontend_help) create all the labels and other text in the interface.
https://github.com/archivesspace/archivesspace/tree/master/common/locales
https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums
https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales
https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help
https://github.com/archivesspace/archivesspace/tree/master/public/config/locales
To translate
Create a branch of your own, copying what’s in the en.yml files to a new file title. Title the file using an abbreviation of the language you are translating the English (en) files into.
Translate the files.
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.
When translating en.yml files, you’ll want to change only what appears after the colon in each line in the file. Always keep what’s before the colon and the spacing as it is in the file.
For example, when translating the Title field into Portuguese from English you would change the line of the file from
Title: Title
to
Title: Título
Only the value for the field itself is translated, not the information before the colon.