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

Find and fix hardcoded translations #266

Closed
tobscure opened this Issue Aug 27, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@tobscure
Member

tobscure commented Aug 27, 2015

Although most of the client is translatable, there are still a few instances of hardcoded text which need to be fixed.

What needs to be done:

  • Make utils/punctuate and utils/abbreviateNumber translatable. See http://discuss.flarum.org/d/336-potential-l10n-stumbling-blocks/5
  • Find any other hardcoded translations by temporarily emptying en.yml and searching far and wide for text that is still in English.
  • Do the same for all default extensions.
  • Make the whole administration section translatable (it is all hardcoded at the moment).

@tobscure tobscure referenced this issue Aug 28, 2015

Closed

v0.1.0 roadmap (old) #74

19 of 53 tasks complete

@tobscure tobscure added this to the 0.1.0-beta.3 milestone Sep 4, 2015

@justjavac justjavac referenced this issue Sep 7, 2015

Open

Flarum v0.1.0 开发路线图 #3

18 of 53 tasks complete

@tobscure tobscure modified the milestones: 0.1.0-beta.4, 0.1.0-beta.3 Oct 26, 2015

@franzliedke

This comment has been minimized.

Show comment
Hide comment
@franzliedke

franzliedke Jan 7, 2016

Member

@dcsjapan Can we close this?

Member

franzliedke commented Jan 7, 2016

@dcsjapan Can we close this?

@dcsjapan

This comment has been minimized.

Show comment
Hide comment
@dcsjapan

dcsjapan Jan 7, 2016

Member

I think it's safe to close it now.

As you say, we've caught enough of them that instead of actively looking for them, we can simply wait for localizers to mention any they find. Hopefully there won't be any! 😄

Member

dcsjapan commented Jan 7, 2016

I think it's safe to close it now.

As you say, we've caught enough of them that instead of actively looking for them, we can simply wait for localizers to mention any they find. Hopefully there won't be any! 😄

@dcsjapan dcsjapan closed this Jan 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment