multilingual

I have had a lot of research about optimizing Apachesolr for non-english languages, especially for German. It comes out, that there search results can be dramatically improved by adjusting Solr's stemming and by breaking up compound words. This can be easily achieved with slight changes to Apachesolr's schema.xml.

This post is about configuring stemming:
http://www.early-dance.de/en/news/9188-optimizing-apachesolr-non-english...

And this post is about compound word splitting, that is needed in languages like German that have long combined words like "Dampfschifffahrt":
http://www.early-dance.de/en/news/9189-apachesolr-issues-german-and-othe...

Hi all,

Mình dùng CCK tạo ra 1 kiểu Content Type là Product, trong Product có thêm 2 Field là:

1. Color: Select list gồm các giá trị
   1|Vàng
   2|Đỏ

2. Warranty: text filed bình thường

Sau khi tạo mình có thể dùng I18N dịch được các string như Color, Warranty, nhưng các value của các field thì không thể dịch được, ví dụ: Vàng, Đỏ. Hoặc khi nhập text cho Warranty xong, click translate thì nó chỉ hiểu được 1 value mà thôi.

Hi,

I am planning a multisite project where I want to be able to share users and some content between sites.

All sites will be more or less clones of each other, but they will have different target markets (countries mainly).

What I want to do is:

<

ul>

Found this review of Location module:

http://civicactions.com/blog/Location_Package_Drupal_6

<

blockquote>

Hi,

I'm not sure if I'm posting this in the correct section, but I posed a similar question on the main drupal forum and received no replies on the subject, so i'm hoping someone can assist me here if possible.

What options does one has when trying to set up an internationalized or multilingual user profile at multilingual site. When useing the core profile option the i18n module provides the posibility to translate the names of the profile fields, which might be enough for some profiles, but if you want a profile where user writes an introduction of him self, you are in trouble. Exposing the user entered text for translation trough t() function is not a good option.

This is an old issue, and I wish to get a clear up-to-date status of the situation in Drupal 6 (or 5). It may have been answered already, so a redirection would be as good as an answer :-)

1. RTL CSS files in core: In order to ease the RTLization of themes, and to set a nice example for themers and module developers, core modules should come with and RTL version of CSS. Such a set already exists, and is used in every hebrew Drupal site, and surely in other RTL languages sites as well.

The point of this post is to do a round up for the community, get on the same page with some of the developers, and find a path toward what to do for Drupal 6 core and beyond, as well as with contributed modules.