RESOURCE ANALYSIS

BACKGROUND

Products that are released are often associated with a number of different versions that each targets a specific geographic location. For example, a software product can have a number of different versions, with each version being translated into a different language that corresponds to a specific geographic location and/or culture. This aspect of the product cycle is often referred to as localization. Problems can arise, however, when aspects of a software product are translated from one language to another. For example, a visual element associated with a graphical user interface can be improperly scaled after translation such that the visual element is not displayed properly within the graphical user interface. As another example, text associated with a software product can be mistranslated during the translation process. A mistranslation can cause problems with the functionality of the software product, such as software breakage or a software crash. Legal and/or political problems can also arise from mistranslation, such as the inclusion of a trademarked term in violation of trademark laws in a particular jurisdiction.

Current ways of detecting these and other problems that can arise during product localization are typically error-prone and labor-intensive. For example, some techniques require a user to manually enter all resources that are to be analyzed and are capable of analyzing only one resource at a time.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Various embodiments provide techniques for analyzing resources based on a set of rules to determine problems that may occur during a product development cycle. In accordance with some embodiments, resources can include files, strings (e.g., code strings), images, text, user interface elements (e.g. controls, radio buttons, and/or windows), and so on. For example, a resource for a software product can include a selectable control that is included as part of a graphical user interface for the software product.

In at least some embodiments, a resource analysis utility (“RAU”) is provided that can load resource files and automatically analyze associated resources according to a set of rules. According to some embodiments, the RAU includes a graphical user interface (“GUI”) that enables resource files to be selected and rules to be selected that are to be used to analyze the resource files. The GUI can also include results of the analysis of the resource files. For example, the GUI can display a table that includes the resource files that were analyzed, the rules that were used to analyze the resource files, problems that were detected during the analysis, and so on.

BRIEF DESCRIPTION OF THE DRAWINGS

The same numbers are used throughout the drawings to reference like features.

FIG. 1 illustrates an operating environment in which various principles described herein can be employed in accordance with one or more embodiments.

FIG. 2 illustrates an example resource analysis scenario in accordance with one or more embodiments.

FIG. 3 illustrates a resource analysis utility graphical user interface in accordance with one or more embodiments.

FIG. 4 illustrates a report area of a resource analysis utility graphical user interface in accordance with one or more embodiments.

FIG. 5 illustrates a master resource table of a resource analysis utility graphical user interface in accordance with one or more embodiments.

FIG. 6 illustrates a details table in accordance with one or more embodiments.

FIG. 7 illustrates a statistics table in accordance with one or more embodiments.

FIG. 8 illustrates an example graphical user interface in accordance with one or more embodiments.

FIG. 9 illustrates a command line interface that can be used to implement a resource analysis utility in accordance with one or more embodiments.

FIG. 10 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

FIG. 11 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

FIG. 12 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

FIG. 13 illustrates an example system that can be used to implement one or more embodiments.

DETAILED DESCRIPTION
Overview

Various embodiments provide techniques for analyzing resources based on a set of rules to determine problems that may occur during a product development cycle. In accordance with some embodiments, resources can include files, strings, images, text, user interface elements (e.g. controls, radio buttons, and/or windows), and so on. For example, a resource for a software product can include a selectable control that is included as part of a graphical user interface for the software product.

In at least some embodiments, a resource analysis utility (“RAU”) is provided that can load resource files and analyze associated resources according to a set of rules. According to some embodiments, the RAU includes a graphical user interface (“GUI”) that enables resource files to be selected and rules to be selected that are to be used to analyze the resource files. The GUI can also include results of the analysis of the resource files. For example, the GUI can display a table that includes the resource files that were analyzed, the rules that were used to analyze the resource files, problems that were detected during the analysis, and so on.

In an example implementation, a user can launch the GUI and select resource files to be analyzed. The user can then select rules to be run on the selected resource files. Examples of rules that can be used to analyze resources are provided below. The RAU can then run an analysis of the selected resource files using the selected rules. In at least some embodiments, results of the analysis can be displayed via the GUI.

In at least some embodiments, the RAU can be implemented via a command line interface. For example, a user can invoke the RAU using a command line interface and then enter command line arguments that specify resource files to be analyzed and rules to be used for the analysis. This aspect of the RAU is discussed in more detail below.

In the discussion that follows, a section entitled “Operating Environment” is provided and describes one environment in which one or more embodiments can be employed. Following this, a section entitled “Example Resource Analysis Scenario” describes an example resource analysis scenario in accordance with one or more embodiments. Next, a section entitled “Example User Interfaces” describes example user interfaces that can be used to analyze resources in accordance with one or more embodiments. Following this, a section entitled “Example Command Line Interface” describes example ways of resource analysis utilizing a command line interface in accordance with one or more embodiments. Next, a section entitled “Example Methods” describes example methods in accordance with one or more embodiments. Following this, a section entitled “Example Rules” discusses example rules that can be used to analyze resources in accordance with one or more embodiments. Last, a section entitled “Example System” describes an example system that can be utilized to implement one or more embodiments.

Operating Environment

FIG. 1 illustrates an operating environment in accordance with one or more embodiments, generally at 100. Environment 100 includes a computing device 102 having one or more processors 104 and one or more computer-readable storage media 106. The computer-readable storage media can include, by way of example and not limitation, all forms of volatile and non-volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. One specific example of a computing device is shown and described below in FIG. 13.

In addition, computing device 102 includes a module in the form of a resource analysis utility 108 that can be utilized to analyze a variety of different resources. The resource analysis utility (RAU) includes and/or makes use of a user interface 110, a rules module 112, a file type interpreter 114, and a reporting module 116. According to some embodiments, the user interface can be used to interact with the RAU via a variety of different user interfaces, e.g., graphical user interfaces. In at least some embodiments, the rules module includes a variety of different rules that can be selected and/or used to analyze resources.

According to some embodiments, the file type interpreter 114 is capable of receiving resource files in a variety of different formats and interpreting the resource files such that they can be analyzed by the RAU. For example, the file type interpreter can include a variety of different file type wrappers that can each determine a file type associated with a specific resource file and interpret data within the resource file according to rules and/or logic associated with a respective file type wrapper. Examples of file types that can be interpreted by the file type interpreter include, by way of example and not limitation, text files, media files (e.g., video, audio, and so on), image files, markup language files, and so on.

According to at least some embodiments, the reporting module 116 is configured to report the results of resource analysis in a variety of different ways. For example, the reporting module can generate a table that lists the resources that were analyzed, the rules that were run during the analysis, and the results of the analysis. The reporting module can also flag resources and/or rules that may be associated with potential problems, e.g., problems that may occur when a particular resource is localized.

The computing device 102 also includes resources 118, a command line interface 120, and external components 122. According to some embodiments, the resources 118 include a variety of different resources, such as files, images, strings, text elements, and so on. For example, the resources 118 can include a graphical element that is included as part of an application's graphical user interface.

In at least some embodiments, the command line interface 120 presents one example way in which the RAU can be invoked. Example implementations of the RAU via the command line interface are discussed below. According to some embodiments, the external components 122 can include a variety of different external components from which the RAU can retrieve information and to which the RAU can report. For example, the external components can include a bug filer to which the RAU can report a problem that was detected during an analysis of a resource.

In addition, environment 100 includes a network 124, such as the Internet, and one or more remote entities 126 with which the RAU can communicate. Examples of the remote entities 126 include a remote web server, a cloud computing resource, and so on. In some example embodiments, the RAU can retrieve rules and/or resources from the remote entities. Further to some embodiments, the RAU can also report resource analysis results to the remote entities.

Computing device 102 can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer, a portable computer, a handheld computer such as a personal digital assistant (PDA), cell phone, and the like.

Having described an example operating environment, consider now a discussion of an example resource analysis scenario utilizing the techniques and tools discussed herein.

Example Resource Analysis Scenario

FIG. 2 illustrates an example resource analysis scenario utilizing techniques and/or tools discussed herein, generally at 200. The resource analysis scenario 200 includes a display interface 202 that can be associated with a variety of different applications, such as a web browser, an enterprise application, a word processing application, mobile applications, and so on. As part of the display interface are several resources, including resources 204, 206, and 208. In at least some embodiments, the resources 204, 206, and 208 can be created according to a first language and/or culture, e.g., English. When the resources are translated into a second language (e.g., as part of a localization process), a number of different problems can occur.

For example, a translation 210 illustrates that when the resources 204 and 206 are translated as part of a localization process, the resource 204 overlaps and partially obscures the resource 206. In some embodiments, this can be considered undesirable as it can detract from the visual appeal and usability of the display interface 202. As another example, a translation 212 illustrates that when the resource 208 is translated (e.g., as part of a localization process), a term that should not be translated (e.g., “Microsoft®”), is partially translated into Japanese. In at least some embodiments, this partial translation violates a constraint set on the term that specifies that the term is not to be translated during localization.

The resource analysis scenario 200 also includes resource analysis results 214. In at least some embodiments, the resource analysis results can be generated by the reporting module 116 as a part of a resource analysis session implemented by the RAU 108. As illustrated, the resource analysis results include a flag for the translation 210 that indicates that localization may cause the resource 204 to visually overlap with the resource 206. As also illustrated, the resource analysis results include a flag for the translation 212 that indicates that a term associated with the resource 208 should not be translated and that localization may cause the resource 208 to be partially or completely translated.

Having described an example resource analysis scenario, consider now a discussion of some example graphical user interfaces that can be used to implement the RAU.

Example User Interfaces

FIG. 3 illustrates an example graphical user interface (GUI) that can be used to implement the RAU in accordance with one or more embodiments, generally at 300. GUI 300 includes a rules area 302 which can display rules and can be used to select rules to be used to analyze resources. Example rules are discussed in more detail below. The GUI 300 also includes a resource area 304 in which resources can be displayed and selected for analysis. As discussed above, the RAU can be implemented to analyze resources in a variety of different file types. Accordingly, in at least some embodiments, the resource area can enable resources associated with a variety of different file types to be selected. In addition, GUI 300 includes a report area 306 and a master resource table 308, each of which is discussed in more detail below.

In some example embodiments, the GUI 300 includes a variety of selectable controls that can be selected to access and/or initiate various functionalities of the RAU. For example, the GUI 300 includes an add resources control 310 that can be selected to cause the resources area 304 to be displayed. A user can then select resources from the resources area for analysis. The GUI 300 also includes an add rules control 312 which can be selected to cause the rules area 302 to be displayed for selection of rules to be used for resource analysis.

In at least some embodiments, the GUI 300 includes a start analysis control 314 and a stop analysis control 316 which can be selected, respectively, to start and stop a resource analysis process. Also included as part of the GUI 300 is an unattended control 318 that can be selected to indicate that a resource analysis session is to be run in an unattended mode. For example, in some embodiments the RAU can present one or more prompts during a resource analysis session (e.g., via a popup window) that request user input. In at least some embodiments, presenting a prompt can cause the resource analysis session to be paused until a user provides the requested input. If a user is not present to provide the requested input, this can prevent the resource analysis session from continuing until a user becomes aware of the prompt and provides the requested input.

Accordingly, in some embodiments the unattended control 318 can be selected to cause a resource analysis session to run without prompting a user for input during the session. For example, if the RAU requests input during a resource analysis session, the RAU can maintain default values that can be automatically used for the input without requesting user input. Thus, in at least some embodiments, the unattended mode enables all or part of a resource analysis session to be run without the presence of a user, e.g., without user input.

Also included as part of the GUI 300 is a report control 320 that can be selected to access reporting functionalities of the RAU. For example, selection of the report control can cause the report area 306, the master resource table 308, a statistics table (discussed below), a trend table, and/or any other suitable reporting functionality to be displayed. In at least some embodiments, a selection of the report control 320 can cause the results of a resource analysis session to be reported to a remote entity, e.g., the remote entities 126.

The GUI 300 also includes a flag control 322 and an export control 324. In at least some embodiments, the flag control 322 can be selected to cause resource files that are associated with potential problems to be flagged. For example, an analysis of a particular resource may determine that the resource may be improperly formatted after localization. Actuating the flag control can cause the resource to be visually highlighted in the GUI 300, e.g., as part of the report area 306 and/or the master resource table 308.

According to some embodiments, the export control can be selected to export the results of a resource analysis session. For example, the export control can be selected to cause the results to be exported to an external application, such as a spreadsheet application.

FIG. 4 illustrates the report area 306 in more detail, in accordance with one or more embodiments. In this example, report area 306 includes a number of columns that include information about a resource analysis session. For example, the report area includes a resource type column 400 that indicate types for the resources that were analyzed during a particular resource analysis session. In this particular illustrated embodiment, the resource types include tables and controls.

The report area also includes a file name column 402 that displays file names associated with the resources analyzed during a resource analysis session. For example, the file name column can include file names that were selected via the resource area 304. Also included in the report area is a target culture column 404 that lists cultures and/or languages that are associated with a resource analysis session. In this particular illustrated embodiment, the resources that were analyzed are associated with the Japanese culture. A rule column 406 included as part of the report area lists the rules that were used during the resource analysis session.

Also included as part of the report area is a result column 408 that lists resource analysis results. For example, the results can include an indication of potential problems that were detected during the analysis of a resource. In this particular example, the results include an indication that the first resource was properly localized and an indication of warnings associated with the other analyzed resources.

The report area also includes an explanation column 410 that can display various messages associated with resource analysis. For example, an explanation can include information about a particular resource analysis result indicated in the result column. In this particular example, the explanation column indicates that the first resource was correctly localized and also indicates information about the warnings provided for the remaining resources.

The columns included in the report area 306 are presented for purposes of example only, and in some embodiments, the report area can be configured to present a variety of different types of information. Examples of different types of information that can be presented via the report area include:

a resource identifier;

a date on which a resource was modified;

a source string for the resource;

a source type for the resource;

a target string for the resource;

an original untranslated version of the resource;

a localization status of the resource;

comments regarding the resource;

other cultures associated with the resource;

a priority associated with the resource;

a log file path for an analysis associated with the resource; and

the validity of the resource.

FIG. 5 illustrates the master resource table 308 in more detail, in accordance with one or more embodiments. The master resource table includes a variety of different information about resources. For example, the master resource table includes a resource type column 500 that indicates types for particular resources. A resource string column 502 includes information about resources in their original form, e.g., a resource before it has been localized.

The master resource table also includes an Arabic column 504 and a Japanese column 506. These columns each include translations of the resources indicated in the resource string column 502 into their respective languages. According to some embodiments, some resources and/or terms are designated as not to be translated during the localization process. As illustrated in this particular example, the term “Windows Live®” is designated as not to be translated during the localization process. In some embodiments the Master resource table enables a variety of different information about resources to be displayed and provides a visual indication of how the localization process can affect resources.

FIG. 6 illustrates a details table 600, in accordance with one or more embodiments. The details table is configured to display a variety of different details about resources and in at least some embodiments can be accessed and/or invoked via the GUI 300. In this particular example embodiment, the details table includes a resource column 602, an aspect column 604, and a value column 606.

The resource column includes descriptions of resources, such as text associated with a particular resource. In this particular example, the resource includes the text “Added a blog entry.” The aspect column displays different aspects of resources that can be viewed via the details table. In at least some embodiments, aspects can include a translation of a resource and physical dimensions of a resource, such as a length of a resource, a width of a resource, a height of a resource, and so on.

The value column includes values for the aspects indicated in the aspects column. In this particular example, the value column includes a translation of the resource and the length, width, and height of the resource. In at least some embodiments, the length, width, and height refer to the size and/or placement of a resource (e.g., in millimeters) when it is displayed, e.g., as part of a user interface.

FIG. 7 illustrates a statistics table 700, in accordance with one or more embodiments. In at least some embodiments, the statistics table is configured to display a variety of different statistics about resources and in some embodiments can be accessed and/or invoked via the GUI 300. The statistics table includes a file name column 702 that includes filenames associated with particular resources. The statistics table also includes a resource type column 704 that indicates a type for each of the resources included in the statistics table.

A statistics field column 706 indicates the particular statistics that are being tracked via the statistics table. Also included as part of the statistics table are statistic values columns 708 and 710. The statistic values columns include values for the particular statistics being tracked by the statistics table for particular cultures and/or languages.

As an example implementation of the statistics table, consider a statistical analysis for resources 712. The statistical analysis is for a “word” resource type (e.g., a textual word) and the statistic being analyzed is how many of the resources 712 are localized, i.e., as indicated by “Localized” in the statistics field. The values included in the statistical values columns 708 and 710 indicate that 86 of the resources 712 were localized in Arabic and in Japanese. In at least some embodiments, discrepancies and/or variations indicated in the statistics table can indicate potential problems with a resource and/or a localization process. For example, a variation between cultures in a number of resources localized can indicate that some resources that should not be localized are in fact being localized, and vice-versa.

FIG. 8 illustrates an example graphical user interface (GUI) that can be used to implement the RAU in accordance with one or more embodiments, generally at 800. In at least some embodiments, the GUI 800 can enable various settings associated with the RAU to be specified such that the settings can be applied for multiple resource analysis sessions without having to specify the settings for each session.

The GUI 800 includes a general settings region 802, an additional settings region 804, and a master resource table settings region 806. According to some embodiments, the general settings region 802 can enable various general settings for the RAU to be specified. In this particular illustrated embodiment, the general settings region enables a user to specify one or more default file types to be used during a resource analysis session, as well as a folder to which a report of the resource analysis session results can be saved.

In at least some embodiments, the additional settings region 804 can enable other various settings associated with the RAU to be specified. For example, in the illustrated example embodiment the additional settings region 804 includes an “Unattended” field where the unattended mode of the RAU can be turned on or off. The unattended mode of the RAU is discussed above in more detail.

According to some embodiments, the master resource table settings region 806 enables settings associated with a master resource table to be specified. For example, this particular illustrated embodiment enables a font family associated with a master resource table to be specified.

The settings and regions illustrated in GUI 800 are presented for purposes of example only, and other embodiments of the GUI 800 can include a variety of different parameters, settings, and fields that can be used to configure various aspects of the RAU.

The example GUIs and tables presented above are for purposes of example only, and a variety of different information can be presented associated with product localization. Examples of different information that can be presented include statistical deviations, data trends, historic analysis data, charts of analysis data, and so on. In at least some embodiments, some or all of this information can be presented via a single user interface.

Having considered example user interfaces in accordance with one or more embodiments, consider now an example implementation of the RAU via a command line interface.

Example Command Line Interface

FIG. 9 illustrates a command line interface 900 that can be used to implement the RAU, in accordance with one or more embodiments. In at least some embodiments, the command line interface can be used to invoke the RAU and to set up and run a resource analysis session via the RAU. The command line interface includes example command line parameters 902 that can be used to configure the RAU for resource analysis. Each of the example command line parameters are discussed in Table 1 below, in accordance with one or more embodiments.

TABLE 1

Parameter
Function

help
Display the help message.

source
Indicate the resources (e.g., files and/or folders) to be tested.

rules
The rules to be run on the selected resources. This command can

be followed by one or more rule names. According to some

embodiments, by default all available rules will run unless specific rules

are specified here.

RuleConfig
Using this parameter, rules can be enabled or disabled and then

run. If the “/Rules” parameter discussed above is utilized, in

some embodiments the “/RuleConfig” parameter can be skipped.

The rules to be run for analysis can be indicated by setting the

‘Enabled’ tag in RulesConfig.xml. In some example

embodiments, ‘1’ indicates that a rule is enabled and ‘0’ indicates

that a rule is disabled.

logpath
This parameter can indicate a location for saving the results of

resource analysis. In some embodiments, if a location is not

specified, the results can be saved to a default location. For

example, a folder named “Analysis Result” can be created in

working folder and the results saved to that folder.

sourceFilter
This parameter can be used to tag specific resources that are

to be analyzed. In some embodiments, RAU will run the rule on all source

strings by default.

Example Options:

N: Run SAT only on the strings that are not localized.

L: Run SAT only on localized strings.

/FileFilter
In some embodiments, this tag can be set to on so that RAU only

checks indicated file formats. In at least some embodiments, one

or more file formats can be input. If this tag isn't set, in some

embodiments RAU will check all supported file formats. In at

least some embodiments, if only ‘/FileFilter’ is provided and/or some

invalid options are provided, RAU will run all the

supported file formats by default.

Example Options: lcl: Run SAT only on .lcl files

edb: Run SAT only on .edb files

lspkg: Run SAT only on .lspkg files

resx: Run SAT only on .resx files

rcxml: Run SAT only on .rcxml files

all: Run SAT on all supported files

/unattend
In some embodiments, this parameter can be set to “yes” or “no”

if user input may be requested. For example, this parameter can

be set to “Yes” to allow the RAU to run in silent mode and

without presenting prompts for user input. In some embodiments,

by default a user will provide input when the process requests it.

/w
In some embodiments, a warning level threshold can be specified

(e.g., <0-4>). For example, in some embodiments if a warning

level is specified, only errors that meet or exceed to specified

warning level will be logged. In at least some embodiments, a default

warning level can be specified.

In at least some embodiments, after the command line parameters have been set, a user can run the command line parameters to cause the RAU to analyze a selected set of resources.

Having considered an example command line interface in accordance with one or more embodiments, consider now some example methods in accordance with one or more embodiments.

Example Methods

FIG. 10 is a flow diagram that describes steps a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented via a resource analysis utility, such as the one described above.

Step 1000 receives a selection of resources to be analyzed. Examples of resources are discussed above and below. In at least some embodiments, resources can be selected via a GUI and/or by specifying resources via a command line interface. Step 1002 receives a selection of rules to be used for analysis of the resources. Additionally or alternatively, a default set of rules can be run if no specific rules are selected. According to some embodiments, the rules can be selected via a GUI and/or by specifying rules via a command line interface. In at least some embodiments, the rules to be run for a resource analysis can be selected prior to a selection of the resources to be analyzed.

Step 1004 analyzes the selected resources using the selected rules. Step 1006 outputs results of the analysis. In at least some embodiments, the results of the analysis can be output via the report area 306, the master resource table 308, the details table 600, the statistics table 700, and/or a command line interface (e.g., the command line interface 900).

FIG. 11 is a flow diagram that describes step 1004 of FIG. 10 in more detail in accordance with one or more embodiments. Step 1100 pseudo-localizes the selected resources. In at least some embodiments, pseudo-localizing a resource can include applying an algorithm to the resource that determines the form, structure, and/or appearance of the resource upon localization and generates a pseudo-localized version of the resource. For example, pseudo-localization of a resource can include translating the resource from one language to a different language. In at least some embodiments, pseudo-localization can include an analysis of the original resources (e.g., in English) to ensure that the resources are localizable and/or do not include errors such as spelling errors, formatting errors, and so on.

Step 1102 applies a rule to the original resources and to the pseudo-localized resources to detect a variation from the rule. In at least some embodiments, applying rules to the original resources and to the pseudo-localized resources can include detecting a pattern associated with the resources and determining if the pattern varies across any of the resources. Example rules and patterns are discussed below in Table 2. For example, a particular rule can determine that an original resource includes a URL but a pseudo-localized resource does not include a URL. This can cause the pseudo-localized resource to be flagged as a potential problem. In at least some embodiments, rules can be applied to detect patterns and/or pattern variations for a resource in multiple different languages and/or cultures in a single resource analysis session.

FIG. 12 is a flow diagram that describes example steps that can occur during a product development cycle in accordance with one or more embodiments. In at least some embodiments, the RAU can be employed during and/or between the various steps of the product development cycle to analyze resources. According to some embodiments, the RAU can determine if resource problems exist with a resource and/or if potential problems may occur with a resource during the product development cycle.

Step 1200 is a resource phase of the example product development cycle. During the resource phase, resources can be developed and/or gathered prior to implementation in the actual code of a product. In at least some embodiments, the RAU can be utilized during the resource phase to detect problems with individual resources and to ensure that resources are appropriately commented such that the resources can be accurately translated into different languages and can be correctly integrated into a product. In at least some embodiments, the RAU can be used during the resource phase to determine if a resource can be correctly localized.

Step 1202 is the pseudo-localization phase of the example product development cycle. During the pseudo-localization phase, determinations can be made if resources are capable of being localized and if the localization process may cause a resource to fail, e.g., a loss of resource integrity due to localization. In at least some embodiments, the RAU can be utilized during the pseudo-localization phase to determine if a resource is capable of being localized and to determine if the localization process may cause a problem with the resource. For example, consider a resource that is associated with a GUI element such as a dialog box, a control, a text element, and so on. It is possible that during localization, display-related problems can occur such as truncation of the GUI element, clipping of the GUI element, overlap of the GUI element with a different GUI element, and so on. Additionally, the presence of improper code or language-neutral content that can cause product breakage in different languages can be detected. In at least some embodiments, the RAU can detect these problems and cause the resource associated with the GUI element to be flagged. A developer or other entity can then take appropriate actions to mitigate these problems, such as changing the resource itself and/or commenting the resource such that during localization, steps can be taken to prevent these problems.

Step 1204 is the preparation phase of the example product development cycle. During the preparation phase, resources are validated as being ready for localization. In at least some embodiments, the RAU can be utilized during the preparation phase to determine if resources are consistent across multiple languages and/or to determine that if are improper variances in resource count, resource content, resource structure, and so on.

Step 1206 is the localization phase of the example product development cycle. During the localization phase, resources are put through the actual localization process to ready the product for a particular culture and/or language. In at least some embodiments, the RAU can be utilized as part of the localization phase to determine if terms are used consistently across different cultures and/or languages and to make sure that resources that are intended for localization are actually localized and that resources that are not intended for localization are not localized. According to some embodiments, the RAU can be utilized as part of the localization phase to determine if localization will have an undesirable impact on the visual appearance and/or usability of a product.

Step 1208 is the build phase of the example product development cycle. During the build phase, localized resources are integrated into the final product. In at least some embodiments, the RAU can be utilized as part of the build phase to determine if a localized resource may cause the final product to fail and/or if the build process may cause a resource to fail. According to some embodiments, the RAU can also be implemented to statistically analyze resources across multiple cultures and/or languages during the build process. The statistical analysis can include word counts associated with resources, resource types associated with resources, size dimensions associated with resources, and so on. The statistical analysis can then be used to determine if unexpected variances exist that may indicate a problem with a resource and/or the final product. According to some embodiments, the RAU can also be utilized as part of the build phase to determine if resources and/or the final product are able to be processed by language-neutral scripts to generate visual elements, e.g., a GUI.

Accordingly, in at least some embodiments the techniques and tools discussed herein (e.g., the RAU) can be utilized before, during, and/or after the various steps of a product development cycle to analyze resources and determine if problems with a particular resource exist and/or if problems may occur when a resource is integrated into a particular product, e.g., during the localization phase.

Having considered some example methods in accordance with one or more embodiments, consider now some example rules that can be used to analyze resources in accordance with one or more embodiments.

Example Rules

Table 2 below includes example rules that can be utilized to analyze resources in accordance with one or more embodiments. Table 2 is not intended to be an exhaustive list of rules, but is presented for purposes of illustration only. Additionally, the rule names, categories, descriptions, search patterns, examples, and formats are not intended to be limiting, but are presented for purposes of ease of understanding.

TABLE 2

Search Pattern

(Example

Resource

Example

Rule Name
Description
Failure)
Example
Formats

Category: Pseudo Localization

Pseudo
Detects number
If source string is
Source: 2
lcl

Numbers
strings in the source
only numbers
Target:
lspkg,

that have been
and translation is

custom-character

edb

pseudo localized in
not only numbers

custom-character

the translation.

Pseudo Tokens
Detects XML/HTML
If translated

lcl

tags in the source
XML/HTML tag

lspkg,

that have been
does not match

edb

pseudo localized in
source

the translation.

SkipTextInside
Skip text inside
If string inside
Don't
lcl

Brackets
({{ . . . }})
placeholder
translate text
lspkg,

appears in source
inside
edb

string AND
placeholder

doesn't appear in
({{ . . . }})

the target string

AND it appears

in placeholder

specs, rule is set

to indicate failure

Pseudo
Detects start and end
If target string is
Expected
lcl, edb,

Delimiters
delimiters in the
missing the
target string:
lspkg,

target string of the
starting and
text
resx,

pseudo localized
ending (e.g.,
Tagged as
rcxml

term.
or custom-character

).
failure:

text or

test or

text

Category: Localizability

NonStandard
Scans for non-
If source contains
Source:
All

Placeholder
standard placeholders
a non-standard
Vendor{21150}

and matching
placeholder but
Comments:

comments.
lacks matching
RCCX:

comments.
Name = idsAthenaTitle

FeatureName =

MSOE

URL
Scans source strings
If source has a
Source:
All

for URLs and looks
URL and
http://feedback.live.com/

for identical
comments do not
Comments:

matching comments.
contain URL.
RCCX:

Name = idsHelpMSWebFeed

Category: Comments

CodeReference
Identifies coding
If source contains
Source:
All

references such as a
the pattern of a
SpinNumSubj

function call or
function call or
Comments:

name.
name and
null

comments do not

contain matching

function.

Concatenation
Looks for
If source contains
Source: To
lcl,

concatenation (e.g.,
concatenation
help prevent
lspkg,

custom-character

-!, etc) in the
and comments
your
edb

source string and
lack same
messages

matching comments.
character.
from being

identified as

possibly

fraudulent:

Message:

Comments

are missing

context for

the ‘:’ symbol

listed in the

source.

ContainsEmail
Detects the presence
If source contains
Source:
All

of an email address
email and
example555@hotmail.com

and associated
comments do not
Comments:

comments.
contain the exact
RCCX:

same email
Displayed

under the ID

combo box.

Name = IDS_EXAMPLE_LIVE_ID

FeatureName = FSUI

ContainsGlink
Checks for the
If source contains
Source:
All

presence of a g-link
a g-link and
http://g.msn.com/5meen_us/122

(http://hotmail.live.com\en-us\)
comments do not
Comments:

and
contain the exact
RCCX:

related comments.
same g-link.
Name =

IDS_MSNMSGR_UPGRADE_URL

FeatureName = Common

ContainsTokens
Looks for comments
If source contains
Source:
lcl,

on detected items
either XML or
<font
lspkg,

contained within
HTML tags and
face = “Arial”
edb

brackets < > for both
no comments
>Your

XML (generic) and
match detected
Secure

HTML (specific).
tags.
Receipt:</font>

Comments:

null

NonConforming
Flags an error when
If comments
Source:
All

Comments
the comments words
words count less
Receipts

countless that the
than the
Comments:

limitation words
limitation words
null

count value
count

(Example default
value(Default

value is 0).
value is 0).

GenderString
Looks for matches
If words from
Source:
All

from
GenderString.xml
Female

GenderString.xml in
are in source
Comments:

source string that are
and not listed in
null

absent in comments.
comments.
Message:

Gender

string in

source string

but no

comments on

them.

Matches:

Female;

NumberStrings
Flag source strings
If source contains
Source 19
All

that contain a number
a numerical value
Comments:

value but do not
and comments do
null

contain a matching
not match the
Message:

comment.
numeric value.
Source string

contains

number

string(not

placeholder)

and missing

comments on

number

string.

Matches: 19

Placeholders
Scans for
If source has
Source: All
All

placeholders in the
placeholder and
items will be

source string and
placeholder not
deleted. Are

matching comments.
in comments.
you sure you

want to

empty {0}?

({1} item)

Comments:

Dev: Text to

be displayed

on Empty

Folder page

as user

prompt for

emptying a

folder with a

single email.

Message:

Source string

has

placeholder

which is not

referenced in

the

comments.

Matches:

{0}; {1};

Category: Resource Utilization

DuplicateSource
Searches for multiple
If source string
Source:
lcl,

Term
instances of the exact
for id X is the
Vendor Mail
lspkg,

same source string.
same as id Y (or
Message:
edb

any other).
String is

duplicate of

the following

strings in the

same

LocStudio

table:

[“STR”;

21159];

DupSourceAnd
Searches for multiple
If source string
Source:
lcl,

Target
instances for both the
and translation
Move to junk
lspkg,

exact same source
for id X is the
e-mail
edb

string and translation.
same as id Y (or
Translation:

any other).

custom-character

Message:

Source term

and target

string is

duplicate of

the following

strings in the

same

LocStudio

table:

[“STR”;

42593];

EmptyString
Finds where the
If source/target is
Source:
All

source or target
null and the other
server.

contains text but the
target/source is
Comment:

other does not.
not null.
null

LockedStrings
Flags strings that are
If Dev,
User Src
lcl,

marked as locked.
UserSource, or
Lock: Yes
lspkg,

UserTranslation
OR
edb

is locked.
Dev Src

Lock: Yes

OR

User Trans

Lock: Yes

NonTranslatable
Detects strings which
If source contains
Source: , or
All

Strings
are typically non-
non-translatable
_or . . . or +

translatable

or, or; or

SameTranslation
Looks for the same
If target string
Source:
lcl,

translation across
for id X is the
server
lspkg,

multiple strings.
same as the
(instance 1).
edb

string for id Y.
Source:

server

(instance 2)

Spaces
Detects spaces in the
If source has a
Source:
All

starting of a source
starting space.
Text (space

string.

before text)

UnusedStrings
Looks for null values
If source is null
Source: null
lcl,

for both source and
and target is null.
Target: null
lspkg,

target.

edb

Category: Localization

LocalizationForbiddenbyDev
Looks for comments
If comments
Source: Go
All

that indicate the
contain words
to space on

source string has
indicating
Vendor

localization
localization
Spaces

restrictions.
limits (such as do
Comment:

not').
RCCX: Do

not localize

‘Vendor’

MatchesPrevious
Identifies if the
If Source (or
Source:
lcl,

source or target
Target) matches
Server
lspkg,

match the previous
Previous and not
Target:
edb

translation.
each other.
Desktop

Previous:

Desktop

OverLocalized
Searches for terms in
If source contains a
Source:
All

a source string
NonLocalizedPattern
Vendor

matching a string
and target
Corporation

from
words appear
Target:

‘NonLocalizedPatterns.xml’.
translated.
*Mî¢røsøft

custom-character

õrpörãtîòñ*

PartlyNotLocalized
Looks for partial
If part of target
Source: Add
All

matches between
string matches a
to Messenger

source and target
word in the
Target:

strings.
source string.
Messenger

custom-character

TranslationOrNot
Looks for identical
If full source
Target
All

matches between the
matches full
Culture:

source and target
target string.
ZH-CHS

strings.

Source: beta

Target: beta

Category: Language Quality

NotLocalized
Detect non-localized
If TextLocStatus
Returns
lcl,

strings in source file.
! = Localized
strings where
lspkg,

TextLocStatus
edb

is

NotLocalized,

Updated

or

NotApplicable.

NotPreApproved
Detect non-
If
Returns
lcl,

preapproved strings
ApprovalStatus
strings were
lspkg,

in source file.
! = PreApproved
ApprovalStatus
edb

is

Approved,

NotReady,

Failed,

ForResearch,

NotApplicable,

Postponed,

Won't Fix

BinaryNotLocalized
Detect non-localized
If
Returns
lcl,

strings (using
BinaryLocStatus
resources
lspkg,

BinaryLocalizationStatus)
! = Localized
where
edb

in source file.

BinaryLocStatus

is

NotLocalized,

Updated

or

NotApplicable

BinaryToDO
Detect
If
Returns
lcl,

BinaryLocStatus and
BinaryLocSTatus
resources
lspkg,

Localization status
! = NotApplicable
where both
edb

are not applicable.
and
BinaryLocStatus

TextLocStatus ! =
and

Not Applicable
TextLocStatus

are both

not

applicable.

Category: Integrity

BrokenPlaceholder
Identifies broken or
If source contains
Source:
All

incorrect content of
placeholder and
Sorry, we

placeholders (such as
translation does
were unable

( ){ }[ ]<>%1%a) that
not.
to sign you

were detected in

in to

source.

{21151} at

this time.

Please try

again later.

Target:

custom-character

{10203}.

.

ExtraLineBreaker
Checks for additional
Target contains
Source:
All

line break (\n)
more line break
Line 1

characters in
characters than
Line 2

translation. It doesn't
source.
Line 3

check for ‘\n’ strings

Target:

(as MissLineBreaker

Line 1

does), but for

Line 2

additional

Line 3

<ENTER>s inserted

in the translation.

DuplicateHotkey
Detects duplicate
If the same
Source:
lcl,

hotkeys in the same
hotkey exists for
&Configure
lspkg,

space (source/target)
a string within
Message:
edb

and within the same
the same
Source string

namespace (menu,
namespace such
hotkey(&C)

dialog, and string).
as menu, dialog,
is duplicate

string.
to this source

in following

source ID:

[“WIN_DLG_CTRL_”,

130; 3522];

InconsistentNumbers
Checks if source and
Target contains
Source:
All

target contains the
more or less
1234

same number of
numbers than
Target: cat

numbers.
source.

LocalizedHTMLAttributes
Looks for translated
If Source Type =
ResourceID:
All

HTML attributes
HTML and
Attr

such as left, right,
Resource ID
SourceType:

and center.
contain Attr and
HTML

Target does not
Source:

match Source.
RIGHT

Target:

Desno

OverLocalizedFontNames
Check for over
If Source
Source:
All

localized font names
contains font
Some string

in the translation.
names (e.g.:
with font

Arial, Times
name: Arial

New Roman,
Target:

etc.) and Target

custom-character

doesn't contain

custom-character

one or more of

those names.

DuplicateSourceID
Identifies duplicate
If SourceID
SourceID:
All

SourceIDs in the
(instance 1)
1234

same resource file.
matches
(instance 1)

SourceID:
SourceID:

(instance 2+).
1234

(instance 2)

InconsistentShortCut
Detects if the source
If source (or
Source:
lcl,

or translation has a
target) contain a
Week (or
lspkg,

mismatched shortcut
shortcut and the
Ebaki
edb

(alt, del, ctrl, etc).
other does not
(Ktrl + X))

contain an
Target:

identical match.
Sedmica

Ctrl + Shift + 3

(or Auto)

MissHotkey
Identifies missing
If a hotkey (&)
Source:
lcl,

hotkeys (&) in either
exists in only the
&Search (or
lspkg,

the source or target.
source or target.
Save as)
edb

Target:

Cerca (or

custom-character

OverLocalizedHotkey
Looks for hotkeys
If Source
Source:
lcl,

that appear to be over
contains hotkey
&Unblock
lspkg,

localized by auto
and Target
Target:
edb

translation.
appears to

custom-character

contain
(&U)

additional hotkey

information.

MissLineBreaker
Identifies missing
If a
Source:
All

lineBreaker (\r\t\n) in
LineBreaker(\r\t\
\r\n\t

either the source or
n) exists in only
Target: \r\n

target.
the source or

target.

IdenticalToken
Looks for multiple
If a single token
Source: {0}
All

uses of the same
(like {0})
of {0}

token.
appears more
Comments:

than once.
Dev: like 11

of 11

Category: Punctuation

InconsistentPairing
Identifies some
Some
Source:
All

punctuation in target
punctuation
{Placeholder

or source string not
should in pair in
Target:

in pair, such as
some culture.
{Placeholder

( ){ }[ ].

{

UnEven
Identifies some
Some
Source: “” ‘
All

punctuation in source
punctuation
‘

string that is not
should be carried
Target: “” ’

translated properly.
over in some

cultures.

AppearanceInTranslation
Identifies some
Some
Source: Are
All

punctuation in source
punctuation
you Ok!

string should not
should not appear
Target:

appear in translation,
in translation in

custom-character

some culture.
Chinese

should not

use ‘?’,

should use

‘!’.)

LastPunctuationMismatch
Identifies miss match
Last punctuation
Source: Are
All

last punctuation
should match
you Ok?

between source and
between source
Target:

target string.
and target in

custom-character

some culture.

SpaceBeforePunctuation
Identifies whether
Space should not
Source: Are
All

some space before
before some
you Ok?

punctuation.
punctuation.
Target:

custom-character

AbsenseOfSpaceAfterPunctuation
Identifies some
Some
Source: Are
All

punctuation in target
punctuation
you Ok?

or source string not
should followed
Target:

have space followed.
by space in some

custom-character

culture.
(Last exists a

space.)

MoreThanOneContiguousSpaces
Identifies whether
More than one
Source: Are
All

there exists more
space should not
you Ok?

than one space in
appear in
Target: custom-character

target string.
translation.
(More than 1

space.)

ExtraPunctuation
Detects extra
Checks if Target
Source:
All

punctuation in the
String contains
Hello!

target string.
extra punctuation
Target:

when compared
Hello!!!!!

to the source

string.

Category: Advanced

LengthComparison
Looks for translated
If target is X
Source:
All

strings that are X
times longer than
Privacy

times longer (where
source string.
Target:

X can be set).

Beskyttelseaf

personligeoplysninger

StringLengthLimit
Determines if a
If target has more

All

localized string is
than X

greater than a
characters.

specified length.

SearchString
Looks for matches in
If string contains
Based on
All

a variety of locations
a match as
what you

(comments, sourceid,
inputted in
input in the

source, and target).
specified location
SearchOption

(comment, ID,
section of

source, or target).
the Rule tab

while

‘SearchString’

is selected

SpellingError
Looks for English
If source string
Source: Tst
lcl,

spelling errors
contains a mis-
Correction:
lspkg,

against the source
spelled English
Test
edb

string.
word.

CheckConformance
In some

resx

embodiments, this

check is a pre-

requisite for all the

rules. This rule has to

pass before any other

rules to run.

DeadResources
This rule checks for

resx,

references to the

rcxml

resources within an

application source

codes and lists all

resource IDs, which

don't appear in input

resx/rcxml files.

MissingEntry
Detect missing entry

resx,

between local and

rcxml

source resx files.

Category: Globalization

LocaleSensitive
Looks for strings
If source,
Source:
All

related to culture
sourceid, or
http://join.msn.com/?pgmarket=en-

such as LCID,
comments
us&amp;page=hotmail/options

LLCC, markets (en-
contain a string
Message:

us) or terms which
which is deemed
Source string

are locale sensitive.
locale sensitive.
references

culture

name: en-

US, culture:

English

(United

States).

LineBreaker
Looks for line
If source contains
Source: The
All

breakers (like \n\r)
a line breaker
selected

and for comments
and comments do
video could

associated with them.
not match it.
not be

accessed

from the

service\r\n

due to heavy

service

usage. Please

try again.

Comments:

null

FileName
Flags strings which
If source contains
Source:
lcl,

look like a filename
a filename or
oestyle.css
lspkg,

or filepath and
filepath and
Comments:
edb

missing comments.
comments do not
null

match string.

DateTimeForm
Scans source for
If source contains
Source: d
lcl,

Date Time style
Date Time
MMM, dddd
lspkg,

strings and for exact
format and
Comments:
edb

matching comments.
comments lack
RCCX:DS_NAVTREE_DAYFORMAT

matching string.

FindAllHotkey
Finds and lists all the
If source contains
Source:
Lcl,

hotkeys present in
a hotkey, list the
contains
lspkg,

the source file.
string.
hotkey
edb

denoted by

& or &

Having described rules that can be utilized in accordance with one more embodiments, consider now an example system that can be utilized to implement one or more embodiments.

Example System

FIG. 13 illustrates an example computing device 1300 that can be used to implement the various embodiments described above. Computing device 1300 can be, for example, computing device 102 and/or one or more of remote entities 126 of FIG. 1.

Computing device 1300 includes one or more processors or processing units 1302, one or more memory and/or storage components 1304, one or more input/output (I/O) devices 1306, and a bus 1308 that allows the various components and devices to communicate with one another. Bus 1308 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 1308 can include wired and/or wireless buses.

Memory/storage component 1304 represents one or more computer storage media. Component 1304 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Component 1304 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).

One or more input/output devices 1306 allow a user to enter commands and information to computing device 1300, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.

Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer-readable storage media”.

“Computer-readable storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

CONCLUSION

Various embodiments provide techniques for analyzing resources based on a set of rules to determine problems that may occur during a product development cycle. In accordance with some embodiments, resources can include files, strings, images, text, user interface elements (e.g. controls, radio buttons, and/or windows), and so on. For example, a resource for a software product can include a selectable control that is included as part of a graphical user interface for the software product.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

RESOURCE ANALYSIS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims