IP Library › Granted Patent US 7,103,875

Granted Patent B1

US 7,103,875 · App. 09/960,580 · Granted Sep 5, 2006

Methods and apparatus for integrated, automatic pseudo localization of software

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 7,103,875
App. No.: 09/960,580
Granted: Sep 5, 2006
Kind: B1

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Methods and articles of manufacture for integrated, automatic pseudo localization of software applications are disclosed herein. A pseudo localization process, comprised of one or more utility applications, is integrated into a build cycle for a developing software application to generate pseudo-translated user-interface code as part of a build process. A build application may then generate a pseudo-language build of the developing software application and/or development database to enable testing and identification of internationalization defects that would prevent effective localization of the software product for the international market.

Claims (60)

1. A method, comprising:

integrating at least one pseudo localization utility application with a build application to provide an integrated build application;

executing the integrated build application to generate pseudo-translated locale-dependant code, wherein executing the at least one pseudo localization utility application includes:

(a) retrieving locale-dependant code from at least one storage location;

(b) altering an appearance of the locale-dependant code; and

generating a pseudo-language build with the pseudo-translated locale-dependant code.

2. The method of claim 1 , further comprising:

testing the pseudo-language build; and

identifying at least one internationalization bug.

3. The method of claim 2 , wherein the internationalization bug comprises a hard-coded string, a hard-coded format, or a hard-coded reference to a translation.

4. The method of claim 2 , wherein identifying the at least one internationalization bug comprises discovering unaltered locale-dependant code in the user-interface.

5. The method of claim 1 , wherein altering the appearance of the locale-dependant code comprises adding at least one prefix character to the locale-dependant code.

6. The method of claim 5 , wherein the at least one prefix character comprises at least one multi-byte character.

7. The method of claim 5 , wherein the at least one prefix character comprises at least one right-to-left character.

8. The method of claim 5 , wherein the at least one prefix character comprises a prefix string including at least one multi-byte character and at least one right-to-left character.

9. The method of claim 1 , wherein the at least one pseudo localization utility application comprises at least one server message specific utility, and the locale-dependant code comprises at least one server message.

10. The method of claim 1 , wherein the at least one pseudo localization utility application comprises at least one repository string specific utility, and the locale-dependant code comprises at least one repository string.

11. The method of claim 1 , wherein the at least one pseudo localization utility application comprises at least one resource file specific utility, and the locale-dependant code comprises at least one resource file.

12. The method of claim 1 , wherein the at least one pseudo localization utility application comprises at least one utility application capable of retrieving or altering at least one element of user-interface code of a type selected from a group, including: a server message, a repository string, a static UI file, and a seed data file.

13. The method of claim 1 , wherein the build application comprises a database build application, the at least one pseudo localization utility application comprises at least one seed data file specific utility, and the locale-dependant code comprises at least one seed data file.

14. The method of claim 1 , wherein the build application comprises a software build application.

15. The method of claim 1 , wherein said executing the at least one pseudo localization utility application is in response to a determination in the build application to build a pseudo-language build.

16. An article of manufacture, comprising:

a machine-readable storage medium to store instructions, which, when executed by a processing system, cause the processing system to:

implement at least one pseudo localization utility application integrated with a build application to provide an integrated build application;

execute the integrated build application to generate pseudo-translated locale-dependant code through

(a) retrieving locale-dependant code from at least one storage location,

(b) altering an appearance of the locale-dependant code, and

generate a pseudo-language build with the pseudo-translated locale-dependant code.

17. The article of manufacture of claim 16 , wherein the machine-readable medium further includes instructions, which, when executed by a machine, cause the machine to:

test the pseudo-language build; and

identify at least one internationalization bug.

18. The article of manufacture of claim 17 , wherein the internationalization bug comprises a hard-coded string, a hard-coded format, or a hard-coded reference to a translation.

19. The article of manufacture of claim 17 , wherein identifying the at least one internationalization bug comprises discovering unaltered locale-dependant code in the user-interface.

20. The article of manufacture of claim 16 , wherein altering the appearance of the locale-dependant code comprises adding at least one prefix character to the locale-dependant code.

21. The article of manufacture of claim 20 , wherein the at least one prefix character comprises at least one multi-byte character.

22. The article of manufacture of claim 20 , wherein the at least one prefix character comprises at least one right-to-left character.

23. The article of manufacture of claim 20 , wherein the at least one prefix character comprises a prefix string including at least one multi-byte character and at least one right-to-left character.

24. The article of manufacture of claim 16 , wherein the at least one pseudo localization utility application comprises at least one server message specific utility, and the locale-dependant code comprises at least one server message.

25. The article of manufacture of claim 16 , wherein the at least one pseudo localization utility application comprises at least one repository string specific utility, and the locale-dependant code comprises at least one repository string.

26. The article of manufacture of claim 16 , wherein the at least one pseudo localization utility application comprises at least one resource file specific utility, and the locale-dependant code comprises at least one resource file.

27. The article of manufacture of claim 16 , wherein the at least one pseudo localization utility application comprises at least one utility application capable of retrieving or altering at least one element of user-interface code of a type selected from a group, including: a server message, a repository string, a static UI file, and a seed data file.

28. The article of manufacture of claim 16 , wherein the build application comprises a database build application, the at least one pseudo localization utility application comprises at least one seed data file specific utility, and the locale-dependant code comprises at least one seed data file.

29. The article of manufacture of claim 16 , wherein the build application comprises a software build application.

30. A system, comprising:

computer system having a processor, a memory, and an input/output device;

an executable build application, stored in the memory of the computer system, and configured, when executed by the processor, to generate a language-specific build; and

at least one executable pseudo localization utility application, stored in the memory of the computer system, and integrated with the build application to generate a pseudo-language, language-specific build, the at least one executable pseudo localization utility application integrated with the build application, when executed by the processor, to retrieve locale-dependant code from at least one storage location, to alter an appearance of the locale-dependant code, and to store the altered locale-dependant code in at least one second storage location.

31. The system of claim 30 , wherein altering the appearance of the locale-dependant code comprises adding at least one prefix character to the locale-dependant code.

32. The system of claim 31 , wherein the at least one prefix character comprises at least one multi-byte character.

33. The system of claim 31 , wherein the at least one prefix character comprises at least one right-to-left character.

34. The system of claim 31 , wherein the at least one prefix character comprises a prefix string including at least one multi-byte character and at least one right-to-left character.

35. The system of claim 30 , wherein the at least one pseudo localization utility application comprises at least one server message specific utility, and the locale-dependant code comprises at least one server message.

36. The system of claim 30 , wherein the at least one pseudo localization utility application comprises at least one repository string specific utility, and the locale-dependant code comprises at least one repository string.

37. The system of claim 30 , wherein the at least one pseudo localization utility application comprises at least one resource file specific utility, and the locale-dependant code comprises at least one resource file.

38. The system of claim 30 , wherein the at least one pseudo localization utility application comprises at least one utility application capable of retrieving or altering at least one element of user-interface code of a type selected from a group, including: a server message, a repository string, a static UI file, and a seed data file.

39. The system of claim 30 , wherein the build application comprises a database build application, the at least one pseudo localization utility application comprises at least one seed data file specific utility, and the locale-dependant code comprises at least one seed data file.

40. The system of claim 30 , wherein the build application comprises a software build application.

Assignments (1)

MERGER Recorded Feb 5, 2016

From: SIEBEL SYSTEMS, INC.

To: ORACLE AMERICA, INC.

Reel/Frame 037702/0516 →