-
Notifications
You must be signed in to change notification settings - Fork 151
Tolk imports translation tokens from gems, but not translations #25
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
Comments
I think it would be a nice improvment, but I have no idea on how to include only the tokens of the project , have you got any trail ? |
I poked and prodded within the internals of Rails, but I wasn't able to On Mon, Jan 21, 2013 at 9:45 AM, Thomas Darde notifications@github.comwrote:
Sami Haahtinen |
These are good start points for digging. I don't have a lot of time at the moment, but as soon as I can I'll try to find a good way, maybe we can see with the guys involved with i18n. On 21 janv. 2013, at 18:54, Sami Haahtinen notifications@github.com wrote:
|
Any progress on this? |
Sorry , I have no time these days for Tolk, but would happily merge any related Code ! |
Tolk setup imports all translation tokens which have translations. This means that all tokens that come pre-translated by other gems, like rails-i18n get imported to tolk. This leads to problems like mentioned in issue #18. While setup imports the tokens, it doesn't import the translations from those gems.
This can easily be worked around by importing the translations manually. But a real solution would be to import translations only included in the project itself. Since most of those translations will be translated within the gems itself it seems a bit pointless to import them to Tolk.
The text was updated successfully, but these errors were encountered: