1. A method for imaging device display element localization, said method comprising: registering a remote computing device (RCD) application with an imaging device (IDev) wherein said RCD application is accessed when a trigger input is received at an IDev user interface (UI); receiving a notification at said RCD application, said notification indicating that said trigger input was received at said IDev UI; sending menu data to said IDev in response to said receiving a notification, wherein said menu data is in the form of an XML message and wherein said menu content data comprises at least one prompt to solicit user input at said IDev UI; receiving locale data from said IDev UI, wherein said locale data is embedded in a header of an HTTP request and said locale data defines the geographical locale of a user; receiving a content request from said IDev, wherein said content request is a user interface page in said HTTP request and said content request identifies locale-independent content; identifying a locale from said locale data; retrieving locale-specific data related to said locale using a dynamic link library (DLL), wherein said locale-specific data consists of a language, a time format, a date format, an address format, a calendar format and a currency type; retrieving static content identified in said content request; merging said locale-specific data with said static content to form a localized document; and sending said localized document to said IDev.
1. A method for imaging device display element localization, said method comprising: registering a remote computing device (RCD) application with an imaging device (IDev) wherein said RCD application is accessed when a trigger input is received at an IDev user interface (UI); receiving a notification at said RCD application, said notification indicating that said trigger input was received at said IDev UI; sending menu data to said IDev in response to said receiving a notification, wherein said menu data is in the form of an XML message and wherein said menu content data comprises at least one prompt to solicit user input at said IDev UI; receiving locale data from said IDev UI, wherein said locale data is embedded in a header of an HTTP request and said locale data defines the geographical locale of a user; receiving a content request from said IDev, wherein said content request is a user interface page in said HTTP request and said content request identifies locale-independent content; identifying a locale from said locale data; retrieving locale-specific data related to said locale using a dynamic link library (DLL), wherein said locale-specific data consists of a language, a time format, a date format, an address format, a calendar format and a currency type; retrieving static content identified in said content request; merging said locale-specific data with said static content to form a localized document; and sending said localized document to said IDev. 8. A method as described in claim 1 wherein said static content comprises a markup language page comprising locale-specific variables.