Localize l.d.o

yes, translators should have the option to see l.d.o in their own (or any other) language.

+1 add multi lang support

+1

It's a little bit grotesque to me: A page that shall encourage people to help translation into their own language, but is not able to use that features.

Adding my vote here ...

Reasons:

1) l.d.o should be the first to use what it is providing to illustrate and show it.
2) Not all users speak English, but want to use l.d.o to get translations for their sites.
3) RTL languages have display problems in the l.d.o site when it is in English instead of the rtl language ( rtl css files available here )
4) Adding a language to l.d.o is easy and straightforward

There should be a minimum translation requirement for each language to be added to l.d.o especially for modules it is using (l10n_server of course)

Regards

Well, what we need basically, is a fast-feedback loop for translations to show up in the locales table when submitted for the l10n_server tables. The .po file building is not yet stable enough to serve as a base, but that's another option to work with that and l10n_update module.

Generally, the reason this is not solved yet is that we are moving off of CVS as a translation submission UI but we do not yet have complete .po file generation ready to roll to feed an l10n_update module setup on l.d.o. You can already pick a language on l.d.o (your user account page), but it is only used for emails currently.

I'm guessing http://drupal.org/project/l10n_update is the plan for getting this in place at ldo, is that right?
What needs to be done before it can be used at ldo?

l10_update provides a way to get the data. l10n_client has a nice UI way to translate the strings and you can do them in local site.
The site need not fully in local language I think. It can only give us a block in main section( like sidebar top) to show message to user

i think we have all working what is needed

+1

Moving this issue to the new l.d.o project.

It's a quite old issue, which meanwhile has been solved. As far as I quickly tested now in January 2014, the Translating interface (the 3rd green tab under the content title) of l.d.o now uses the strings of Localization Server module. If teams wants l.d.o (once again: not the entire sub-site, but the translating workbench with the filter at least) speaking in their own language, the first thing they should do is fully translate to 100% all strings of Localization Server module.

There have been a lot of development on this project, but no new releases for a very long time. What is more important is that there is no update of translated or updated strings. As said before http://drupal.org/project/l10n_update could be used to update new or updated strings.
I wish there would be a new release of this project every time there is a change on l.d.o

I searched for this topic yesterday but couldn't remember the topic.

I have fully tested l10n server with English/German and this works great. We are fine here and strings are mostly complete.

Enable language switcher and lang_dropdown with language icons, please. Import all strings of all languages.

What is holding this back 6 years? Enabling lang_dropdown with language icons, positioning the block plus running localizarion update 30 minutes.