View comments | RSS feed
Contents > Developing ColdFusion MX Applications > Building a Search Interface > About Verity > Support for international languages PreviousNext

Support for international languages

ColdFusion supports Verity Locales in European and Asian languages. For European languages, ColdFusion uses LinguistX technology from Inxight; for Asian languages, ColdFusion uses ICU (IBM Classes for Unicode) technology. For more information about installing Verity Locales, see Installing and Using ColdFusion MX.

The default language for Verity collections is English. To index data in another supported language, select it from the drop-down list when you create a collection with the ColdFusion MX Administrator. In CFML, the cfcollection, cfindex, and cfsearch tags have an optional language attribute that you use to specify the language of the collection that you are searching. If you do not specify a language in these tags, ColdFusion checks the neo-verity.xml file for the collection's language. If this is defined, ColdFusion uses that language.

Use the following table to find the correct value for the language attribute for your collection; for example, the following code creates a collection for simplified Chinese:

<cfcollection action = "create" collection = "lei_01"
  path = "c:\cfusionmx\verity\collections"
  language = "simplified_chinese"> 

The following table lists the languages names and attributes that ColdFusion supports:

Language

Language attribute

Localization technology

Arabic

arabic

ICU

Chinese (simplified)

simplified_chinese

ICU

Chinese (traditional)

traditional_chinese

ICU

Czech

czech

ICU

Danish

danish

LinguistX

Dutch

dutch

LinguistX

English

english

LinguistX

Finnish

finnish

LinguistX

French

french

LinguistX

German

german

LinguistX

Greek

greek

ICU

Hebrew

hebrew

ICU

Hungarian

hungarian

ICU

Italian

italian

LinguistX

Japanese

japanese

ICU

Korean

korean

ICU

Norwegian

norwegian

LinguistX

Norwegian (Bokmal)

bokmal

LinguistX

Norwegian (Nynorsk)

nynorsk

LinguistX

Polish

polish

ICU

Portuguese

portuguese

LinguistX

Russian

russian

ICU

Spanish

spanish

LinguistX

Swedish

swedish

LinguistX

Turkish

turkish

ICU

You can register collections in the Administrator or by creating a collection with the cfcollection tag. If you register a given collection with ColdFusion and you specify a language attribute, then you do not have to specify the language attribute when using cfindex and cfsearch for that collection. If you do not register a given collection with ColdFusion, the language defaults to English, unless you specify it in the language attribute for the cfindex and cfsearch tags for that collection.


Contents > Developing ColdFusion MX Applications > Building a Search Interface > About Verity > Support for international languages PreviousNext

ColdFusion 9 | ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting

Version 6.1

Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.

Comments


mrali77 said on Jan 7, 2004 at 10:37 PM :
Dear Macromedia team i m working here in Dubai, UAE, and here we are facing alot problems in Flash becouse of not supporting arabic text.

In middle east market people want to use this software but becouse of it companies dont prefer and avoid it. You guys should bring some solution for it. And if solution is already there kindly do let me know on my email.
Thanks
Aali
jrunrandy said on Jan 9, 2004 at 6:06 AM :
Thank you for the feedback. I have forwarded your request to the Flash Product Manager.
cschmitz said on Sep 30, 2004 at 9:59 AM :
Hi,

please excuse me for going back to the page context, from Flash back to Verity. ;-))

If you try to search a collection in another language than English, you can not use the original operators AND resp. OR. You have to translate those into the langauge of the collection as well.

Examples:

English: one AND two
German: eins UND zwei
French: un ET deux

IMHO the operators are part of the query language and should not be translated. Besides, having to implement the operators in a dozen languages is an unneccessary complication of things.

Is there any workaround for this???

TIA

C. Schmitz

 

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/coldfusion/6.1/htmldocs/indexse6.htm