Sure, that would be good in the long term.

I would offer my help to translate into German ;)
[mailto:bsag.tt.check[at]xoxy.net]

I have problems with german umlaute. They didn't shown correct. Or is it a missconfiguration of my mysql db? i use utf-8

anonymous: characters like umlaut work fine here, so I would think it's a misconfiguration somewhere else along the line.

> characters like umlaut work fine here

same here, you should consider that each involved party has some influence on the display of characters: web server, database (engine) and browser - and finally at three stages: input, modification and output/view.

switching to utf-8 in my safari resolved the umlaute-issue for me. firefox worked out of the box !

of course this ist only a very short-term solution, but according to this "changeset":http://dev.rousette.org.uk/changeset/111 things should be resolved in a future release of tracks - meanwhile you might just want to patch the file manually.

I've summarised all the needed stuff to support utf-8 with safari & hopefully other browsers.

" -> Look into my comment here.":http://dev.rousette.org.uk/ticket/283

I think we should reconsider this ticket, rails i18n is easy now.

I can help with Romanian, Russian translations.

Related association with ticket #202 was added

I think we should consider the changes on i18n that are going into rails right now.

But if anyone is willing to start the work, now is fine too :-) I can help with the dutch translations

I can help with Brazilian Portuguese.

Child association with ticket #980 was added

Markus Kobel is working on this http://github.com/kobel/tracks

I couldn't get how I subscribe to be notified of changes in tickets. In some issue tracking s/w posting a comment is enough. Is it here? Forgive the tech question.

I'm not sure there is a way to subscribe to a particular ticket. Assembla handles email poorly.

Is this done already? I'd like to translate.

we need to get the infrastructure in before we can accept translations. The infrastructure is not done. Currently I'm not seeing anybody working on it though...

Markus Kobel told me that he was working on it, but he isn't answering me.

This is important to me, this issue. I'd like to get it done somehow. Thinking of paying someone for his time.

perhaps you could ask on the mailing list and/or in the forum. Don't know if people are watching this ticket...

I'm planing to integrate i18n into tracks. perhaps we can put money and manpower together. feel free to contact me via my profile email.

I would like to be involved in solving this task. Before start of works on this task, we should agree on the directory structure and structure of localization files and also on the division of the different views between us.

I was working on this for some time. But I have a lot to do right now. I would like to finish a basic set up of the i18n over easter. I have not extracted all the strings, yet. But you could look into my structure and then we can discuss, what we should change! http://github.com/kobel/tracks
As i have seen, it will not be a big deal to change file and directory structures.

I had to set up my new workstation... So, I did not work on this task, sorry. :-(
However, I will work on it for sure next weekend!

Now, I have running most of the forms, the header and the sidebar in German. I will go on with this task next week.

Duplicated association with ticket #1040 was added

Has there been any progress since April? A german localization would be quite attractive for my colleagues and I'd be willing to invest some time adapting the code or translating some text.

Unfortunately, there was no progress since April... Right now, I have to finalize a Master Thesis -> so, I will not be able to invest time in tracks until the end of the year. So, if you have time earlier, this would be great for tracks!
Please look into http://github.com/kobel/tracks and tell me what you think...

Sorry Markus, I had already started adding i18n support for most of the code before reading your post.
Was busy for the last few days but finally got around to finish the basic infrastructure for i18n.
See my commit at
https://github.com/milgner/tracks/commit/01cf39b557ecc20590147c888c07e88b9119c180
The translation itself will have to wait a couple of more days and it still needs a user preference and/or a cookie to store the selected language for AJAX requests.
Also I may have forgotten to add one or two human_attribute_name translations of the model attributes to the YAML file but I wanted to get a first usuable commit online so you could take a look and comment.
I'll be away next weekend but will try to get something done nonetheless, to complete this project.

I've committed Marcis work to master as it is quite complete. Tests are still failing, so please help with patches.

btw, for the locale to pass with ajax, you can use the same method as for source_view. See application.js

Markus, I hope you can fold in your work into the changes of Marcus...

I've fixed some tests, but there are still two issues

• in project model I had to prepend t with I18n.t to get it to work
• in the same project model, the validation error messages are not taken from en.yml, but are the rails defaults

So for some reason I18m does not work for project model. Not sure if this is related to the test framework. I did not check that.

run rake test:units for example to see some of the errors

I fixed the second issue, no tests are failing anymore

Sorry for not running the tests myself, but I thought that they were broken since rake test didn't work for me from the start.
Now I did a clean git clone again and found that it apparently conflicts with the 1.9.2 Ruby interpreter I was using - rvm-ed to 1.8.7, cloned the gemset and everything's working fine now.
I'll keep that in mind and promise not to break any tests in future commits :)

:-)

I have been trying to upgrade to rails 2.3.9 which has some compatibility code for both rails 3 and ruby 1.9.x.

Unfortunately cucumber/webrat/selenium won't work anymore under 2.3.9 and I haven't figured out why :-( One theory is that the current javascript is not working correctly on 2.3.9 (longshot) so I'm migrating tracks to the latest jquery... I need it too for the last big issue for 2.0: the gui for adding dependencies.

Well, enough off-topic commenting :-)

Ok, here's another patch with lots of improvements and including an actual german translation by Ulf Klose (https://github.com/ulfklose).
Now it is possible to set the desired locale for each user in the preferences.
There's still some strings in application.js that I couldn't translate since those aren't processed by Rails. Looking around, I found this project https://github.com/toretore/babilu which could probably solve this issue.

file:czXsVwizyr4kRieJe5cbLr: More I18n for the current version

I have applied the patch from Ulf Klose. What does your patch do? Does it build on his changes?

After going through the code once again I found another bunch of strings which have now been correctly externalized.
I have extended the german translation by Ulf to include the newly introduced keys.
The patch also introduces a locale preference so the user can set his desired locale in the preferences dialog.

Ok, I'll try to apply your patch. Do you have a branch I can pull from? (With github I can then apply it with a few clicks :-) )

@babilu: I like to look at that (and other ways to pass I18n-txt to js), but I want to finish my jquery migration first, since it contains a complete rewrite/refactoring of all javascript

I've migrated all js. I hope that your i18n changes are merged correctly. please report any regressions.

I've just installed the translate plugin from https://github.com/newsdesk/translate

start tracks in development or test mode and go to /translate to see all keys and edit on the spot!

Ive added some instructions on the wiki on how to translate tracks, see http://www.getontracks.org/wiki/Translating-Tracks

Perhaps you can enhance this howto. Closing the ticket