[patch] Minimal kk and tr language support

[hugo]

Sorry, but these aren't even minimal translations - there are no strings translated in it :)

Please add at least a few strings so we get something out of it, ok?

[ibr]

Hello Adrian and Hugo,

thanks for the review!

1. How can I make trac notify me on updates to a bug? I've entered my e-mail address in the hope it would, but it only exposes it to spam harvesters.

1. I'm not really interested in the translations since I use the English interface and only need the languages listed so that I can use them on my site. I'm not sure why you ask for "a few" strings, could you perhaps check this in and wait till someone needs that? In the USSR, you might have to buy tin glass covers if you wanted to buy dishes, since dishes were in demand, and tin covers were not, since glass canning tools were in deficit, and stores had a strict plan to sell everything they got from the warehouse. Is this a kind of that -- a tax :) ?

1. I managed to translate 58% of django.po. The translation is quite lousy since I don't see the context, and many messages are split. Can I at least change the var order, like "%(a)s %(b)s" -> "%(b)s %(a)s"?

With kind regards,
Baurzhan.

[hugo]

If translation strings contain named variables - as they should - you can change their order for sure. If they use positional variables (just %s instead of %(name)s), you can't change their order.

Can't say about the ticket updates, I just look into my open tickets from time to time, or keep bookmarks for other tickets that interest me.

Regarding "just check this in" - sorry, but I guess it is not of much use to check in translations without translations :). To add languages to the language list, you can just set up your own LANGUAGES list in your own settings file. That way you have them available in your system.

Questions about doing translations should be directed to the django-i18n mailing list, not the ticket system, as the ticket system is for bugs or translation updates. I close this ticket for now, but feel free to create a new ticket with translations for the languages when you have them ready. Even partial translations will help, as that often triggers ppl to join in and add or correct the translations, if they are actually there. Or ask on the django-i18n list about others who might want to join in on doing the languages you are working on.

[ibr]

Hello Hugo,

I'm not sure why you asked to open another bug; I hope you don't mind continuing here (but if you do, just let me know).

Regarding named vars -- they do, thanks!

Regarding tickets -- "My open tickets" would be perfect, where can I register? Or at least locating a bug by its number -- couldn't find this feature!

Regarding translations without translations -- I did add the languages to myapp/settings.py. However, I use the /i18n/setlang/ feature of django.middleware.locale.LocaleMiddleware, which didn't want to change the language to Kazakh or Turkish (but did change to German or Russian) till I added them to django, thus the motivation for the suggested change. Django i18n doc says that "only languages listed in the LANGUAGES setting can be selected", and "LANGUAGES setting" page (​http://www.djangoproject.com/documentation/settings/#languages) doesn't list these languages. If there is a way to do that without modifying Django, I would be glad to know it.

Regarding questions about translations -- sure, sorry for abusing the dialog with a developer :) .

Here is a raw and incomplete Turkish translation.

With kind regards,
Baurzhan.

[hugo]

(In [3822]) fixed #2623: added new turkish translation