Difference between revisions of "Rule Sets FAQ"
(Blanked the page) |
|||
| Line 1: | Line 1: | ||
| + | ===Does Globalyzer fix JavaScript locale-sensitive method issues?=== |
||
| + | |||
| + | 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 have written internationalization (i18n) help for the method 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 i18n help, we provide links to external help on the method, which sometimes provide information about i18n considerations. |
||
| + | |||
| + | ===What is the fix for the JavaScript locale-sensitive method 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. |
||
| + | |||
| + | ===When will internationalization help be added for JavaScript locale-sensitive methods?=== |
||
| + | |||
| + | We are always pressed to get more features into Globalyzer, but do try to spend as much time as possible adding to the help. 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! |
||
| + | |||
| + | ===How do I add new JavaScript locale-sensitive methods or modify the description and help for existing methods?=== |
||
| + | |||
| + | If you have a Globalyzer Team Server license, you can add to or modify the default [[Rule Sets#Locale-Sensitive_Method_Scan_Rules|locale-sensitive methods]] for each programming language so that your users will also see your changes whenever they create a new Rule Set. If you’re using our hosted [http://www.globalyzer.com globalyzer.com] server, you can add to or modify the locale-sensitive methods of a specific [[Rule Sets#What_Are_Rule_Sets.3F|Rule Set]] that you create and then share with other Globalyzer users that are part of your team. That way, your team members will benefit from the work you have done in determining the resolution for locale-sensitive method issues. This approach applies to all Rule Set rules, such as General Patterns, Static File References, and all the many filters Globalyzer applies during code scanning. |
||
Revision as of 20:28, 26 May 2012
Contents
- 1 Does Globalyzer fix JavaScript locale-sensitive method issues?
- 2 What is the fix for the JavaScript locale-sensitive method charAt()?
- 3 When will internationalization help be added for JavaScript locale-sensitive methods?
- 4 How do I add new JavaScript locale-sensitive methods or modify the description and help for existing methods?
Does Globalyzer fix JavaScript locale-sensitive method issues?
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 have written internationalization (i18n) help for the method 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 i18n help, we provide links to external help on the method, which sometimes provide information about i18n considerations.
What is the fix for the JavaScript locale-sensitive method 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.
When will internationalization help be added for JavaScript locale-sensitive methods?
We are always pressed to get more features into Globalyzer, but do try to spend as much time as possible adding to the help. 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!
How do I add new JavaScript locale-sensitive methods or modify the description and help for existing methods?
If you have a Globalyzer Team Server license, you can add to or modify the default locale-sensitive methods for each programming language so that your users will also see your changes whenever they create a new Rule Set. If you’re using our hosted globalyzer.com server, you can add to or modify the locale-sensitive methods of a specific Rule Set that you create and then share with other Globalyzer users that are part of your team. That way, your team members will benefit from the work you have done in determining the resolution for locale-sensitive method issues. This approach applies to all Rule Set rules, such as General Patterns, Static File References, and all the many filters Globalyzer applies during code scanning.
