Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I18n string resource system #2

Closed
inghamn opened this issue Sep 12, 2012 · 1 comment
Closed

I18n string resource system #2

inghamn opened this issue Sep 12, 2012 · 1 comment
Assignees

Comments

@inghamn
Copy link
Member

inghamn commented Sep 12, 2012

We're currently running through all the code trying to find and replace the word Ticket with Case. However, different cities might want to call them different things.

We could set this word in the configuration. Then, make sure everywhere on the site, the configured word is used.

I'm not sure if this would best be in the current configuration.inc, or if we should create some new configuration file with system labels. Looking down the road at i18n might give us some ideas.

@inghamn
Copy link
Member Author

inghamn commented Sep 20, 2013

The unix standard is to use gettext. PHP has support for gettext, provided you've compiled it in. From a performance standpoint, this would be the fastest system to use. However, the translation files require a special editor to be able to change the wording. A free editor (POEdit) is available on Windows, Mac, and Linux, of course.

So, cities who might want to change the wording for themselves might face a small learning curve.

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

No branches or pull requests

1 participant