Closed (fixed)
Project:
Language Sections
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
19 Jun 2008 at 09:21 UTC
Updated:
4 Jul 2008 at 05:51 UTC
I came across your module which plugs some holes in the localization of Views content. But upon testing, it seems to not support Chinese language (zh-hans). Can you kindly check or confirm? From the previous posts, it seems you have tested it with fr and es only.. Thanks.
Comments
Comment #1
andy inman commentedHi, thanks for the information. It's not a bug, only a limitation of the default configuration. By default, the module assumes that language codes are in the form "aa" or "aa-bb" - such as: en, es, fr, en-uk, en-us. So, zh-hans will not be recognized as a language code. However, you can configure the module so that it will work:
Goto the configuration screen (filters, configuration) and set the "Use alternative pattern" option and copy/paste the pattern below:
Alternative pattern:
/(=+ *([a-z]{2}|[a-z]{2}-[a-z]{2,5}) *=+\s?)(.*?)/
Note, if you have more than one "Input filter" that uses Language Sections, you will need to configure each one in this way.
Please confirm if this works for you - it should.
Comment #2
sharifudinrizal commentedSuperb! It works..
So I take it this can only be used for Views' header, footer and empty text fields? Any idea how to translate field labels too? Thanks!!
Comment #3
andy inman commentedYes :) I'm working on another module to do just that! Actually it aims to be a general purpose tool for adding translation possibilities where they either don't exist or they do exist but are not easy to manage - that means Views, CCK and other modules where multiple languages don't work well.
http://drupal.org/project/language_extras
Please "feature requests" in the project area describing what you need to do. If you're interested in testing an early version of the module, let me know. Basically it already works, but I probably need to add more configuration options, and I need to build a Drupal 6 version - that will probably be today.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.