Skip to content
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.

Language options - is it a nice feature to consider? #35

Open
shenghuang opened this issue Jul 26, 2012 · 1 comment
Open

Language options - is it a nice feature to consider? #35

shenghuang opened this issue Jul 26, 2012 · 1 comment

Comments

@shenghuang
Copy link

Currently the implementation has hard-coded English texts. For example, the title of project description is hard-coded as "Project description" and the no title warning message is hard-coded as "No description available." in project_description.jade.

As the Canadian federal government, we must support both official languages - English and French. Al our IATI data have texts in both languages. Some other countries have the same requirements.

Is there a possibility to enhance the software to support multiple languages? The default texts in English can be moved to a properties file, and we can contribute to the translated properties file of French. In this way, the software can detect browser locale then display in the selected language or in the default language (probably English) if there is no properties file for the chosen language.

I am aware of the fact that codelists of the IATI standard are English only for now. Again translated copies in other languages can be added and the standard itself does allow multiple languages for the codelists.

Please let me know whether this is a nice feature to consider.

@siwhitehouse
Copy link

I think this is something we should consider and CIDA's experience in doing this will be invaluable. This wasn't specified in the previous iterations of the development of AidView. I've added it in as a consideration for the next sprint.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants