[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

US20090222787A1 - Repositories and related services for managing localization of resources - Google Patents

Repositories and related services for managing localization of resources Download PDF

Info

Publication number
US20090222787A1
US20090222787A1 US12/041,620 US4162008A US2009222787A1 US 20090222787 A1 US20090222787 A1 US 20090222787A1 US 4162008 A US4162008 A US 4162008A US 2009222787 A1 US2009222787 A1 US 2009222787A1
Authority
US
United States
Prior art keywords
resource
localized
representation
resources
localization
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US12/041,620
Other versions
US8595710B2 (en
Inventor
Ayman Aldahleh
Javier L. Larrinaga
Anatoliy Burukhin
Terry Farrell
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhigu Holdings Ltd
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to US12/041,620 priority Critical patent/US8595710B2/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FARRELL, TERRY, ALDAHLEH, AYMAN, BURUKHIN, ANATOLIY, LARRINAGA, JAVIER L.
Publication of US20090222787A1 publication Critical patent/US20090222787A1/en
Application granted granted Critical
Publication of US8595710B2 publication Critical patent/US8595710B2/en
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Assigned to ZHIGU HOLDINGS LIMITED reassignment ZHIGU HOLDINGS LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT TECHNOLOGY LICENSING, LLC
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • G06F9/454Multi-language systems; Localisation; Internationalisation

Definitions

  • These repositories may include representations of resources provided in first human languages, representations of software products that may incorporate these resources; and representations of other human languages into which the resources are localized.
  • the repositories may relate the resources to the software products and to the other human languages.
  • Methods provided by these tools may receive the resources as provided in the first human languages, send the resources for localization into other human languages, and receive localized resources.
  • the methods may convert the localized resources into binary representations, and build software products that incorporate the binary representations.
  • the tools may also provide systems that include processors, suitable bus systems, and computer-readable storage media that contains the resource repository.
  • FIG. 1 is a combined block and flow diagram illustrating systems or environments in which repositories and related services for managing localization of resources may operate.
  • FIG. 2 is a combined block and flow diagram illustrating components and process flows relating to the localization management service and related resource repository.
  • FIG. 3 is a combined block and flow diagram illustrating components and process flows by which localization vendors may localize the resources at build time.
  • FIG. 4 is a database diagram illustrating models or hierarchies for the resource repository.
  • FIG. 5 is a diagram illustrating processes and data flows for managing the localization of resources.
  • FIG. 6 is a diagram illustrating continuations of the process and data flows from FIG. 5 .
  • FIG. 7 is a diagram illustrating processes and data flows by which the localization tools may enable localization vendors to build products or applications for testing localized resources.
  • FIG. 1 illustrates systems or operating environments, denoted generally at 100 , in which repositories and related services for managing localization may operate. These systems 100 may include one or more server systems 102 , with FIG. 1 illustrates one server system 102 only for clarity of illustration. However, implementations of the description herein may include any number of server systems.
  • FIG. 1 shows examples in which the server system 102 is a centralized computing system, possibly shared by more than one client system.
  • the server systems 102 may also represent one or more desktop systems without departing from the scope and spirit of this description.
  • the description herein also contemplates other forms of server systems, including but not limited to, those shown in FIG. 1 .
  • the servers may include one or more processors 104 , which may have a particular type or architecture, chosen as appropriate for particular implementations.
  • the processors 104 may couple to one or more bus systems 106 chosen for compatibility with the processors 104 .
  • the servers 102 may also include one or more instances of computer-readable storage media 108 , which couple to the bus systems 106 .
  • the bus systems may enable the processors 104 to read code and/or data to/from the computer-readable storage media 108 .
  • the media 108 may represent storage elements implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like.
  • the media 108 may include memory components, whether classified as RAM, ROM, flash, or other types, and may also represent hard disk drives.
  • the storage media 108 may include one or more modules of software instructions that, when loaded into the processor 104 and executed, cause the server 102 to perform various techniques related to operating and/or maintaining the repositories and related services for managing localization. As detailed throughout this description, these servers 102 may manage the localization services using the components and flows now described in connection with FIG. 1 .
  • the computer-readable media 108 may include one or more applications or software products, denoted generally at 110 . These applications may incorporate or operate with various textual information, strings, or other label-type elements, referred to generally in this description as resources. Examples of these resources may include, but are not limited to, labels or strings appearing in various user interface (UI) elements, dialog boxes, error messages, or the like. The content of these resources may determine, for example, the content of error messages that are presented to users when the applications are running.
  • UI user interface
  • FIG. 1 illustrates different developers who may author the various resources used by the applications 110 .
  • FIG. 1 illustrates developers 112 a and 112 n (collectively, developers 112 ), who may respectively author resources 114 a and 114 n (collectively, resources 114 ) to be included in one or more of the applications.
  • the developer 112 a may author the resources 114 a primarily in the English language
  • the developer 114 n may author the resources 114 n primarily in the Japanese language.
  • the examples of languages as chosen herein are provided only for example, and do not limit possible implementations.
  • the two developers shown in FIG. 1 are illustrative only, and the operating environments 100 may support any number of developers.
  • the applications 110 may be made available to a variety of different users speaking a variety of different human languages.
  • the resources 114 are typically specific to particular human languages. More specifically, the resources 114 may be localized or translated, from the language in which they were originally authored to any number of destination or target human languages.
  • the computer-readable media 108 may include software modules 116 that, when executed by the processor 104 manages the localization of the resources 114 into localized resources 118 . Once the localized resources 118 are available, the applications 110 may incorporate these localized resources, as appropriate for any number of different human languages in which the applications are marketed.
  • the localization management service 116 may coordinate and administer efforts of a variety of different vendors to localize the resources into any number of target human languages.
  • FIG. 1 provides examples of localization vendors 120 a and 120 m (collectively, localization vendors 120 ).
  • the localization vendor 120 a localizes the resources into German
  • the localization vendor 120 m localizes the resources into Chinese.
  • the two localization vendors 120 are chosen only for example, and the operating environments 100 may support any number of localization vendors.
  • FIG. 1 also illustrates localization flows 122 a and 122 m (collectively, localization flows 122 ) associated respectively with the vendors 120 a and 120 m.
  • these localization flows 122 may represent requests to localize particular resources, the localized resources provided in response to those requests, as well as any related message or process flows related to these localizations.
  • the localization management service 116 may store these localized resources into a unified resource repository 124 .
  • the term “unified” may refer to a common format applicable to all resources stored in the repository 124 .
  • FIG. 1 denotes the localized resources as stored in this repository at 126 .
  • the localization management service 116 may also retrieve the localized resources 126 from the repository 124 as appropriate to build any number of localized applications 110 .
  • FIG. 1 illustrates examples in which the storage medium 108 contains the applications 110 , the localization management service 116 , and the resource repository 124 .
  • implementations of this description may store the applications, management service, and resource repository in the same or different media without departing from the scope and spirit of this description.
  • FIG. 2 Having described the overall covering environments or systems in FIG. 1 , the discussion now turns to a more detailed description of the localization management service and related resource repository. This description is now provided with FIG. 2 .
  • FIG. 2 illustrates components and process flows, denoted generally at 200 , that provide additional details on the operations of the localization management service and related resource repository.
  • FIG. 2 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers.
  • FIG. 2 carries forward an example localization management service at 116 and an example resource repository at 124 .
  • the localization management service 116 may include a preliminary translation module 202 that operates to receive resources (e.g., carried forward as resources 114 a ) authored initially in a given language (e.g., English). The translation module may then preliminarily or initially localize these resources into any number of target languages.
  • This preliminary localization may represent a “first cut” at localizing the given resource, for purposes of testing or verifying the operation of applications that may include a localized resource. More specifically, these preliminary localizations may enable the localization management service to test the applications at build time using the preliminary localizations, rather than later at runtime. This initial testing may take the form of operational dry runs or other forms of preliminary testing.
  • resource strings may have been previously localized, and are thus available for reuse or recycling.
  • the preliminary translation module 202 may use machine or automated translation to preliminarily or initially localize the input resource. Even though such machine or automated translations may not be perfectly accurate, they may still represent a suitable starting point for the localization process, and may provide a sufficient basis for preliminary testing.
  • the preliminary translation module may use random code points, which provide a type mapping between different languages.
  • the preliminary translation module 202 may localize the English resource 114 a into Chinese (e.g., 114 b ), German (e.g., 114 m ), or other suitable languages.
  • a binary conversion module 204 may receive the English resource 114 a, and any preliminarily localized resources (e.g., 114 b and 114 m ) as input. The module 204 may convert these resources, expressed in any suitable unified format across a plurality of different applications, into compressed, binary representations of converted resources.
  • converted resources 206 may be localized, in the sense that the example resource 206 a may be in English, the example resource 206 b may be in Chinese, and the example resource 206 m may be in German.
  • the converted resources 206 may be .dll (dynamically linked library) files. However, it is noted that implementations of this description may use other examples of converted representations.
  • a resource manager 208 may receive and store the various converted resources 206 .
  • various applications may request the converted resources 206 (e.g., .dll files) from the resource manager 208 .
  • the various converted resources 206 may be associated with corresponding unique identifiers 210 , enabling the applications to request particular converted resources using the unique identifiers.
  • FIG. 2 provides an example in which an application 110 a requests the converted resource 206 a using a first identifier 210 a associated with the resource 206 a, and in which a second application 110 m requests the converted resource 206 m using a second identifier 210 m associated with the resource 206 m.
  • FIG. 2 denotes at 212 a the converted resource as provided to the application 110 a, and denotes at 212 m the converted resource as provided to the application 110 m.
  • FIG. 3 illustrates components and process flows, denoted generally at 300 , by which localization vendors may localize the resources at build time.
  • FIG. 3 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers.
  • FIG. 3 carries forward an example localization management service at 116 and an example resource repository at 124 .
  • FIG. 3 also carries forward the example English-language resource 114 a, as well as the example Chinese-language and German-language resources 114 b and 114 m, as preliminarily localized by the localization module 202 .
  • a localization vendor may obtain the initially-localized German-language resource 114 m, as shown in FIG. 2 , and more completely localize this resource.
  • the localization vendor 120 a may review the preliminary localization, and adjust or correct it as appropriate.
  • FIG. 3 denotes these localization flows generally at 122 a, resulting in an updated and finally-localized German-language resource 302 m.
  • an example Chinese-language localization vendor 120 m may obtain and perform final localization on the initially-localized Chinese-language resource 114 b, resulting in the finally-localized resource 302 b.
  • These localization flows are denoted generally at 122 m.
  • FIG. 3 carries forward the binary converter 204 , which as described above may convert the English-language resource 114 a into a converted resource 206 a.
  • the binary converter may process the finally-localized Chinese-language and German-language resources 114 b and 114 m, resulting in updated versions of the converted resources 212 a and 212 m, which were shown in FIG. 2 .
  • FIG. 3 denotes these updated resources at 304 b and 304 m.
  • the resources 304 b and 304 m may be updated to incorporate final localizations made by the vendors 120 a and 120 m.
  • the resource manager 208 may make these of resources 206 a, 304 b, and 304 m available on request to various applications (e.g., 110 in FIGS. 1 and 2 ).
  • the localization management service enables the localization vendors to localize resources before they are converted into binaries that are built into applications, rather than after they are built into applications. In this manner, the localization management service enables resource authoring and development to proceed in parallel in several different languages.
  • FIG. 4 illustrates models or hierarchies, denoted generally at 400 , for the resource repository. To facilitate description, but not to limit possible implementations, FIG. 4 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 4 carries forward an example localization management service at 116 and an example resource repository at 124 .
  • the resource repository 124 may be implemented using a database model and related data structures, represented generally at 402 .
  • This model may arrange or organize along a first axis 404 representations of applications or software products (e.g., 110 in FIGS. 1 and 2 ).
  • This model may also arrange or organize along a second axis 406 representations of resources available for these applications, and may arrange or organize along a third axis 408 representations of languages available for these applications and/or resources.
  • the database model 402 may conceptually provide a type of three-dimensional hierarchical scheme that relates or links the representations of the products, languages, and resources to one another.
  • a given product may include one or more resources that are localized in a first given language.
  • a second given product may include one or more resources that are localized in a second given language.
  • the database model 402 may be generalized to incorporate and organize representations of any number of products, languages, and resources, with the example shown in FIG. 4 being illustrative rather than limiting.
  • a representation of a given application or software product 404 a may be associated with representations of one or more localizable resources 406 a, which may be associated with globally unique identifiers (GUIDs) (e.g., 210 ) as discussed above in FIG. 2 . More specifically, the localizable resources may be associated with respective GUIDs, regardless of where these resources lie in the three-dimensional hierarchy shown in FIG. 4 . In this manner, the hierarchy may enable external interfaces or tools to address and retrieve resources individually and uniquely, regardless of the language into which the resources are localized, and regardless of which products incorporate these resources.
  • GUIDs globally unique identifiers
  • the resources 406 a may be localized into one or more additional human languages, with two example representations provided at 408 a and 408 n.
  • a representation of the localized resource 408 a may be associated with a corresponding converted or binary representation of the resource, carried forward at 206 a.
  • a representation of the localized resource 408 n may be associated with a corresponding light binary 206 n.
  • these hierarchies may establish any number of different relationships between the products, resources, and/or languages for localizing resources for incorporation into different products. For example, a given resource may be incorporated into a variety of different products or applications, and the resource may be localized into any number of different target human languages.
  • the localization management service 116 may cooperate with the resource repository 124 to define a set of tools or interfaces that enable a variety of different entities to interact with the resource repository.
  • the localization management service 116 may provide a developer interface 414 that exposes a set of tools 416 to development personnel (e.g., 112 and FIG. 1 ). These tools may enable developers to author resources (e.g., text strings) in a variety of different languages. These development tools may also store the resources appropriately within the data base model.
  • a localization interface 418 may expose a set of localization tools 420 to, for example, one or more localization vendors (e.g., 120 in FIG. 1 ). As described elsewhere herein, different vendors may localize resources into different languages. Accordingly, the localization tools 420 may expose different “slices” of the database model 402 to different localization vendors, depending on the languages in which the vendors operate. FIG. 4 provides an example of such a slice at 422 , which may represent German-language products and resources that are provided to a localization vendor operating in German.
  • the localization tools 420 may provide for converting formats, as appropriate, between those used to implement the resource repository 124 and those used internally by localization vendors. In some instances, however, the localization tools 420 may enable the localization vendors to access the resource repository directly, without converting formats. In this manner, the localization tools may provide an online service by which the vendors may directly localize the resources in the repository.
  • a software build interface 424 may expose a set of software build tools 426 to, for example, produce or build software products. More specifically, these software build tools may enable a build lab to produce a given software product that incorporates a set of resources that are localized to a particular language.
  • FIG. 4 provides examples, denoted at 410 and 412 , that illustrate relationships between a given product, the particular resources included in that product, and the languages for which the resources are localized.
  • a process for building particular product may be visualized as “drilling” through the two-dimensional plane formed by the product axis 404 and the language axis 408 in parallel with the resource axis 406 .
  • the build process may “drill” into the appropriate point in the product-language plane, depending on the target product and the target language.
  • the build process may incorporate the appropriate resources for building a product, with these resources localized into the target language appropriate for the product.
  • the various elements stored in the resource repository may be implemented in XML.
  • the software build tools 426 may include binary converters (e.g., 204 in FIG. 2 ) to convert these elements into, for example, .dll files or other equivalent representations.
  • a management interface 428 may expose a set of management tools 430 to, for example, program managers involved with particular products and/or resources. These management tools 430 may enable the program managers to view a set of resources across one or more particular products. In this manner, the management tools 430 may enable the program managers to identify any redundancy or duplication appearing in different resources in different products. For example, a given error message may appear in slightly different forms in two or more different products. The management tools 430 may enable a program manager to identify the slightly different forms for this error message, resolve any inconsistencies in this message across the different products, and update the resource for this error message accordingly.
  • the localization management service 116 and the resource repository 124 may cooperate to manage the database model 402 as operations proceed over time.
  • resource developers may continually provide new text strings through the developer interface 414 and related development tools 416 .
  • the localization management service may preliminarily translate or localize these new strings into any number of target languages.
  • FIGS. 2 and 3 provide examples of preliminary localization modules at 202 .
  • preliminary or initial localizations of the new text string may propagate through the database model 402 along the language axis 408 .
  • the localization interface 418 and related tools 420 may expose these preliminary localizations to the appropriate vendors who operate in those different languages. As described above, these vendors may review these preliminary localizations, and finalize as appropriate.
  • the various elements stored in the resource repository may be implemented in XML.
  • the software build tools 426 may include binary converters (e.g., 204 in FIG. 2 ) to convert these elements into, for example, .dll files or other equivalent representations.
  • the software build tools 426 and the localization tools 420 may cooperate, to enable localization vendors to build software products that incorporate resources that were finally-localized by the vendors. More specifically, the localization vendors may be able to generate .dll files for the localized resources, link these .dll files into built products, and run the products to view the results of the localization. In this manner, the localization vendors may test and verify their localizations, as well as testing the operation of the built product when operating with the localized resources.
  • FIG. 4 provides various examples of interfaces or tools to facilitate this description. However, these examples of interfaces or tools are non-limiting, and implementations of this description may provide other interfaces or tools as well.
  • the product builds, as presented to the localization vendors may enable the vendors to hover a user interface device (e.g., a mouse pointer) over a particular non-localized string, or over a preliminarily-localized string appearing within the running product.
  • the localization tools 420 may present a suitable user interface, responsive to input from vendor personnel to finally localize the string. Once the string is localized finally, the localization tools 420 may propagate the localized resource back to the resource repository.
  • finalized and shipped product builds may be presented to end-users, along with suitable tools enabling these end-users to localize or translate UI resources presented when these product builds are executed.
  • end-user localization tools may enable the end-users to access the resource repository, whether sent or shipped with the product build directly to the end-users, or whether the end-users are given some mechanisms for accessing the repository.
  • Such mechanisms may include web services by which the users may access the repository, with the repository not being physically shipped or sent with the build product.
  • the repository may be provided in a “binary” form, and in these scenarios, conversion to binary may be optional in a sense. given access to the repository, the end-users may perform a form of “do it yourself” runtime localization on their own build of the product.
  • Enabling the end-users to access the resource repository may enable uses other than run-time localization. For example, end users may look up resources at run time, if they have access to the resource repository. As described elsewhere herein, most resource loads may be based on knowing the unique identifier associated with a particular resource, and loading the resource based on this identifier. However, in some cases identifier-based lookups may fail, for example, if a given resource with a given unique identifier is not yet been translated or localized. In this case, the resource repository could provide a string-based lookup mechanism to locate the resource, in addition to identifier-based lookups.
  • the database model 402 and related services and tools may readily be extended to handle not only languages, but also language dialects spoken within particular regions or communities.
  • the localization tools 420 may enable dialect localizers (who may or may not be localization vendors) who speak a particular dialect to add layers to the database model 402 . These additional layers may localize resources from broader languages to particular dialects. Samples of these dialects may include, but are not limited to, the various dialects spoken in China, Native American languages, or the like.
  • these layers added to the database model may be isolated from the rest of the database model, thereby enabling these dialect localizers to operate within these additional layers without affecting or impacting the rest of the database model.
  • the rest of the database model may be designated as “read-only” to these dialect localizers.
  • FIG. 5 illustrates process and data flows, denoted generally at 500 , for managing the localization of resources.
  • FIG. 5 may carry forward some elements from previous figures, and denote them with identical reference numbers.
  • FIG. 5 carries forward examples of development tools at 414 , examples of a localization management service (e.g., 116 ) cooperating with a resource repository (e.g., 124 ), and examples of localization tools at 418 .
  • a localization management service e.g., 116
  • resource repository e.g., 124
  • FIG. 5 arranges certain processes and data flows in columns, corresponding to illustrative entities that may perform such processes and data flows, only for the purposes of this description. However, it is noted that these arrangements are provided for example only, and not to limit possible implementations. More specifically, entities other than those shown in FIG. 5 may perform some or all of these processes or data flows.
  • block 502 represents sending a resource authored in a first given language.
  • block 502 may include the development tools 414 providing text strings authored by development personnel (e.g., 112 in FIG. 1 ).
  • FIG. 5 denotes these authored resources at 504 , which collectively represents the various resources shown in FIG. 1 (e.g., 114 a and 114 n ).
  • Block 506 represents receiving the authored resource in a first language.
  • block 506 may include the localization management service receiving the resource.
  • Block 508 generally represents preliminarily localizing the resource received in block 506 .
  • the preliminary localization module 202 shown in FIG. 2 , may perform block 508 .
  • Block 510 may convert the preliminary localizations to a binary form (e.g., .dll files).
  • block 512 represents sending the resource for final localization.
  • block 512 may include sending the resources to one or more appropriate localization vendors, via the localization tools 418 .
  • FIG. 5 denotes at 514 the resources as sent for localization.
  • block 512 may include providing the input resource 514 to the localization vendor before the resource is compiled into a binary form.
  • the localization vendor may translate the resource before it is incorporated into a built, executable product. Accordingly, the localization vendor and related services are moved upstream in the software development process, as compared to previous techniques.
  • block 512 may include sending the input resource 514 to multiple localization vendors, to be localized into multiple different target languages.
  • FIG. 5 illustrates one instance of localization tools only for clarity of illustration.
  • block 516 generally represents receiving the resource for localization.
  • block 516 may include receiving resources that are preliminarily localized, or may include receiving resources that are non-localized.
  • Block 518 represents localizing the input resource 514 .
  • multiple different localization vendors may respectively perform block 518 on a given input resource, to localize the input resource into several different target languages.
  • Block 518 may include performing a final localization on the input resource.
  • Block 520 represents the localization tools returning the localized resource to the localization management service.
  • FIG. 5 denotes the localized resource at 522 .
  • a plurality of different localization tools 418 may provide different instances of the resources 522 , localized for different target languages.
  • Block 524 represents receiving one or more instances of resources 522 , localized for one or more target languages. Afterwards, block 510 may convert the localized resources into binary form (e.g., .dll files). In instances where resources are initially or preliminarily localized and then converted to binary, block 510 may include updating the binary representation of such resources, after these resources have been finally localized.
  • binary form e.g., .dll files
  • FIG. 6 illustrates continuations, denoted generally at 600 , of the process and data flows from FIG. 5 .
  • FIG. 6 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers.
  • FIG. 6 carries forward an example localization management service at 116 , an example resource repository at 124 , and example software build tools at 426 .
  • block 604 generally represents loading a resource 606 into the repository.
  • the resource 606 loaded into the repository may be non-localized, preliminarily localized, or finally localized.
  • block 608 generally represents requesting one or more resources for building a given software product or application, localized for a particular target language.
  • These resources may be converted or binary resources (e.g., .dll files), and the requests may reference unique identifiers associated with these converted resources (e.g., 210 in FIG. 2 ).
  • FIG. 6 denotes such requests for localized resources at 610 .
  • block 612 generally represents receiving the request for localized resources.
  • Block 612 may also include querying the resource repository with any identifiers associated with the requested resource, as denoted generally at 614 .
  • block 618 generally represents returning the localized resources.
  • FIG. 6 denotes the returned localized resources generally at 620 .
  • block 622 generally represents receiving the localized resources in response to the request 610 .
  • block 624 generally represents building the application, incorporating the localized resources 620 , as built into and obtained from the resource repository 124 .
  • the resource repository provides the ability to build and/or generate for any human language for which resources are available dynamically. In the scenarios described herein, the English language is treated as just another language, in contrast to previous approaches in which development occurred initially and primarily in English, with other languages being localized after-the-fact.
  • the resource manager e.g., 208 in FIG. 2
  • FIG. 7 illustrates processes and data flows, denoted generally at 700 , by which the localization tools may enable localization vendors to build products or applications for testing localized resources.
  • FIG. 7 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers.
  • FIG. 7 carries forward an example localization management service at 116 , an example resource repository at 124 , and example localization tools at 418 .
  • block 702 represents providing a resource 704 from the resource repository 124 .
  • the localization management service 116 may perform block 702 .
  • this resource may have been non-localized, or in some cases preliminarily-localized.
  • FIG. 7 denotes the resource at 706 .
  • block 708 generally represents receiving the resource (whether non-localized, or localized preliminarily) from the localization management service.
  • block 710 represents finally localizing the resource, as may be performed by a localization vendor using the localization tools 418 .
  • Block 712 represents building a software product to incorporate the localized resource.
  • Block 712 may include converting the localized resource into appropriate binary form (e.g., .dll files) for incorporation or linking into the software product.
  • the localization tools 418 may include a binary converter (e.g., 204 in FIG. 2 ) for performing this conversion.
  • Block 714 generally represents executing the software product built in block 712 to test the localized resource is incorporated into that software product. Put differently, block 714 may include testing whether the software product executes appropriately with the localized resource, as represented in decision block 716 .
  • block 710 may include applying a different localization to the resource, and repeating blocks 712 , 714 , and 716 with the newly-localized resource. In this manner, the process flows 700 may loop through block 716 , 710 , 712 , and 714 until the software executes appropriately with the localized resource.
  • Block 722 generally represents returning the localized resource, denoted at 724 , to the localization management service.
  • block 726 represents receiving the localized resource 724 .
  • block 728 represents loading the localized resource (denoted at 730 ) into the resource repository 124 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

Tools and techniques for repositories and related services for managing localization of resources are described herein. These repositories may include representations of resources provided in first human languages, representations of software products that may incorporate these resources; and representations of other human languages into which the resources are localized. The repositories may relate the resources to the software products and to the other human languages. Methods provided by these tools may receive the resources as provided in the first human languages, send the resources for localization into other human languages, and receive localized resources. The methods may convert the localized resources into binary representations, and build software products that incorporate the binary representations. The tools may also provide systems that include processors, suitable bus systems, and computer-readable storage media that contains the resource repository.

Description

    BACKGROUND
  • Software companies are increasing efforts to reach a variety of markets around the globe. In these different markets, users may speak a variety of different languages, and software products marketed to those users are typically localized to particular languages. In previous approaches, software was typically developed and released in a first language (e.g., English), and then localized as appropriate for different global markets.
  • SUMMARY
  • Tools and techniques for repositories and related services for managing localization of resources are described herein. These repositories may include representations of resources provided in first human languages, representations of software products that may incorporate these resources; and representations of other human languages into which the resources are localized. The repositories may relate the resources to the software products and to the other human languages. Methods provided by these tools may receive the resources as provided in the first human languages, send the resources for localization into other human languages, and receive localized resources. The methods may convert the localized resources into binary representations, and build software products that incorporate the binary representations. The tools may also provide systems that include processors, suitable bus systems, and computer-readable storage media that contains the resource repository.
  • The above-described subject matter may also be implemented as a method, computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
  • 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 that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a combined block and flow diagram illustrating systems or environments in which repositories and related services for managing localization of resources may operate.
  • FIG. 2 is a combined block and flow diagram illustrating components and process flows relating to the localization management service and related resource repository.
  • FIG. 3 is a combined block and flow diagram illustrating components and process flows by which localization vendors may localize the resources at build time.
  • FIG. 4 is a database diagram illustrating models or hierarchies for the resource repository.
  • FIG. 5 is a diagram illustrating processes and data flows for managing the localization of resources.
  • FIG. 6 is a diagram illustrating continuations of the process and data flows from FIG. 5.
  • FIG. 7 is a diagram illustrating processes and data flows by which the localization tools may enable localization vendors to build products or applications for testing localized resources.
  • DETAILED DESCRIPTION
  • The following detailed description is directed to technologies for repositories and related services for managing localization. While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
  • In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of tools and techniques for repositories and related services for managing localization will be described.
  • FIG. 1 illustrates systems or operating environments, denoted generally at 100, in which repositories and related services for managing localization may operate. These systems 100 may include one or more server systems 102, with FIG. 1 illustrates one server system 102 only for clarity of illustration. However, implementations of the description herein may include any number of server systems.
  • The graphical elements used in FIG. 1 to depict the server systems are chosen only to facilitate illustration, and not to limit possible implementations of the description herein. More particularly, FIG. 1 shows examples in which the server system 102 is a centralized computing system, possibly shared by more than one client system. However, the server systems 102 may also represent one or more desktop systems without departing from the scope and spirit of this description. Thus, the description herein also contemplates other forms of server systems, including but not limited to, those shown in FIG. 1.
  • Turning to the servers 102 in more detail, the servers may include one or more processors 104, which may have a particular type or architecture, chosen as appropriate for particular implementations. The processors 104 may couple to one or more bus systems 106 chosen for compatibility with the processors 104.
  • The servers 102 may also include one or more instances of computer-readable storage media 108, which couple to the bus systems 106. The bus systems may enable the processors 104 to read code and/or data to/from the computer-readable storage media 108. The media 108 may represent storage elements implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like. The media 108 may include memory components, whether classified as RAM, ROM, flash, or other types, and may also represent hard disk drives.
  • The storage media 108 may include one or more modules of software instructions that, when loaded into the processor 104 and executed, cause the server 102 to perform various techniques related to operating and/or maintaining the repositories and related services for managing localization. As detailed throughout this description, these servers 102 may manage the localization services using the components and flows now described in connection with FIG. 1.
  • The computer-readable media 108 may include one or more applications or software products, denoted generally at 110. These applications may incorporate or operate with various textual information, strings, or other label-type elements, referred to generally in this description as resources. Examples of these resources may include, but are not limited to, labels or strings appearing in various user interface (UI) elements, dialog boxes, error messages, or the like. The content of these resources may determine, for example, the content of error messages that are presented to users when the applications are running.
  • FIG. 1 illustrates different developers who may author the various resources used by the applications 110. FIG. 1 illustrates developers 112 a and 112 n (collectively, developers 112), who may respectively author resources 114 a and 114 n (collectively, resources 114) to be included in one or more of the applications. For example only, the developer 112 a may author the resources 114 a primarily in the English language, while the developer 114 n may author the resources 114 n primarily in the Japanese language. The examples of languages as chosen herein are provided only for example, and do not limit possible implementations. In addition, the two developers shown in FIG. 1 are illustrative only, and the operating environments 100 may support any number of developers.
  • The applications 110 may be made available to a variety of different users speaking a variety of different human languages. As appreciated from the foregoing, the resources 114 are typically specific to particular human languages. More specifically, the resources 114 may be localized or translated, from the language in which they were originally authored to any number of destination or target human languages. The computer-readable media 108 may include software modules 116 that, when executed by the processor 104 manages the localization of the resources 114 into localized resources 118. Once the localized resources 118 are available, the applications 110 may incorporate these localized resources, as appropriate for any number of different human languages in which the applications are marketed.
  • The localization management service 116 may coordinate and administer efforts of a variety of different vendors to localize the resources into any number of target human languages. FIG. 1 provides examples of localization vendors 120 a and 120 m (collectively, localization vendors 120). In the non-limiting examples shown in FIG. 1, the localization vendor 120 a localizes the resources into German, and the localization vendor 120 m localizes the resources into Chinese. The two localization vendors 120 are chosen only for example, and the operating environments 100 may support any number of localization vendors.
  • FIG. 1 also illustrates localization flows 122 a and 122 m (collectively, localization flows 122) associated respectively with the vendors 120 a and 120 m. Generally, these localization flows 122 may represent requests to localize particular resources, the localized resources provided in response to those requests, as well as any related message or process flows related to these localizations.
  • Once the localized resources 118 are available from the various vendors 120, the localization management service 116 may store these localized resources into a unified resource repository 124. The term “unified” may refer to a common format applicable to all resources stored in the repository 124. FIG. 1 denotes the localized resources as stored in this repository at 126. The localization management service 116 may also retrieve the localized resources 126 from the repository 124 as appropriate to build any number of localized applications 110.
  • Only for clarity of illustration and description, but not to limit possible implementations, FIG. 1 illustrates examples in which the storage medium 108 contains the applications 110, the localization management service 116, and the resource repository 124. However, implementations of this description may store the applications, management service, and resource repository in the same or different media without departing from the scope and spirit of this description.
  • Having described the overall covering environments or systems in FIG. 1, the discussion now turns to a more detailed description of the localization management service and related resource repository. This description is now provided with FIG. 2.
  • FIG. 2 illustrates components and process flows, denoted generally at 200, that provide additional details on the operations of the localization management service and related resource repository. To facilitate description, but not to limit possible implementations, FIG. 2 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 2 carries forward an example localization management service at 116 and an example resource repository at 124.
  • Turning to FIG. 2 in more detail, the localization management service 116 may include a preliminary translation module 202 that operates to receive resources (e.g., carried forward as resources 114 a) authored initially in a given language (e.g., English). The translation module may then preliminarily or initially localize these resources into any number of target languages. This preliminary localization may represent a “first cut” at localizing the given resource, for purposes of testing or verifying the operation of applications that may include a localized resource. More specifically, these preliminary localizations may enable the localization management service to test the applications at build time using the preliminary localizations, rather than later at runtime. This initial testing may take the form of operational dry runs or other forms of preliminary testing.
  • As examples of these preliminary localizations, in some cases resource strings may have been previously localized, and are thus available for reuse or recycling. In another example, the preliminary translation module 202 may use machine or automated translation to preliminarily or initially localize the input resource. Even though such machine or automated translations may not be perfectly accurate, they may still represent a suitable starting point for the localization process, and may provide a sufficient basis for preliminary testing. In yet another example, the preliminary translation module may use random code points, which provide a type mapping between different languages.
  • In the example shown in FIG. 2, the preliminary translation module 202 may localize the English resource 114 a into Chinese (e.g., 114 b), German (e.g., 114 m), or other suitable languages. In turn, a binary conversion module 204 may receive the English resource 114 a, and any preliminarily localized resources (e.g., 114 b and 114 m) as input. The module 204 may convert these resources, expressed in any suitable unified format across a plurality of different applications, into compressed, binary representations of converted resources. FIG. 2 illustrates examples in which the resources 114 a, 114 b, and 114 m are converted into respective resources 206 a, 206 b, and 206 m (collectively, converted resources 206). These converted resources 206 may be localized, in the sense that the example resource 206 a may be in English, the example resource 206 b may be in Chinese, and the example resource 206 m may be in German.
  • In example implementations, the converted resources 206 may be .dll (dynamically linked library) files. However, it is noted that implementations of this description may use other examples of converted representations.
  • A resource manager 208 may receive and store the various converted resources 206. In the example shown in FIG. 2, various applications may request the converted resources 206 (e.g., .dll files) from the resource manager 208. For example, the various converted resources 206 may be associated with corresponding unique identifiers 210, enabling the applications to request particular converted resources using the unique identifiers. FIG. 2 provides an example in which an application 110 a requests the converted resource 206 a using a first identifier 210 a associated with the resource 206 a, and in which a second application 110 m requests the converted resource 206 m using a second identifier 210 m associated with the resource 206 m. FIG. 2 denotes at 212 a the converted resource as provided to the application 110 a, and denotes at 212 m the converted resource as provided to the application 110 m.
  • Having described in FIG. 2 components and flows for preliminary localization of resources, the discussion now turns to a description of components and flows by which localization vendors may localize the resources at build time. This discussion is now presented with FIG. 3.
  • FIG. 3 illustrates components and process flows, denoted generally at 300, by which localization vendors may localize the resources at build time. To facilitate description, but not to limit possible implementations, FIG. 3 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 3 carries forward an example localization management service at 116 and an example resource repository at 124. FIG. 3 also carries forward the example English-language resource 114 a, as well as the example Chinese-language and German-language resources 114 b and 114 m, as preliminarily localized by the localization module 202.
  • Turning to FIG. 3 in more detail, a localization vendor (e.g., 120 a) may obtain the initially-localized German-language resource 114 m, as shown in FIG. 2, and more completely localize this resource. For example, the localization vendor 120 a may review the preliminary localization, and adjust or correct it as appropriate. FIG. 3 denotes these localization flows generally at 122 a, resulting in an updated and finally-localized German-language resource 302 m. In a similar manner, an example Chinese-language localization vendor 120 m may obtain and perform final localization on the initially-localized Chinese-language resource 114 b, resulting in the finally-localized resource 302 b. These localization flows are denoted generally at 122 m.
  • FIG. 3 carries forward the binary converter 204, which as described above may convert the English-language resource 114 a into a converted resource 206 a. In addition, the binary converter may process the finally-localized Chinese-language and German-language resources 114 b and 114 m, resulting in updated versions of the converted resources 212 a and 212 m, which were shown in FIG. 2. FIG. 3 denotes these updated resources at 304 b and 304 m.
  • Continuing the example described above in FIG. 2, in which the converted resources 206 are .dll files, the resources 304 b and 304 m may be updated to incorporate final localizations made by the vendors 120 a and 120 m. In turn, the resource manager 208 may make these of resources 206 a, 304 b, and 304 m available on request to various applications (e.g., 110 in FIGS. 1 and 2).
  • Having described the above components and flows in FIGS. 2 and 3, several observations are noted. The localization management service enables the localization vendors to localize resources before they are converted into binaries that are built into applications, rather than after they are built into applications. In this manner, the localization management service enables resource authoring and development to proceed in parallel in several different languages. In addition, applications and/or products that are localized for a variety of different languages and may be built in parallel using the tools and techniques described herein. For example, converted binary resources authored originally in English (e.g., 206 a) may be made available to the resource manager 208 when the applications are built, generally in parallel with the corresponding localized resources (e.g., 304 b and 304 m).
  • Having described the components and flows and FIG. 3, the discussion now proceeds to a description of a model or hierarchy for the resource repository. This discussion is now presented with FIG. 4.
  • FIG. 4 illustrates models or hierarchies, denoted generally at 400, for the resource repository. To facilitate description, but not to limit possible implementations, FIG. 4 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 4 carries forward an example localization management service at 116 and an example resource repository at 124.
  • Turning to FIG. 4 in more detail, the resource repository 124 may be implemented using a database model and related data structures, represented generally at 402. This model may arrange or organize along a first axis 404 representations of applications or software products (e.g., 110 in FIGS. 1 and 2). This model may also arrange or organize along a second axis 406 representations of resources available for these applications, and may arrange or organize along a third axis 408 representations of languages available for these applications and/or resources. In this manner, the database model 402 may conceptually provide a type of three-dimensional hierarchical scheme that relates or links the representations of the products, languages, and resources to one another. For example, as represented generally at 410, a given product may include one or more resources that are localized in a first given language. As represented generally at 412, a second given product may include one or more resources that are localized in a second given language. It is noted that the database model 402 may be generalized to incorporate and organize representations of any number of products, languages, and resources, with the example shown in FIG. 4 being illustrative rather than limiting.
  • In an example hierarchy shown in FIG. 4, elaborating further on the relationships noted at 410, a representation of a given application or software product 404 a may be associated with representations of one or more localizable resources 406 a, which may be associated with globally unique identifiers (GUIDs) (e.g., 210) as discussed above in FIG. 2. More specifically, the localizable resources may be associated with respective GUIDs, regardless of where these resources lie in the three-dimensional hierarchy shown in FIG. 4. In this manner, the hierarchy may enable external interfaces or tools to address and retrieve resources individually and uniquely, regardless of the language into which the resources are localized, and regardless of which products incorporate these resources. In turn, the resources 406 a may be localized into one or more additional human languages, with two example representations provided at 408 a and 408 n. Finally, a representation of the localized resource 408 a may be associated with a corresponding converted or binary representation of the resource, carried forward at 206 a. Similarly, a representation of the localized resource 408 n may be associated with a corresponding light binary 206 n.
  • In elaborating on the relationships shown at 410, it is noted that such relationships may be extended across any number of software products or applications. Further, these hierarchies may establish any number of different relationships between the products, resources, and/or languages for localizing resources for incorporation into different products. For example, a given resource may be incorporated into a variety of different products or applications, and the resource may be localized into any number of different target human languages.
  • The localization management service 116 may cooperate with the resource repository 124 to define a set of tools or interfaces that enable a variety of different entities to interact with the resource repository. For example, the localization management service 116 may provide a developer interface 414 that exposes a set of tools 416 to development personnel (e.g., 112 and FIG. 1). These tools may enable developers to author resources (e.g., text strings) in a variety of different languages. These development tools may also store the resources appropriately within the data base model.
  • A localization interface 418 may expose a set of localization tools 420 to, for example, one or more localization vendors (e.g., 120 in FIG. 1). As described elsewhere herein, different vendors may localize resources into different languages. Accordingly, the localization tools 420 may expose different “slices” of the database model 402 to different localization vendors, depending on the languages in which the vendors operate. FIG. 4 provides an example of such a slice at 422, which may represent German-language products and resources that are provided to a localization vendor operating in German.
  • The localization tools 420 may provide for converting formats, as appropriate, between those used to implement the resource repository 124 and those used internally by localization vendors. In some instances, however, the localization tools 420 may enable the localization vendors to access the resource repository directly, without converting formats. In this manner, the localization tools may provide an online service by which the vendors may directly localize the resources in the repository.
  • A software build interface 424 may expose a set of software build tools 426 to, for example, produce or build software products. More specifically, these software build tools may enable a build lab to produce a given software product that incorporates a set of resources that are localized to a particular language. FIG. 4 provides examples, denoted at 410 and 412, that illustrate relationships between a given product, the particular resources included in that product, and the languages for which the resources are localized.
  • In the example database model 402, a process for building particular product may be visualized as “drilling” through the two-dimensional plane formed by the product axis 404 and the language axis 408 in parallel with the resource axis 406. In this visual example, the build process may “drill” into the appropriate point in the product-language plane, depending on the target product and the target language. As the build process proceeds or “drills” along the resource axis 406, the build process may incorporate the appropriate resources for building a product, with these resources localized into the target language appropriate for the product.
  • In example implementations, the various elements stored in the resource repository may be implemented in XML. The software build tools 426 may include binary converters (e.g., 204 in FIG. 2) to convert these elements into, for example, .dll files or other equivalent representations.
  • A management interface 428 may expose a set of management tools 430 to, for example, program managers involved with particular products and/or resources. These management tools 430 may enable the program managers to view a set of resources across one or more particular products. In this manner, the management tools 430 may enable the program managers to identify any redundancy or duplication appearing in different resources in different products. For example, a given error message may appear in slightly different forms in two or more different products. The management tools 430 may enable a program manager to identify the slightly different forms for this error message, resolve any inconsistencies in this message across the different products, and update the resource for this error message accordingly.
  • The localization management service 116 and the resource repository 124 may cooperate to manage the database model 402 as operations proceed over time. For example, resource developers may continually provide new text strings through the developer interface 414 and related development tools 416. As these new text strings or resources arrive in the repository, the localization management service may preliminarily translate or localize these new strings into any number of target languages. FIGS. 2 and 3 provide examples of preliminary localization modules at 202. In this manner, preliminary or initial localizations of the new text string may propagate through the database model 402 along the language axis 408. In turn, as these preliminary localizations become available in different languages, the localization interface 418 and related tools 420 may expose these preliminary localizations to the appropriate vendors who operate in those different languages. As described above, these vendors may review these preliminary localizations, and finalize as appropriate.
  • In example implementations, the various elements stored in the resource repository may be implemented in XML. The software build tools 426 may include binary converters (e.g., 204 in FIG. 2) to convert these elements into, for example, .dll files or other equivalent representations. In some cases, the software build tools 426 and the localization tools 420 may cooperate, to enable localization vendors to build software products that incorporate resources that were finally-localized by the vendors. More specifically, the localization vendors may be able to generate .dll files for the localized resources, link these .dll files into built products, and run the products to view the results of the localization. In this manner, the localization vendors may test and verify their localizations, as well as testing the operation of the built product when operating with the localized resources.
  • Assuming that the resource repository is implemented in XML, the various interfaces and tools described in FIG. 4 may enable various entities or processes to interact with the resource repository without programming in XML. More generally, the various interfaces and tools may serve to isolate external entities or processes from the implementations details of the resource repository. In addition, it is noted that FIG. 4 provides various examples of interfaces or tools to facilitate this description. However, these examples of interfaces or tools are non-limiting, and implementations of this description may provide other interfaces or tools as well.
  • In some implementations, the product builds, as presented to the localization vendors, may enable the vendors to hover a user interface device (e.g., a mouse pointer) over a particular non-localized string, or over a preliminarily-localized string appearing within the running product. The localization tools 420 may present a suitable user interface, responsive to input from vendor personnel to finally localize the string. Once the string is localized finally, the localization tools 420 may propagate the localized resource back to the resource repository.
  • In addition, finalized and shipped product builds may be presented to end-users, along with suitable tools enabling these end-users to localize or translate UI resources presented when these product builds are executed. More specifically, such end-user localization tools may enable the end-users to access the resource repository, whether sent or shipped with the product build directly to the end-users, or whether the end-users are given some mechanisms for accessing the repository. Such mechanisms may include web services by which the users may access the repository, with the repository not being physically shipped or sent with the build product. In these different scenarios, the repository may be provided in a “binary” form, and in these scenarios, conversion to binary may be optional in a sense. given access to the repository, the end-users may perform a form of “do it yourself” runtime localization on their own build of the product.
  • Enabling the end-users to access the resource repository may enable uses other than run-time localization. For example, end users may look up resources at run time, if they have access to the resource repository. As described elsewhere herein, most resource loads may be based on knowing the unique identifier associated with a particular resource, and loading the resource based on this identifier. However, in some cases identifier-based lookups may fail, for example, if a given resource with a given unique identifier is not yet been translated or localized. In this case, the resource repository could provide a string-based lookup mechanism to locate the resource, in addition to identifier-based lookups.
  • The database model 402 and related services and tools may readily be extended to handle not only languages, but also language dialects spoken within particular regions or communities. For example, the localization tools 420 may enable dialect localizers (who may or may not be localization vendors) who speak a particular dialect to add layers to the database model 402. These additional layers may localize resources from broader languages to particular dialects. Samples of these dialects may include, but are not limited to, the various dialects spoken in China, Native American languages, or the like.
  • In some instances, these layers added to the database model may be isolated from the rest of the database model, thereby enabling these dialect localizers to operate within these additional layers without affecting or impacting the rest of the database model. For example, the rest of the database model may be designated as “read-only” to these dialect localizers.
  • Having described the models or hierarchies for the resource repository in FIG. 4, the discussion now turns to a description of process flows for managing the localization of resources. This description is now presented with FIG. 5.
  • FIG. 5 illustrates process and data flows, denoted generally at 500, for managing the localization of resources. To facilitate description, but not to limit possible implementations, FIG. 5 may carry forward some elements from previous figures, and denote them with identical reference numbers. For example, FIG. 5 carries forward examples of development tools at 414, examples of a localization management service (e.g., 116) cooperating with a resource repository (e.g., 124), and examples of localization tools at 418.
  • In addition, FIG. 5 arranges certain processes and data flows in columns, corresponding to illustrative entities that may perform such processes and data flows, only for the purposes of this description. However, it is noted that these arrangements are provided for example only, and not to limit possible implementations. More specifically, entities other than those shown in FIG. 5 may perform some or all of these processes or data flows.
  • Turning to FIG. 5 in more detail, block 502 represents sending a resource authored in a first given language. For example, block 502 may include the development tools 414 providing text strings authored by development personnel (e.g., 112 in FIG. 1). FIG. 5 denotes these authored resources at 504, which collectively represents the various resources shown in FIG. 1 (e.g., 114 a and 114 n).
  • Block 506 represents receiving the authored resource in a first language. In the example shown in FIG. 5, block 506 may include the localization management service receiving the resource.
  • Block 508 generally represents preliminarily localizing the resource received in block 506. For example, the preliminary localization module 202, shown in FIG. 2, may perform block 508.
  • Block 510 may convert the preliminary localizations to a binary form (e.g., .dll files). In parallel with blocks 508 and 510, block 512 represents sending the resource for final localization. For example, block 512 may include sending the resources to one or more appropriate localization vendors, via the localization tools 418. FIG. 5 denotes at 514 the resources as sent for localization. More specifically, block 512 may include providing the input resource 514 to the localization vendor before the resource is compiled into a binary form. In this manner, the localization vendor may translate the resource before it is incorporated into a built, executable product. Accordingly, the localization vendor and related services are moved upstream in the software development process, as compared to previous techniques.
  • It is noted that block 512 may include sending the input resource 514 to multiple localization vendors, to be localized into multiple different target languages. FIG. 5 illustrates one instance of localization tools only for clarity of illustration.
  • Turning to the localization tools, block 516 generally represents receiving the resource for localization. In different possible scenarios, block 516 may include receiving resources that are preliminarily localized, or may include receiving resources that are non-localized.
  • Block 518 represents localizing the input resource 514. In some scenarios, multiple different localization vendors may respectively perform block 518 on a given input resource, to localize the input resource into several different target languages. Block 518 may include performing a final localization on the input resource.
  • Block 520 represents the localization tools returning the localized resource to the localization management service. FIG. 5 denotes the localized resource at 522. As noted elsewhere in this description, a plurality of different localization tools 418 may provide different instances of the resources 522, localized for different target languages.
  • Block 524 represents receiving one or more instances of resources 522, localized for one or more target languages. Afterwards, block 510 may convert the localized resources into binary form (e.g., .dll files). In instances where resources are initially or preliminarily localized and then converted to binary, block 510 may include updating the binary representation of such resources, after these resources have been finally localized.
  • For clarity of illustration and description, but not to limit possible implementations, the description of the process flows 500 now proceeds to FIG. 6 via off-page reference 526. The discussion now continues with FIG. 6.
  • FIG. 6 illustrates continuations, denoted generally at 600, of the process and data flows from FIG. 5. To facilitate description, but not to limit possible implementations, FIG. 6 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 6 carries forward an example localization management service at 116, an example resource repository at 124, and example software build tools at 426.
  • Beginning at off-page reference 602 from FIG. 5, block 604 generally represents loading a resource 606 into the repository. In different scenarios, the resource 606 loaded into the repository may be non-localized, preliminarily localized, or finally localized.
  • Turning to the software build tools 426, block 608 generally represents requesting one or more resources for building a given software product or application, localized for a particular target language. These resources may be converted or binary resources (e.g., .dll files), and the requests may reference unique identifiers associated with these converted resources (e.g., 210 in FIG. 2). FIG. 6 denotes such requests for localized resources at 610.
  • At the localization management service, block 612 generally represents receiving the request for localized resources. Block 612 may also include querying the resource repository with any identifiers associated with the requested resource, as denoted generally at 614.
  • Assuming that the resource repository contains converted, localized resources 616 responsive to the query 614, block 618 generally represents returning the localized resources. FIG. 6 denotes the returned localized resources generally at 620.
  • Turning to the software build tools 426, block 622 generally represents receiving the localized resources in response to the request 610. In turn, block 624 generally represents building the application, incorporating the localized resources 620, as built into and obtained from the resource repository 124. The resource repository provides the ability to build and/or generate for any human language for which resources are available dynamically. In the scenarios described herein, the English language is treated as just another language, in contrast to previous approaches in which development occurred initially and primarily in English, with other languages being localized after-the-fact. When block 622 generates/builds for a given language, the resource manager (e.g., 208 in FIG. 2) uses metadata stored in a resource repository to represent the user interface resources with which the product is built, without affecting the functionality of the product.
  • Having described the process and data flows shown in FIGS. 5 and 6, the discussion now turns to descriptions of additional processes and data flows by which the localization tools may enable localization vendors to build products or applications for testing localized resources. This description is now presented with FIG. 7.
  • FIG. 7 illustrates processes and data flows, denoted generally at 700, by which the localization tools may enable localization vendors to build products or applications for testing localized resources. To facilitate description, but not to limit possible implementations, FIG. 7 may carry forward some drawing elements from previous figures, and denote them with identical reference numbers. For example, FIG. 7 carries forward an example localization management service at 116, an example resource repository at 124, and example localization tools at 418.
  • Turning to FIG. 7 in more detail, block 702 represents providing a resource 704 from the resource repository 124. In the example shown in FIG. 7, the localization management service 116 may perform block 702. As described elsewhere herein, this resource may have been non-localized, or in some cases preliminarily-localized. To represent these different scenarios, FIG. 7 denotes the resource at 706.
  • Turning to the localization tools 418, block 708 generally represents receiving the resource (whether non-localized, or localized preliminarily) from the localization management service. In turn, block 710 represents finally localizing the resource, as may be performed by a localization vendor using the localization tools 418.
  • Block 712 represents building a software product to incorporate the localized resource. Block 712 may include converting the localized resource into appropriate binary form (e.g., .dll files) for incorporation or linking into the software product. For example, the localization tools 418 may include a binary converter (e.g., 204 in FIG. 2) for performing this conversion.
  • Block 714 generally represents executing the software product built in block 712 to test the localized resource is incorporated into that software product. Put differently, block 714 may include testing whether the software product executes appropriately with the localized resource, as represented in decision block 716.
  • From decision block 716, if the testing indicates that the software build does not execute appropriately with the localized resource, then the process flows 700 may take No branch 718 to return to block 710. In this scenario, block 710 may include applying a different localization to the resource, and repeating blocks 712, 714, and 716 with the newly-localized resource. In this manner, the process flows 700 may loop through block 716, 710, 712, and 714 until the software executes appropriately with the localized resource.
  • Returning to decision block 716, if the testing indicates that the software build executes appropriately with the localized resource, then the process flows 700 may take Yes branch 720 to block 722. Block 722 generally represents returning the localized resource, denoted at 724, to the localization management service.
  • At the localization management service, block 726 represents receiving the localized resource 724. In turn, block 728 represents loading the localized resource (denoted at 730) into the resource repository 124.
  • Having provided the preceding description, several observations are now noted. To facilitate description, some of the drawing figures illustrate data and/or process flows represented by unidirectional arrows. However, it is noted that these unidirectional representations do not exclude implementations having bidirectional data and/or process flows. in addition, certain processes and/or data flows are shown herein in particular orders chosen only for convenience and description, but not to limit possible implementations
  • Although the subject matter presented herein has been described in language specific to computer structural features, methodological acts, and computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the claims.
  • The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the following claims.

Claims (20)

1. A computer readable storage medium in which is encoded at least one data structure, the data structure comprising:
a representation of at least one resource provided in a first human language;
a representation of a software product that may incorporate at least the resource; and
a representation of at least a second human language into which the resource is localized, wherein the representation of the resource is related to the representation of the software product and to the representation of the second human language.
2. The computer readable storage medium of claim 1, wherein the representation of the resource is a representation of a text string.
3. The computer readable storage medium of claim 1, further comprising at least one representation of a binary version of the resource as localized into the second human language.
4. The computer readable storage medium of claim 3, wherein the binary version of the resource is a .dll file.
5. The computer readable storage medium of claim 1, further comprising a representation of at least a further resource, wherein the representation of the further resource is related to the representation of the software product to indicate that the software product may incorporate the further resource, and further comprising a representation of at least one human language into which the further resource is localized.
6. The computer readable storage medium of claim 1, further comprising a representation of at least a further human language into which the resource is localized.
7. The computer readable storage medium of claim 1, further comprising a representation of at least a dialect of the second human language into which the resource is localized.
8. The computer readable storage medium of claim 7, wherein the representation of the dialect is isolated from the rest of the data structure.
9. At least one computer-readable storage medium having computer-executable instructions stored thereon that, when executed by a computer, cause the computer to perform a method comprising:
receiving at least one resource provided in a first human language;
sending the resource for localization into at least a second human language;
receiving a localized version of the resource;
converting at least the localized version of the resource into a binary representation; and
building at least one software product that incorporates at least the binary representation of the localized version of the resource.
10. The computer-readable storage medium of claim 9, further comprising instructions for preliminarily localizing the resource, and wherein the instructions for sending the resource localization include instructions for sending the preliminarily localized resource for final localization.
11. The computer-readable storage medium of claim 9, further comprising instructions for storing the localized version of the resource into a resource repository.
12. The computer-readable storage medium of claim 9, wherein the instructions for building the software product include instructions for building a first version of the software product in the first human language in parallel with building at least a second version of the software product localized to the second human language.
13. The computer-readable storage medium of claim 9, wherein the instructions for building the software product include instructions for building a first version of the software product in the first human language, and wherein the instructions for sending the resource for localization are performed before the instructions for building the first version of the software product.
14. The computer-readable storage medium of claim 9, further comprising instructions for exposing a set of developer tools for authoring and receiving the resource, a set of software build tools for building the software product, a set of management tools for accessing representations of the resource, and a set of localization tools for localizing the resource.
15. A system comprising:
at least one processor coupled to communicate via at least one bus system;
at least one computer-readable storage medium coupled to communicate through the bus system, wherein the storage medium includes at least a resource repository, wherein the resource repository further comprises:
a representation of at least one resource provided in a first human language;
a representation of a software product that may incorporate at least the resource; and
a representation of at least a second human language into which the resource is localized, wherein the representation of the resource is related to the representation of the software product and to the representation of the second human language.
16. The system of claim 15, wherein the storage medium includes computer-executable instructions that, when executed by the processor, cause the processor to manage localizing the resource into at least a second human language.
17. The system of claim 16, further comprising a binary converter for converting the localized resource into a binary representation, and for associating a unique identifier with the localized resource.
18. The system of claim 17, further comprising a resource manager operative to receive requests that include unique identifiers associated with the converted resources, and to provide the converted resources in response to the requests.
19. The system of claim 16, wherein the storage medium includes at least one software product built using at least at least one resource that is localized into the second human language.
20. The system of claim 16, wherein the storage medium includes computer-executable instructions that, when executed by the processor, cause the processor to perform a method comprising:
receiving at least one resource provided in a first human language;
sending the resource for localization into at least a second human language;
receiving a localized version of the resource;
converting at least the localized version of the resource into the binary representation; and
building at least one software product that incorporates at least the binary representation of the localized version of the resource.
US12/041,620 2008-03-03 2008-03-03 Repositories and related services for managing localization of resources Active 2031-06-05 US8595710B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/041,620 US8595710B2 (en) 2008-03-03 2008-03-03 Repositories and related services for managing localization of resources

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/041,620 US8595710B2 (en) 2008-03-03 2008-03-03 Repositories and related services for managing localization of resources

Publications (2)

Publication Number Publication Date
US20090222787A1 true US20090222787A1 (en) 2009-09-03
US8595710B2 US8595710B2 (en) 2013-11-26

Family

ID=41014182

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/041,620 Active 2031-06-05 US8595710B2 (en) 2008-03-03 2008-03-03 Repositories and related services for managing localization of resources

Country Status (1)

Country Link
US (1) US8595710B2 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110276939A1 (en) * 2010-05-06 2011-11-10 Microsoft Corporation Techniques to enhance software production
US20130227522A1 (en) * 2012-02-23 2013-08-29 Microsoft Corporation Integrated Application Localization
WO2013138179A1 (en) * 2012-03-13 2013-09-19 Google Inc. System and method for providing a binary representation of a web page
US20130290930A1 (en) * 2010-12-23 2013-10-31 Microsoft Corporation Resource deployment based on conditions
US8595710B2 (en) * 2008-03-03 2013-11-26 Microsoft Corporation Repositories and related services for managing localization of resources
WO2014074629A1 (en) * 2012-11-06 2014-05-15 Intuit Inc. Stack-based adaptive localization and internationalization of applications
US9047103B2 (en) 2010-12-21 2015-06-02 Microsoft Technology Licensing, Llc Resource index identifying multiple resource instances and selecting most appropriate UI resource instance based on weighted resource request conditions
US20150154018A1 (en) * 2013-03-07 2015-06-04 Microsoft Technology Licensing, Llc Cloud-based localization platform
US20150309811A1 (en) * 2014-04-28 2015-10-29 Citrix Systems, Inc. Modifying an Application for Managed Execution
US9442744B2 (en) 2012-02-23 2016-09-13 Microsoft Technology Licensing, Llc Multilingual build integration for compiled applications
US9495371B2 (en) 2010-12-28 2016-11-15 Microsoft Technology Licensing, Llc Unified access to resources
US10007535B1 (en) * 2012-09-11 2018-06-26 EMC IP Holding Company LLC Method and system for an automation framework for internationalization compliant applications
US10248396B1 (en) * 2017-09-18 2019-04-02 Amazon Technologies, Inc. Code review with automated translation
US10417348B2 (en) * 2012-06-01 2019-09-17 Hangzhou Hikvision Digital Technology Co., Ltd. Method for processing and loading web pages supporting multiple languages and system thereof
US20200210211A1 (en) * 2018-12-27 2020-07-02 Microsoft Technology Licensing, Llc Personalization of resource strings in a computing device
WO2021050141A1 (en) * 2019-09-10 2021-03-18 Microsoft Technology Licensing, Llc Integrated system for localization of resources
US20230062965A1 (en) * 2021-08-25 2023-03-02 Sap Se Intelligent platform for documentation authoring and production

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9922351B2 (en) 2013-08-29 2018-03-20 Intuit Inc. Location-based adaptation of financial management system
US11636064B2 (en) 2021-07-13 2023-04-25 Microsoft Technology Licensing, Llc Compression of localized files

Citations (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5903858A (en) * 1995-06-23 1999-05-11 Saraki; Masashi Translation machine for editing a original text by rewriting the same and translating the rewrote one
US6035121A (en) * 1997-07-07 2000-03-07 Netscape Communication Corporation Method and system for localizing a computer program
US6092037A (en) * 1996-03-27 2000-07-18 Dell Usa, L.P. Dynamic multi-lingual software translation system
US20020116172A1 (en) * 2001-02-16 2002-08-22 Microsoft Corporation Multilanguage UI with localized resources
US6496793B1 (en) * 1993-04-21 2002-12-17 Borland Software Corporation System and methods for national language support with embedded locale-specific language driver identifiers
US20030004703A1 (en) * 2001-06-28 2003-01-02 Arvind Prabhakar Method and system for localizing a markup language document
US6567973B1 (en) * 1999-07-28 2003-05-20 International Business Machines Corporation Introspective editor system, program, and method for software translation using a facade class
US20030126559A1 (en) * 2001-11-27 2003-07-03 Nils Fuhrmann Generation of localized software applications
US20040088370A1 (en) * 2002-05-16 2004-05-06 Ajay Patel System and method for application and resource data integration
US20040230416A1 (en) * 2003-05-12 2004-11-18 Microsoft Corporation Bifurcated operating system having a language neutral component
US20050050526A1 (en) * 2003-08-28 2005-03-03 Dahne-Steuber Ines Antje System and method for real-time generation of software translation
US20050066315A1 (en) * 2003-09-23 2005-03-24 Nguyen Liem Manh Localization tool
US20050102253A1 (en) * 2003-10-23 2005-05-12 Microsoft Corporation Resource compaction
US20050108433A1 (en) * 2003-10-23 2005-05-19 Microsoft Corporation Resource manifest
US6910068B2 (en) * 1999-06-11 2005-06-21 Microsoft Corporation XML-based template language for devices and services
US20050204332A1 (en) * 2004-03-15 2005-09-15 Ramco Systems Limited Method and system for developing large web-based multi-language applications
US20050240905A1 (en) * 2004-04-22 2005-10-27 Microsoft Corporation Language localization using tables
US6983238B2 (en) * 2001-02-07 2006-01-03 American International Group, Inc. Methods and apparatus for globalizing software
US20060116864A1 (en) * 2004-12-01 2006-06-01 Microsoft Corporation Safe, secure resource editing for application localization with automatic adjustment of application user interface for translated resources
US20060117304A1 (en) * 2004-11-23 2006-06-01 Microsoft Corporation Method and system for localizing a package
US20060195831A1 (en) * 2005-02-28 2006-08-31 John Bossom System and method for the localization of released computer program
US20060225068A1 (en) * 2000-10-30 2006-10-05 Microsoft Corporation System and method for dynamically verifying the compatibility of a user interface resource
US20070245321A1 (en) * 2004-09-24 2007-10-18 University Of Abertay Dundee Computer games localisation
US20080189096A1 (en) * 2007-02-02 2008-08-07 Square D Company Translation process component
US7509318B2 (en) * 2005-01-28 2009-03-24 Microsoft Corporation Automatic resource translation
US20090094609A1 (en) * 2007-10-09 2009-04-09 Microsoft Corporation Dynamically providing a localized user interface language resource
US7552452B2 (en) * 2004-12-01 2009-06-23 Microsoft Corporation Safe, secure resource editing for application localization with language fallback
US7607085B1 (en) * 1999-05-11 2009-10-20 Microsoft Corporation Client side localizations on the world wide web
US7716641B2 (en) * 2004-12-01 2010-05-11 Microsoft Corporation Method and system for automatically identifying and marking subsets of localizable resources
US7761849B2 (en) * 2005-08-25 2010-07-20 Microsoft Corporation Automated analysis and recovery of localization data

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8595710B2 (en) * 2008-03-03 2013-11-26 Microsoft Corporation Repositories and related services for managing localization of resources

Patent Citations (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6496793B1 (en) * 1993-04-21 2002-12-17 Borland Software Corporation System and methods for national language support with embedded locale-specific language driver identifiers
US5903858A (en) * 1995-06-23 1999-05-11 Saraki; Masashi Translation machine for editing a original text by rewriting the same and translating the rewrote one
US6092037A (en) * 1996-03-27 2000-07-18 Dell Usa, L.P. Dynamic multi-lingual software translation system
US6035121A (en) * 1997-07-07 2000-03-07 Netscape Communication Corporation Method and system for localizing a computer program
US7607085B1 (en) * 1999-05-11 2009-10-20 Microsoft Corporation Client side localizations on the world wide web
US6910068B2 (en) * 1999-06-11 2005-06-21 Microsoft Corporation XML-based template language for devices and services
US6567973B1 (en) * 1999-07-28 2003-05-20 International Business Machines Corporation Introspective editor system, program, and method for software translation using a facade class
US20060225068A1 (en) * 2000-10-30 2006-10-05 Microsoft Corporation System and method for dynamically verifying the compatibility of a user interface resource
US7178142B2 (en) * 2000-10-30 2007-02-13 Microsoft Corporation System and method for dynamically verifying the compatibility of a user interface resource
US6983238B2 (en) * 2001-02-07 2006-01-03 American International Group, Inc. Methods and apparatus for globalizing software
US20020116172A1 (en) * 2001-02-16 2002-08-22 Microsoft Corporation Multilanguage UI with localized resources
US20030004703A1 (en) * 2001-06-28 2003-01-02 Arvind Prabhakar Method and system for localizing a markup language document
US20030126559A1 (en) * 2001-11-27 2003-07-03 Nils Fuhrmann Generation of localized software applications
US20040088370A1 (en) * 2002-05-16 2004-05-06 Ajay Patel System and method for application and resource data integration
US20040230416A1 (en) * 2003-05-12 2004-11-18 Microsoft Corporation Bifurcated operating system having a language neutral component
US20050050526A1 (en) * 2003-08-28 2005-03-03 Dahne-Steuber Ines Antje System and method for real-time generation of software translation
US20050066315A1 (en) * 2003-09-23 2005-03-24 Nguyen Liem Manh Localization tool
US20050108433A1 (en) * 2003-10-23 2005-05-19 Microsoft Corporation Resource manifest
US20050102253A1 (en) * 2003-10-23 2005-05-12 Microsoft Corporation Resource compaction
US20050204332A1 (en) * 2004-03-15 2005-09-15 Ramco Systems Limited Method and system for developing large web-based multi-language applications
US20050240905A1 (en) * 2004-04-22 2005-10-27 Microsoft Corporation Language localization using tables
US7721271B2 (en) * 2004-04-22 2010-05-18 Microsoft Corporation Language localization and intercepting data using translation tables
US20070245321A1 (en) * 2004-09-24 2007-10-18 University Of Abertay Dundee Computer games localisation
US20060117304A1 (en) * 2004-11-23 2006-06-01 Microsoft Corporation Method and system for localizing a package
US7552452B2 (en) * 2004-12-01 2009-06-23 Microsoft Corporation Safe, secure resource editing for application localization with language fallback
US20060116864A1 (en) * 2004-12-01 2006-06-01 Microsoft Corporation Safe, secure resource editing for application localization with automatic adjustment of application user interface for translated resources
US7716641B2 (en) * 2004-12-01 2010-05-11 Microsoft Corporation Method and system for automatically identifying and marking subsets of localizable resources
US7509318B2 (en) * 2005-01-28 2009-03-24 Microsoft Corporation Automatic resource translation
US20060195831A1 (en) * 2005-02-28 2006-08-31 John Bossom System and method for the localization of released computer program
US7761849B2 (en) * 2005-08-25 2010-07-20 Microsoft Corporation Automated analysis and recovery of localization data
US20080189096A1 (en) * 2007-02-02 2008-08-07 Square D Company Translation process component
US7797151B2 (en) * 2007-02-02 2010-09-14 Darshana Apte Translation process component
US20090094609A1 (en) * 2007-10-09 2009-04-09 Microsoft Corporation Dynamically providing a localized user interface language resource

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Kuhr, "Creating a Multilingual Scribble Application with the MS Resource Localization Toolset", September 12th, 1998 *

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8595710B2 (en) * 2008-03-03 2013-11-26 Microsoft Corporation Repositories and related services for managing localization of resources
US9710261B2 (en) * 2010-05-06 2017-07-18 Microsoft Technology Licensing, Llc Techniques to enhance software production
US20110276939A1 (en) * 2010-05-06 2011-11-10 Microsoft Corporation Techniques to enhance software production
US9047103B2 (en) 2010-12-21 2015-06-02 Microsoft Technology Licensing, Llc Resource index identifying multiple resource instances and selecting most appropriate UI resource instance based on weighted resource request conditions
US9021434B2 (en) * 2010-12-23 2015-04-28 Microsoft Technology Licensing, Llc Resource deployment based on conditions
US10228933B2 (en) 2010-12-23 2019-03-12 Microsoft Technology Licensing, Llc Resource deployment based on conditions
US20130290930A1 (en) * 2010-12-23 2013-10-31 Microsoft Corporation Resource deployment based on conditions
US9495371B2 (en) 2010-12-28 2016-11-15 Microsoft Technology Licensing, Llc Unified access to resources
US9442744B2 (en) 2012-02-23 2016-09-13 Microsoft Technology Licensing, Llc Multilingual build integration for compiled applications
US20140309983A1 (en) * 2012-02-23 2014-10-16 Microsoft Corporation Integrated Application Localization
US9400784B2 (en) * 2012-02-23 2016-07-26 Microsoft Technology Licensing, Llc Integrated application localization
US8789015B2 (en) * 2012-02-23 2014-07-22 Microsoft Corporation Integrated application localization
US20130227522A1 (en) * 2012-02-23 2013-08-29 Microsoft Corporation Integrated Application Localization
US11194557B2 (en) 2012-03-13 2021-12-07 Google Llc System and method providing a binary representation of a web page
US10360291B2 (en) 2012-03-13 2019-07-23 Google Llc System and method providing a binary representation of a web page
US9298679B2 (en) 2012-03-13 2016-03-29 Google Inc. System and method providing a binary representation of a web page
WO2013138179A1 (en) * 2012-03-13 2013-09-19 Google Inc. System and method for providing a binary representation of a web page
US10417348B2 (en) * 2012-06-01 2019-09-17 Hangzhou Hikvision Digital Technology Co., Ltd. Method for processing and loading web pages supporting multiple languages and system thereof
US10007535B1 (en) * 2012-09-11 2018-06-26 EMC IP Holding Company LLC Method and system for an automation framework for internationalization compliant applications
GB2511667A (en) * 2012-11-06 2014-09-10 Intuit Inc Stack-based adaptive localization and internationalization of applications
WO2014074629A1 (en) * 2012-11-06 2014-05-15 Intuit Inc. Stack-based adaptive localization and internationalization of applications
US9990191B2 (en) * 2013-03-07 2018-06-05 Microsoft Technology Licensing, Llc Cloud-based localization platform
US9772840B2 (en) * 2013-03-07 2017-09-26 Microsoft Technology, LLC Cloud-based localization platform
US20150154019A1 (en) * 2013-03-07 2015-06-04 Microsoft Technology Licensing, Llc Cloud-based localization platform
US20150154018A1 (en) * 2013-03-07 2015-06-04 Microsoft Technology Licensing, Llc Cloud-based localization platform
US9619216B2 (en) * 2014-04-28 2017-04-11 Citrix Systems, Inc. Modifying an application for managed execution
US20150309811A1 (en) * 2014-04-28 2015-10-29 Citrix Systems, Inc. Modifying an Application for Managed Execution
US10248396B1 (en) * 2017-09-18 2019-04-02 Amazon Technologies, Inc. Code review with automated translation
US20200210211A1 (en) * 2018-12-27 2020-07-02 Microsoft Technology Licensing, Llc Personalization of resource strings in a computing device
US11327774B2 (en) * 2018-12-27 2022-05-10 Microsoft Technology Licensing, Llc Personalization of resource strings in a computing device
WO2021050141A1 (en) * 2019-09-10 2021-03-18 Microsoft Technology Licensing, Llc Integrated system for localization of resources
US11630681B2 (en) 2019-09-10 2023-04-18 Microsoft Technology Licensing, Llc Integrated system for localization of resources tailored for translations by setting a flag
US20230062965A1 (en) * 2021-08-25 2023-03-02 Sap Se Intelligent platform for documentation authoring and production
US11762657B2 (en) * 2021-08-25 2023-09-19 Sap Se Intelligent platform for documentation authoring and production

Also Published As

Publication number Publication date
US8595710B2 (en) 2013-11-26

Similar Documents

Publication Publication Date Title
US8595710B2 (en) Repositories and related services for managing localization of resources
US7987087B2 (en) Method and system for improved software localization
US8516435B2 (en) System and method for generating implementation artifacts for contextually-aware business applications
US8667456B1 (en) Cloud-based indexing for integrated development environments
US7937410B2 (en) Generic archiving of enterprise service oriented architecture data
US20090094609A1 (en) Dynamically providing a localized user interface language resource
US20160283228A1 (en) Integrated cloud platform translation system
US7823120B2 (en) Device, system and method for accelerated modeling
US8433687B1 (en) Off-line indexing for client-based software development tools
US7818277B2 (en) Methods and apparatus for business rules authoring and operation employing a customizable vocabulary
US9965259B2 (en) System for translating diverse programming languages
US20090210390A1 (en) Asset adviser intelligence engine for managing reusable software assets
US20110144972A1 (en) Method and System for Generating a Localized Software Product
Zhang et al. Development of IFC-based construction industry ontology for information retrieval from IFC models
US20120290284A1 (en) Creating and implementing language-dependent string pluralizations
Karagiannis et al. Metamodels as a conceptual structure: some semantical and syntactical operations
US9244706B2 (en) Command line shell command generation based on schema
Ziad et al. Teanga: a linked data based platform for natural language processing
Wagelaar et al. Platform ontologies for the model-driven architecture
US20110307240A1 (en) Data modeling of multilingual taxonomical hierarchies
Diercks et al. Evaluation of tools for describing, reproducing and reusing scientific workflows
JP7269244B2 (en) Systems and methods for providing globalization capabilities in service management application interfaces
Almas et al. Continuous integration and unit testing of digital editions
US8521753B2 (en) Unified formats for resources and repositories for managing localization
Wright et al. Segueing from a data category registry to a data concept registry

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALDAHLEH, AYMAN;LARRINAGA, JAVIER L.;BURUKHIN, ANATOLIY;AND OTHERS;REEL/FRAME:020592/0194;SIGNING DATES FROM 20080226 TO 20080229

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALDAHLEH, AYMAN;LARRINAGA, JAVIER L.;BURUKHIN, ANATOLIY;AND OTHERS;SIGNING DATES FROM 20080226 TO 20080229;REEL/FRAME:020592/0194

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034542/0001

Effective date: 20141014

AS Assignment

Owner name: ZHIGU HOLDINGS LIMITED, CAYMAN ISLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT TECHNOLOGY LICENSING, LLC;REEL/FRAME:040354/0001

Effective date: 20160516

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8