Does i18n have any sub-module to translate Contact module (name, description, receipt message, etc.)?

Thank you

Comments

manveru’s picture

manveru commented

I think this module is translatable by defining additional translatable variables:
$conf['i18n_variables'] = array(
// Site configuration
'site_name',
'site_slogan',
'site_mission',
'site_footer',
'anonymous',
// Contact form
'contact_form_information',
);
These works for me.

geodaniel’s picture

geodaniel commented
Title: Transalation for Contact module » Translation for Contact module
piotrsmykaj’s picture

piotrsmykaj commented

What with categories if contact form has them?

vthirteen’s picture

vthirteen commented
Title: Translation for Contact module » Translation for Contact module categories
Version: master » 6.x-1.1
Component: Experimental modules » Code
Category: feature » support

adding Contact form information in settings.php is not enough to translate contact form categories:
'contact_form_information'

is there any other setting that should be added? any workaround?
btw, is it at all a i18n bug?

R.Hendel’s picture

R.Hendel commented
Status: Active » Closed (fixed)

This should work like in #1 described

alexbk66-’s picture

alexbk66- commented
Component: Code » Blocks
Status: Closed (fixed) » Active

The issue is about translating CATEGORIES in admin/build/contact.

Setting 'contact_form_information' as multilang variable allows to translate "Additional Information" string in admin/build/contact/settings.

Any help with the Categories translation?

webflo’s picture

webflo commented
Version: 6.x-1.1 » 6.x-1.x-dev
Component: Blocks » Strings
Category: support » feature

I thinks its not possible atm. We need to backport i18n_contact to Drupal 6.

alexbk66-’s picture

alexbk66- commented

Duplicate FIXED here

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)