#112 closed task (fixed)
Translated Links
| Reported by: | jsanz | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | WebSite | Keywords: | |
| Cc: | arnulf, jsanz |
Description
It should be convenient to have the main links of the Main Page of www.osgeo.org translated into different languages.
It was discussed on the WebCom list but never fixed until now.
The thread starts here: http://lists.osgeo.org/pipermail/webcom/2007-April/001148.html
Change History (7)
comment:1 by , 17 years ago
| Cc: | added |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
comment:2 by , 17 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
WebCom: Do we need to vote on whether translators get permission to edit menus? If yes please indicate on the mailing list whether we should do that. Who can edit the users's roles? Is it inside LDAP or does it use the Drupal database?
comment:3 by , 17 years ago
I don't think we need to vote (it's part of the translation responsibilities). However, I'm not sure that Drupal has fine-grained enough permissions to allow admin access only for editing the menu blocks.
I'd not be in favour at all of granting full admin rights.
comment:4 by , 17 years ago
<menu module> <administer menu> is one checkbox. Cheking it obviously means that translators can totally mess up menus. Not opening up means that translators have to bug report translations for menaus and people with role <admins> have to update it.
The next one that we will want to give to translators is <path module>. There are two checkboxes <administer url aliases> and <create url aliases>. Makes sense too. Cannot mess up that much.
I did not change any permissions yet but suggest that we decide soon so that translation can proceed either way.
And yes there do seem to be some problems with translations. Especially long links seem to confuse Drupal, jsanz and I debugged two of them but it is not transparent to either of us what made things go wrong in the first place. This is irritating.
comment:5 by , 17 years ago
| Cc: | added |
|---|
I have added <menu module> <administer menu> to the role "translator".
Please edit with sense!
jsanz: can you please check whether you can now administer/translate menus? If you have trouble finding things ping TylerM or me on IRC.
WebCom: What about URL aliases? This smells like a larger topic. I really want get rid of some of the worm like directories that we inherited from the CN platform and in my experience it is necessary to be able to create new aliases as part of the translation. http://www.osgeo.org/node/81 is not a nice web url (funny, this one even exists?!).
comment:6 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
OK, they work, but for some strange reason (I think cache related) when I click on the main logo only one link (the oldest) appears translated).
Aliases... we should discuss but yes, /node/XX are funny links and are causing some troubles as Arnulf said before (specially with relative links). A convention like blah/blah/blah/page_ES for the original blah/blah/blah/page could be a nice fix for that.
This way, when I translate one page with many future translated pages, I only have to create the translated nodes (in English at first), everyone with its alias and afterwards I don't have to return to update every link for every page I translate (that sucks :|).
comment:7 by , 17 years ago
This should go to the mailing list for further discussion.
I'm sure that I've seen an option to expose the alias field to the page author, to allow them to specify their own.
This is already possible. Go to <administer>/<menu> and select <edit>. On the opening page at the top is a link translatoin that expands the page when licked. (Yuck, I hate to expain click & go. Please just stumble through these menus and find out yourself... :-)
You need permissions to administer <menu module> which only "admins" are allowed currently. You probably have the role "translator".