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

Internationalization support #196

Closed
jmaupetit opened this issue May 29, 2012 · 3 comments
Closed

Internationalization support #196

jmaupetit opened this issue May 29, 2012 · 3 comments

Comments

@jmaupetit
Copy link
Contributor

I wonder if django-oscar would support i18n support in templates and code ... Yes, some people do not speak english :) #frenchtouchinside

@codeinthehole
Copy link
Contributor

Yep - I've been lazy to date as most Tangent projects have been English language only. One project was in Danish and English but we used a custom set of templates there where we made the effort to make sure all text was in i18n blocks.

It's on the roadmap for oscar - it's just a bit of a long and boring task that I haven't got around to. There are some tricky problems to solve too such as where search descriptions are built up in pieces and concatenated at the end. It probably won't work to have each piece as a separate translatable string.

The first step is to go through all templates and wrap all text in the appropriate i18n tabs. Pull requests welcome!

@jmaupetit
Copy link
Contributor Author

I have done this for my own purpose with (oscar derived) custom templates. I can do this for oscar default templates. I could also be helpful to consider this in code also ...

@codeinthehole
Copy link
Contributor

i18n is now supported - we have french and german translations committed to core.

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

2 participants