Scanning and Filtering FAQ
Contents
- 1 Scanning and Filtering
- 2 Rule Sets
- 2.1 Do you have any model rule sets that we could leverage as 'models' for our own?
- 2.2 How can we filter out C# functions that should be filtered out from the Embedded Strings list?
- 2.3 Where can I find more introduction and materials about “General Pattern” issues found in C++ code scanning?
- 2.4 Is there support for detecting and fixing GUI alignment problems?
- 3 Javascript Filtering
- 3.1 You do not have a documentation for JavaScript locale sensitive methods in the help documents. But running the code scan does give violations in JavaScript locale sensitive methods – there is no fix code option, but a ignore option.
- 3.2 What is the fix for a violation like javascript.charAt()?
- 3.3 Is the javascript part something which is not supported in the evaluation version but will be in the licensed version?
- 3.4 Are there new JavaScript api’s available for these violations, or have you developed in house solutions for fixing these?
Scanning and Filtering
Can I use Globalyzer to look for issues in my code that have nothing to do with internationalization?
Yes. In fact this is quite common. One of the added values that our customers use Globalyzer for is as a repository for regular expression searches, which they can name, describe and share among their company’s developers.
How can I tell if I am using the correct method call for a supported locale?
For most 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.
Rule Sets
Do you have any model rule sets that we could leverage as 'models' for our own?
Each time we release, we try to add more default filters to our rule sets. It is an ongoing process.
How can we filter out C# functions that should be filtered out from the Embedded Strings list?
We do need to add more default string method filters for C#. If you have a server license, you could easily add these to your database. With your installation, there is a document that describes how to do this: Advanced_Globalyzer_Server_Usage_3_3.doc. If you do decided to go this route, please feel free to ask any questions.
Where can I find more introduction and materials about “General Pattern” issues found in C++ code scanning?
If you go to the Globalyzer Server and look at the General Patterns for your rule set, it will often give information on why Globalyzer is scanning for this pattern. In addition, if you go to the Help system on the Globalyzer Server, there are various topics on C++ internationalization. In particular, click on “Unsafe Methods”, then “C++ Programming Language”, and then “C++ Rule Sets”. This help page talks about Unicode support in the various C++ rule sets. For example, usually a C++ program will be compiled with single-byte character strings. These single-bytes cannot support Unicode characters, which require more than 1 byte. That is a main reason why our C++ General Patterns scan for character strings: because you will have to make sure to modify them if they are to hold Unicode strings.
Is there support for detecting and fixing GUI alignment problems?
This would be handled using programming patterns written to find fixed widths.
Javascript Filtering
You do not have a documentation for JavaScript locale sensitive methods in the help documents. But running the code scan does give violations in JavaScript locale sensitive methods – there is no fix code option, but a ignore option.
Globalyzer detects methods that could be an issue when supporting multiple languages, but has no specific fixing built in. This is because it’s not always clear that the method is an actual issue and the fix may involve some reworking that requires manual decisions. However, for some programming languages, we do have specific help for the detection that explains the reason for the detection as well as suggestions on what change might need to be made. When we don’t provide specific internationalization (i18n) help, we provide links to external help on the method, which sometimes provide information about i18n considerations.
What is the fix for a violation like javascript.charAt()?
In this case, Globalyzer detected charAt because it is a method that indexes into a string. If that string contains a translation, then the location of the character may have changed or it may not be the same character. The fix is really dependent on the usage. If the string is locale-independent, then you can insert an “Ignore This Line” comment so that Globalyzer will no longer flag this issue.
Is the javascript part something which is not supported in the evaluation version but will be in the licensed version?
We are always pressed to get more features into Globalyzer, but do try to spend as much time as possible adding to the help. We could add help for javascript in our next release. In the meantime, if you have any specific questions, you should email support@lingoport.com and we’ll get an answer for you right away!
Are there new JavaScript api’s available for these violations, or have you developed in house solutions for fixing these?
While Globalyzer doesn’t fix your method issues for you, it does allow you to document your resolutions directly in the Globalyzer Rule Set. For example, if you are an enterprise client, you can modify the default locale-sensitive methods for each programming language so that your users will also see your help modifications. If you’re using our hosted globalyzer.com, you can modify the locale-sensitive methods of a specific Rule Set that you create and then share that with other Globalyzer users that are part of your team. That way, once you do resolve an issue, others can benefit from your work.
