...
To translate ArchivesSpace using files directly from GitHub, you will need to translate the following five en.yml filesin 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): https://github.com/archivesspace/archivesspace/tree/master/common/locales
enums (for controlled value lists entries) https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums
frontend (for many labels and messages in the staff interface) https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales
frontend help (for context-sensitive help link labels and tooltips) https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help
public (for many labels and messages in the public interface) https://github.com/archivesspace/archivesspace/tree/master/public/config/locales
...
Create a branch of your own, copying what’s in the en.yml files to a new file title. Title the file using an 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.
Translate as many of the entries in the files as you can.
Submit a pull request with the translations to Github when you’re ready to contribute the translation to the application.
...
| Panel | ||
|---|---|---|
| ||
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. |