Closed (fixed)
Project:
Localization server
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2008 at 14:13 UTC
Updated:
28 Nov 2023 at 06:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hass commentedComment #2
zirvap commentedYou can replace the text in the "Handy links" box with anything you want by using the locale function in core, see HOWTO: Creating a customized language set to replace Drupal terminology. I don't think there should be any automatic removal or replacement of text here -- it's much more flexible if those who want to use the interface for something else can make their custom changes.
I'm changing the priority to minor because there is another way available to achieve what you want (see the link above).
Comment #3
hass commentedThis is no reasonable solution. The module could solve this very easily. Maybe with a taxonomy term and node or anything else. Then i'm able to change the text easily. But as noted - the complete box makes no sense if this is not a d.o. translation project.
Comment #4
gábor hojtsyEh, why would the translators mailing list of group not make sense for people to suggest? Especially the translators docs? That has explanations on the placeholders, and other stuff, which is quite useful for translators using any tool.
Comment #5
hass commentedI'm thought about people using LS for their PO based translations (maybe an open source desktop software) that is not a Drupal like project. As the current placeholders are a special implementation in the Drupal world this may be totally different for other projects based on PO files. Other type of projects may have different rules. In such cases the Drupal links makes no sense and would provide wrong information.
Comment #6
gábor hojtsyYes, well, only one of these types of projects showed up so far, and indeed, that help box does not make sense in that case. Agreed.
Comment #7
gábor hojtsyThe d.o connector is discontinued, but we still have the handy links, which could indeed be made configurable, either with an on/off switch or a UI to edit its content. It would generally be more useful to be able to edit the page layouts for stuff like the l10n_server front page, but depending on Panels seems to be a bit "too big stone for the bird".
Comment #8
gábor hojtsyLet's make this a bit broader in scope and just remove all Drupalities from the welcome screen. This includes the explanation block and the handy links as discussed above. This software is (to be) used with other projects beyond Drupal, and since its compatible with all kinds of uses otherwise, we should not put Drupalities right on the welcome page either. People could put such explanations back in via blocks on the welcome page, around the main content (above, below, sideways, etc).
Comment #9
gábor hojtsyForgot to mention I've actually committed the patch.