Translations

hi,

my site www.anamika.co.in is in Marathi i want to put input language marathi.
as like www.manogat.com

means i want to user type in Marathi language on my website this is possible i am using right now TinyMce for textarea. here was any module for this ? or any other plan to use ?

pls Help me.

with reg

Raj

I want to create panel-based pages for first pages of my sections. I want to put one page/article in main part of selected panel and two block with views (first: list of articles in selected taxonomy - this is done by two different views and one multilingual block; second: teaser of newest article - not done yet).

But if i put selected node, users always see one language version (Polish) on this page with possibility to click English.

I've got my site running multilingual now. English and Spanish.

I've just enabled the poll mechanism, assigned it to a block and enabled multilingual support so that the question can be seen in both languages. It works fine if it always stays in one language. However if I switch language the poll resets itself to new. I can then go ahead and add votes to it and it will accumulate results but it will not be synchronised with the other language. Each language seems to carry it's own set of results.

i18n Is there any way to know if the node is translated or not?

Check out this node please : http://drupal.org/node/83959

Hi!
I was translating strings for my next drupal project (have some problems translating nodes by the way, but that's my next task), I found the following text: "The e-mail address is not made public" and it was hard coded in two modules:

• modules/user.module:1297
• modules/contact.module:125

As I see it, this is a decision that should be in the privacy policies of the site, and independent to modules drupal, although i know not giving away users email is the way to go, particularly on a social network project as I am working on.

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: