Difference between revisions of "Globalyzer Server and Rule Sets"
(Created page with "== If we customize one rule set for some specific files, how easy is it to apply the same rule set for other projects? == Multiple scans in multiple projects can use the same...") |
|||
| Line 1: | Line 1: | ||
| + | ==How can Globalyzer be leveraged across my development team?== |
||
| + | |||
| + | Software internationalization involves a surprisingly complex variety of issues, depending upon your requirements, technologies and unique application needs. Globalyzer’s client/server architecture lets you build and store internationalization detection and filtering rules (which we call '''Rule Sets'''), and which can then be shared within your development team. Developers can then perform internationalization tasks efficiently, whether they are working in the next cube or in the next country. |
||
| + | |||
== If we customize one rule set for some specific files, how easy is it to apply the same rule set for other projects? == |
== If we customize one rule set for some specific files, how easy is it to apply the same rule set for other projects? == |
||
Revision as of 22:32, 28 May 2019
How can Globalyzer be leveraged across my development team?
Software internationalization involves a surprisingly complex variety of issues, depending upon your requirements, technologies and unique application needs. Globalyzer’s client/server architecture lets you build and store internationalization detection and filtering rules (which we call Rule Sets), and which can then be shared within your development team. Developers can then perform internationalization tasks efficiently, whether they are working in the next cube or in the next country.
If we customize one rule set for some specific files, how easy is it to apply the same rule set for other projects?
Multiple scans in multiple projects can use the same rule set.
