Supported languages with Unicode for analysis

The supported languages with Unicode are:

• Albanian
• Belarusian     
  
• Bosnian      
  
• Bulgarian
• Catalan
• Chinese  
  
• Croatian       
  
• Czech       
• Danish 
• Dutch     
• Estonian 
  
• Faroese     
• Finnish 
• French      
• German      
• English 
• Greek 
• Greenlandic Inuktitut      
• Hungarian 
• Icelandic
• Japanese - note that we do not support:
  • EUC-JP
  • ISO_2022_JP_3
• Irish      
• Italian      
• Latvian 
  
• Lithuanian 
• Luxembourgish      
• Macedonian   
• Maltese 
• Moldovan      
  
• Norwegian 
• Polish     
• Portuguese       
• Romanian 
• Russian       
  
• Serbian 
• Slovak 
• Slovenian      
• Spanish
  
• Swedish 
  
• Turkish
  
• Ukrainian

Any non-supported character that is present in the source code file encoded with one of the supported encodings, will be converted to an arbitrary supported character by CAST. The impact on the analysis result of this conversion depends on the situation in which the conversion occurs and on the character to which the conversion occurred. Therefore, the impact is unpredictable in a general way as for example:

• If the conversion occurs only in source code comments, there is no impact on the analysis result.
• If the conversion occurs inside an identifier and the converted identifier is no longer unique due to the conversion, resolution errors can occur.

Code page equivalence for Unicode Character Sets

The language of the code page used in the Operating System on the server acting as an AIP Node (where AIP Core and AIP Node package are installed) must be the same as the language used for the source code that needs to be analyzed. For example on an OS in Turkish you must analyze source code that is Unicode encoded for the Turkish language.

Encoding support

CAST Storage Service/PostgreSQL

CAST Storage Service/PostgreSQL can be used to store analysis results of Unicode encoded source files provided the files use one of the below mentioned encodings:

• UTF-8 without BOM
• UTF-8 with BOM
• UTF-16 with BOM
• GB 18030 (standard Chinese character set)
• BIG5 (Chinese character set for Taiwan, Hong Kong and Macau)

AIP schemas

The Dashboard, Analysis, Management and Measurement schemas support the following encodings:

• UTF-8 without BOM
• UTF-8 with BOM
• UTF-16 with BOM
• GB 18030 (standard Chinese character set)
• BIG5 (Chinese character set for Taiwan, Hong Kong and Macau)

AIP Analyzers

The following CAST analyzer...

• C/C++
• .NET > Please note that C/S links are not resolved when the T-SQL database collation is not the same as the server collation, and the machine collation is different then the server collation.
• ASP
• Visual Basic
• Universal Analyzer/Universal Importer
• JEE Analyzer extension (including EJB, Web Services and CAST Script )
• Mainframe
• ABAP
• PL/SQL
• T-SQL
• SQL Analyzer extension

...support the following encodings:

• UTF-8 without BOM
• UTF-8 with BOM
• UTF-16 with BOM
• GB 18030 (standard Chinese character set)
• BIG5 (Chinese character set for Taiwan, Hong Kong and Macau)

Other AIP features

The following CAST AIP components...

• CAST Server Manager
• CAST Management Studio, including:
  
  • Reference Patterns
  • Update Knowledge Base (Analysis Service) Assistant
  • XXL Table Quality Rule injection
  • Background Facts upload
  • Environment Profile Manager
• CAST Architecture Checker
• CAST Transaction Configuration Center
• Engineering Dashboard
• Health Dashboard
• Legacy CAST Engineering Dashboard
• Legacy CAST Discovery Portal
• CAST Report Generator
• CAST Logs
• CAST Delivery Manager Tool
• Command line (CAST Management Studio/CAST Delivery Manager Tool)
• Metrics Assistant

...support the following encodings:

• UTF-8 without BOM
• UTF-8 with BOM
• UTF-16 with BOM
• GB 18030 (standard Chinese character set)
• BIG5 (Chinese character set for Taiwan, Hong Kong and Macau)

All other unmentioned CAST AIP components may provoke an arbitrary error when analyzing or working with a Unicode encoded source code file.