Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is probably the wrong place for a UI / usability report, but this is where the 'Having issues?' link takes me... ;)
I've finding it really confusing having both:
http://localize.drupal.org/languages/en-gb
http://localize.drupal.org/translate/languages/en-gb
they are both about the same language, but unconnected, and there is no apparent way of getting from one to the other!
Comments
Comment #1
gábor hojtsy@joachim: the http://localize.drupal.org/translate/languages/en-gb page has the group linked from the Contribute block as well as showing a block with information on the group, letting you join and jump to the group. The group page indeed has no apparent navigation to go to the translation page for the language.
What would you suggest we do?
Comment #2
joachim commentedComing to the site as a newbie, it feels like there is one set of tabs for my language in one place, and another lot of tabs in another place. Why are they not all together?
Comment #3
naught101 commented@Gábor: probably the easiest solution would be to put a link in the "[Language Name] Language Team" block, probably named something like "Translate into [Language Name]" or something. That way it'll be greyed out when you're on the translate page anyway..
Comment #4
gábor hojtsyI'm thinking long term it is probably best to move the group as a tab under the usual translate/languages/{langcode} path. Not sure though how it would affect subtabs under groups. Especially if some of those subtabs have other subtabs.
Comment #5
gábor hojtsyOh, I did not remember we had an actual issue of this, but I did remember you had reservations about this. Now fixed in #738174: Integrate og features better and going to be deployed to localize.drupal.org once localize.staging.drupal.org looks good enough. There are still some tweaks going on there. It is already deployed on localize.staging.drupal.org.