In core we have locale.module and translation.module. Contrib has i18n, i10_server and others. I think it makes sense to collate the administrative items for these modules under a single "internationalisation" menu item - this would include the languages settings in site configuration as well (adding a language to a site isn't really a 'setting' IMO).
This would have the advantage of moving interface translation out of site building (it's not really site building), and making these features easily accessible in one place.
I'm also going to open an issue for a development menu item - for simpletest (core), but also devel and schema modules to add themselves to. Again, for much the same reasons.
Comment | File | Size | Author |
---|---|---|---|
#22 | 368064-followup-1.patch | 1.49 KB | c960657 |
#17 | international_1.patch | 58.16 KB | Berdir |
#12 | international.patch | 40.2 KB | catch |
#10 | international.patch | 44.14 KB | catch |
#10 | international.png | 34.62 KB | catch |
Comments
Comment #1
yoroy CreditAttribution: yoroy commentedAgreed. These admin items can very well be grouped into their own top level admin section:
- The items in core are already a bit misplaced because it is indeed not really site building
- There's quite a family of internationalisation contrib modules available that will be much easier to find with this dedicated admin section.
Comment #2
catchHere's a patch, turns out that translation module doesn't actually define an admin menu item anywhere - just form_alters the content type admin forms. However locale module has two top level items, and the translation settings could arguably not be hidden in workflow settings so maybe move here too.
Need to verify that if two modules define the same router item it'll just overwrite/ignore the second entry rather than break - going to do that with the development item now.
Comment #3
catchscreenshot.
Also, tests not updated yet.
Comment #4
Noyz CreditAttribution: Noyz commented+1
Ultimately I think more work needs to be done. Seems like users should be able to enable multi-language support, and tweak the settings of it's output via the modules settings. I think this is getting closer: http://skitch.com/yoroy/brmpw/localization-client
None-the-less, this is better than what's there today.
Comment #5
Bevan CreditAttribution: Bevan commentedI agree this is an improvement
Comment #6
catchAll tests should pass with this one.
Comment #8
catchThe test I wrote came back to bite me. Updated that one too.
Comment #9
yoroy CreditAttribution: yoroy commentedLet's try some simpler wording. What is this setting-group's name in your favourite OS? e.g. in OS X it's called 'International'. How about:
International
Languages and translation
Comment #10
catchIn Ubuntu I have 'Language settings' and a separate section for date/time. Internationalization makes for a long path, and international sounds better to me.
New, non-empty patch and screenshot.
Comment #12
catchRe-rolled for the new locale test, minor whitespace fixes crept into the patch, sorry.
Comment #14
PasqualleI would not create a top level menu item for 2 links..
The i18n and l10n_client modules do not add any new links to that group. The l10n_server module is used on 50 sites and all will be replaced by one translation server on d.o, so that is a bad example..
I would consider the possibility moving the "interface translations" inside "languages" because I many times searched for that inside the Language settings.
Or redesign the whole menu structure for language related menu links, because I am not convinced with the reasoning, this change isn't an improvement yet..
Comment #15
yoroy CreditAttribution: yoroy commentedYes, all language locale and translation related menu items should move into this section. Contrib modules should update to move their links into this section as well.
Comment #16
Bojhan CreditAttribution: Bojhan commentedSounds like a solid improvement, failed to apply patch - can someone review why?
Comment #17
BerdirRe-rolled.
No idea why the patch failed, it were just text (url) replacements, some worked, some not.
Comment #18
Bojhan CreditAttribution: Bojhan commentedMarking this rtbc, I don't see any objections to this patch other then "other things should be under this as well".
Comment #19
webchickAwesome! Committed to HEAD.
This should be reflected in the ugprade docs for other modules that might want to add settings under here.
Comment #20
catchdocumented :)
Comment #22
c960657 CreditAttribution: c960657 commentedThis broke the edit and delete links in the table on admin/international/translate/translate.
Comment #23
Dave ReidWe probably need some tests then...
Comment #24
pwolanin CreditAttribution: pwolanin commentedI tested this patch, and it fixes the bug (just a typo with leading slashes). Really this is not something likely to regress and we generally don't test our clickcable links everywhere in the UI with simpletest.
Comment #25
webchickCommitted to HEAD. Thanks!