I'm confronted with the task to translate an existing (english) Drupal site into german and simultaneously setting it up as a multi-language site. The original is deeply intertwined and nested, with some vocabularies and rich menu structures and url aliases and so on. All this content will have to be translated.
I've stumbled upon a few issues which I do not know how to resolve in Drupal and which led me to question if it would be wise to use Drupal at all for the task:
1) URL aliases and text links: Most links point not to numerical content denominators, but to URL aliases. When translating an alias the original link does not work any more. But before the target article is translated the URL alias for this article can not yet be set. So it's a hen/egg situation in many cases with cross-references between articles, which means that at least one of them has to be edited twice - first to translate it, second to set the target url alias(es).
2) Structural changes. As of now the site is a collection of articles and custom modules. We plan to add a linear (book) structure for easier reading. How does this structure behave with translations and changes later on? What if we decide to move chapters around - will the translation be "automatically" be synchronized and reflect the new structure?
Hello there,
I am trying to translate the main menu. I have been successful when I to translate the horizontal main menu generated by the code in the theme, (am using zen) but I believe all built in use the same code which is
I was configuring the teaser mode for my front page content. The teaser trimmed just fine. Unfortunately, it also trimmed the full content of the node so that when one accesses the node via the Read More link or the title from the front page/blog, one is still presented with the trimmed version.
I don't know what's going on. I unchecked Teaser from Custom Display, took everything back to default, cleared the caches, and still have trimmed content in both the teaser and the full node.