I just thought I'd toss out some tips from my experience when using Jose's rockin' i18n translation module. This also mentions using i18n in conjunction with the tinyMCE rich text wysiwyg editor. This is just what worked for me-- if anyone has any improvements or caveats, please feel free to post it.

  • links: Use relative links throughout your site. Your english/spanish site may look something like this:
    - http://domain/en/about
    - http://domain/es/about
    So your links within text should link about rather than /about or /en/about or en/about. This makes translation super easy: Find your content, translate it, and save-- links work relative to selected language (/en/about = /es/about)!
  • tinyMCE and links: TinyMCE (really nice rtf editor-- a must) by default rewrites urls according to document_base (tinymce documentation, see convert_urls). To turn off this behavior in Drupal, make your tinymcy.module, ~line 123 for me, look like:
    <script type="text/javascript">
      tinyMCE.init({
        $tinymce_settings
    		, convert_urls : false
      });
    </script>
    

    by adding the , convert_urls : false line

  • Good Workflow for translators:
    1. Log in to the site with your username password at this page:
      http://domain/user
    2. Click the link to the English version web site (the U.S. flag)
    3. Browse to the content to be translated (which has no translation yet) as if you were surfing the web
    4. Click the Translation tab
      1. Note: if there are two items listed there, this means the English node was never designated "English." Click the Edit tab, set the content to English under Language, and click Submit.
      2. Click Translation.
    5. Click create translation.
    6. Translate the content initially copied in from the English equivalent. Do not change any of the links themselves unless needed-- change only the text that is linked. Only change the links themselves if the non-Drupal document (PDF, etc) which is being linked should be a Spanish alternate version of the same document.
      Be sure to set properties that may not have carried over-- Publishing Options>>Sticky, for instance. I'm also not certain that book page hierarchy carries over.
    7. Click Submit at the bottom of the page.
      If the content you need to modify has already been translated, simply browse to the page in Spanish mode, click Editar (Edit) and make updates as normal.

Hmm. Would this be more appropriate as a handbook entry?

Comments

giorgosk’s picture

Definetelly for a handbook page if you ask me

I was about to try the I18n module myself.

------
GiorgosK
Web Development

robthedog’s picture

That sounds really interesting. I will try your approach tomorrow. could you please list which blocks and modules you are using to achieve this. I think it could help a lot of people with translation-problems!

Rob

texas-bronius’s picture

robthedog- you got me started on the right path with this thread on i18n for dumbies.

Modules used:
front_page
i18n
i18nblocks
i18nmenu
locale (that might be just for drupal... dunno)
menu
path (might be automatic with 4.7?)
tinymce
translation

I gathered the list above by skimming down my modules in admin and picking the ones that sound related-- it's probably a complete list. Most are i18n and are installed when you first set up i18n. The only surprise in the list there are front_page and tinyMCE. I think I'm not even using front_page anymore, b/c my Home links in each main menu in each language (see your old thread i18n for dumbies) link to en and es appropriately.

--
..happiness is point and click..

--
http://drupaltees.com
80s themed Drupal T-Shirts