Translation using i18n's multilingual variables doesn't work

Thanks for the rapid reply.

I've upgraded my Lightbox2 to the latest dev version of 01 Jan 2009 and tried the configurations again. It still doesn't work and still has the exact problem as described. I've tried clearing browser's and site's cache without success.

I noticed that when I first enabled the multilingual variables for Lightbox2 a few days ago, every time when I tried to save any multilingual variable related configuration on a Lightbox2 admin page, I would get the following error:

user warning: Access denied for user to database query: LOCK TABLES drupal_i18n_variable WRITE in C:\xampp\htdocs\includes\database.mysqli.inc on line 330.

However, it seemed that the changes have been saved without a problem. I didn't remember whether the translation for Lightbox2 worked or not, probably not. Later, after I've assigned the "LOCK TABLES" privillige the database user, the mentioned error has no longer occurred, but the translation problem (still) exists.

I'd really appreciate some feedbacks on this even if it's only a pointer. Thanks again!

I'm using Drupal 6.8 and i18n 6.x-1.0-beta6. I've enabled the following i18n modules:

Block translation
Content translation
Internationalization
Menu translation
String translation
Taxonomy translation
Views translation

I've attached a list of all my installed and enabled modules. Thanks!

Edit: Apart from the Lightbox2 multilingual variables, all my other multilingual variables work correctly.

I've got the following variables in my i18n_variable table:

anonymous
contact_form_information
date_format_long
date_format_long_custom
date_format_medium
date_format_medium_custom
date_format_short
date_format_short_custom
lightbox2_image_count_str
lightbox2_node_link_text
lightbox2_page_count_str
menu_default_node_menu
menu_primary_links_source
menu_secondary_links_source
site_footer
site_mission
site_name
site_slogan
theme_settings

My settings.php ends with the following:

$conf['i18n_variables'] = array(
'site_name',
'site_slogan',
'site_mission',
'site_footer',
'anonymous',
'blog_help',
'story_help',
'user_mail_password_reset_body',
'user_mail_password_reset_subject',
'user_mail_register_admin_created_body',
'user_mail_register_admin_created_subject',
'user_mail_register_no_approval_required_body',
'user_mail_register_no_approval_required_subject',
'user_mail_register_pending_approval_body',
'user_mail_register_pending_approval_subject',
'user_mail_status_activated_body',
'user_mail_status_activated_subject',
'user_mail_status_blocked_body',
'user_mail_status_blocked_subject',
'user_mail_status_deleted_body',
'user_mail_status_deleted_subject',
'theme_settings',
'menu_primary_links_source',
'menu_secondary_links_source',
'menu_default_node_menu',
'contact_form_information',
'date_format_short',
'date_format_short_custom',
'date_format_medium',
'date_format_medium_custom',
'date_format_long',
'date_format_long_custom',
'lightbox2_node_link_text',
'lightbox2_image_count_str',
'lightbox2_page_count_str'
);

Some the multilingual variables defined in my settings.php have not been used in practice so they do not appear in the i18n_variable table. The following are the corresponding Lightbox2 related values in the i18n_variable table (English (default)/Chinese):

s:18:"View Image Details";
s:18:"查看图片详情";
s:24:"Image !current of !total";
s:23:"Page !current of !total";
s:31:"第 !current 张 共 !total 张";    (i.e. Image !current of !total)
s:31:"第 !current 页 共 !total 页";    (i.e. Page !current of !total)

Again, all other multilingual variables, including site_name, works on the site.

I'm now trying to revert the site to the point before I installed Lightbox2. I'll then install the latest dev version (01 Jan 2009) of Lightbox2 straight away and set up the multilingual variables for Lightbox2 from scratch. I'll report back when it's done. Thanks again!

I've tried. It doesn't work and exhibits the same problem as described at the top.

Edit: I've PM'ed you! Thanks.

I've used the 6.x-1.9 release to update the 6.x-1.8 release installed on my development site and found that the exact problem still exists. But still, thanks for releasing 6.x-1.9 with so many new features and bug fixes!

Changed issue version from 6.x-1.x-dev to 6.x-1.9.