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 internationalization #18

Open
cletusc opened this issue Nov 7, 2013 · 1 comment
Open

i18n: String internationalization #18

cletusc opened this issue Nov 7, 2013 · 1 comment
Labels
enhancement Something we do have implemented already but needs improvement upon to the best of knowledge.
Milestone

Comments

@cletusc
Copy link
Contributor

cletusc commented Nov 7, 2013

Down the line we should make sure the site is easily translatable with some small UI in the footer to change language. Language selection should ideally be included in a user preferences or something.

@Martii
Copy link
Member

Martii commented Jun 1, 2014

Fx is rumored to be doing this shortly. Chrome/Chromium already has this feature. See ghacks article.

Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Jan 14, 2015
* `bootstrap-custom.css` needs some more tweaking as we have some slight pixel related CSS issues overall but will save that for another PR
* Add "Categories" header to main forum page
* Change "Discuss" labels to "Discussions" to match title... we have plenty of room
* Expand out "Libs" to "Libraries" ... again we have room with *bootstrap* and portable devices. Needed for translations in OpenUserJS#18
* Change a few tooltips to match
* Adjust comment reply popup size to match changes

Applies to OpenUserJS#531
Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Feb 5, 2016
* Fix a regular expression to use environment port if available ... this is a dev bug
* Some prior typos and comments clarified
* New OpenUserJS metadata block key of `unstableMinify`... following Scriptish example of camel casing *(interCaps)*. This requires a string after it which is the reason why... invalid reasons may reduce ones karma :)
* Using boolean switch so that the view contains the strings and not the controller/libs side of our code... useful for OpenUserJS#18 and how views should eventually be rendered
* Libraries aren't covered yet because of OpenUserJS#723
* `decodeURIComponent` is required as per OpenUserJS#819 ... do a trap for now just in case it fails... which may produce a false positive but these are just notices at this time

Applies to OpenUserJS#432
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Something we do have implemented already but needs improvement upon to the best of knowledge.
Development

No branches or pull requests

2 participants