Difference between revisions of "Fixing i18n Issues FAQ"

From Lingoport Wiki
Jump to: navigation, search
Line 1: Line 1:
   
==How can I tell if I am using the correct method call for a supported locale?==
+
===How can I tell if I am using the correct method call for a supported locale?===
   
 
For many of its supported languages, Globalyzer will provide you with information and direction for refactoring methods and functions, giving examples and cross references when appropriate. It’s probably the largest on-line internationalization help system existing anywhere.
 
For many of its supported languages, Globalyzer will provide you with information and direction for refactoring methods and functions, giving examples and cross references when appropriate. It’s probably the largest on-line internationalization help system existing anywhere.
   
==Will Globalyzer help me adapt my application to support Unicode?==
+
===Will Globalyzer help me adapt my application to support Unicode?===
   
 
Yes, as is necessary to your particular programming language. You will have a number of character encoding support choices.
 
Yes, as is necessary to your particular programming language. You will have a number of character encoding support choices.
  +
  +
===How should I fix locale-sensitive Static File references?===
  +
  +
Static Files that might contain internationalization issues are usually handled by duplicating the files and locating them in locale-sensitive directories. The code is then refactored to retrieve the file based on the user's locale. Some examples of locale-sensitive static files are images with text, help files, video files, HTML files, and xml files that contain displayable text.
  +
  +
Globalyzer's [[Rule_Sets#Static_File_Reference_Scan_Rules|Static File Reference Scan]] will scan the source code for references to these types of static files. After you've filtered out the false positives, you'll need to refactor the references so that they use the locale to determine which static file to load.
  +
  +
===Will Globalyzer automatically externalize embedded strings?===
  +
  +
Globalyzer has the capability of externalizing an unlimited number of embedded strings with just a few keystrokes. However, once you select the strings you want to externalize, you may view each reported issue in a snippet of the code and exclude it from the externalization process as needed. While batch externalization is a huge time-saver in your internationalization process, we do recommend checking the strings carefully first.

Revision as of 20:55, 26 May 2012

How can I tell if I am using the correct method call for a supported locale?

For many of its supported languages, Globalyzer will provide you with information and direction for refactoring methods and functions, giving examples and cross references when appropriate. It’s probably the largest on-line internationalization help system existing anywhere.

Will Globalyzer help me adapt my application to support Unicode?

Yes, as is necessary to your particular programming language. You will have a number of character encoding support choices.

How should I fix locale-sensitive Static File references?

Static Files that might contain internationalization issues are usually handled by duplicating the files and locating them in locale-sensitive directories. The code is then refactored to retrieve the file based on the user's locale. Some examples of locale-sensitive static files are images with text, help files, video files, HTML files, and xml files that contain displayable text.

Globalyzer's Static File Reference Scan will scan the source code for references to these types of static files. After you've filtered out the false positives, you'll need to refactor the references so that they use the locale to determine which static file to load.

Will Globalyzer automatically externalize embedded strings?

Globalyzer has the capability of externalizing an unlimited number of embedded strings with just a few keystrokes. However, once you select the strings you want to externalize, you may view each reported issue in a snippet of the code and exclude it from the externalization process as needed. While batch externalization is a huge time-saver in your internationalization process, we do recommend checking the strings carefully first.