No ratings.
ewefwefrgthyuio;sdfg |
Certree Product Globalization May 29, 2019 Table of Contents 1.Globalization 2.Background & Purpose The purpose of this document is to explain the technical implementation of globalization. It will also cover the scope of globalization in Certree Product. 3.What is Globalization? When a web application supports globalization, it means that the application can render its contents based on the language preference set by a user in his or her profile or browser. Localization involves translating a web application into different languages and cultures. 4.Language preference setting option for user When a user will open the Certree application, it will pick browsers language/culture and set an application's language. There will be an option at the top to change the language. If a user has changed the language manually from language drop-down then it will be saved in browser's cookies for the future, so the user doesn't have to change it to manually each and every time. 5.Scope of Globalization in application Following areas will be changed by changing language. Language Vocabulary -Translate content into selected language. This is implemented through database. ListOption Label NavigationItem ErrorMessage HelpText PageHeader SectionHeader GridHeader Button LinkButton Placeholder AlertMessage HyperLink 2. The layout of User Interface - Direction of writing data. Left to Right or Right to Left. This is not implemented yet. 3. Date Format - Date format should automatically be changed on the basis of the user's geographical location. This is implemented through moment.js. 4. Time of Region - People living in different timezones should see the corresponding local time in the application. This is not implemented yet. 5. Currency handling - Thousand and decimal separators are different in some countries, so it should change as per profile language. This is not implemented yet. 6. International Input Types - Code should handle and interpret all input types without affecting the functionality of the product. Input fields like Mobile number, SSN, address and Postal code/ Zip code, etc should be validated as per selected country language. This is implemented through database. Use below link for masking details. https://vuetifyjs.com/en/components/text-fields 7. Third party screens - If a user is redirecting to third-party login page Microsoft, google, yahoo, etc or payment service provider then those also should be in a preferred language. This is not implemented yet. 6.Resource Types The table below shows the Resource types which should be in the database by default. Resource Type Name Resource Type Description Label Used for field labels. ErrorMessage Used for validation and error messages. HelpText Used for help text and help bubble messages. ListOption Used for list items within a specific list. GridHeader Used for table and grid headers. PageHeader Used for main page headers. SectionHeader Used for page section headers. CommunicationTemplate Used for communication templates. EmailTemplate Used for e-mail templates. ActionIcon Used for icons which correspond actions (edit, delete, etc.) NavigationItem Used for hyperlinks related to navigation. SiteFooterLink Used for hyperlinks which appear in the site footer. TopMenuLink Used for hyperlinks which appear in the top menu. InternationInputType Used for international input types, which are dynamically decided based on the country exp. SSN, Phone Number, Zipcode/Postalcode, etc. 7.Resource Naming Convention The table below shows the naming convention to be used for each Resource type. Resource Type Name Resource Type Description Label Label_ModuleName_SectionName_ResourceKeyName ErrorMessage ErrorMessage_ModuleName_ SectionName_ResourceKeyName HelpText HelpText_ModuleName_ SectionName_ResourceKeyName ListOption ListOption_ListName_ResourceKeyName GridHeader GridHeader_ModuleName_ SectionName_ResourceKeyName PageHeader PageHeader_ModuleName_ SectionName_ResourceKeyName SectionHeader SectionHeader_ModuleName_ SectionName_ResourceKeyName CommunicationTemplate CommunicationTemplate_ModuleName_ SectionName_ResourceKeyName EmailTemplate EmailTemplate_ModuleName_ SectionName_ResourceKeyName ActionIcon ActionIcon_ModuleName_ SectionName_ResourceKeyName NavigationItem NavigationItem_ModuleName_ResourceKeyName SiteFooterLink SiteFooterLink_ResourceKeyName TopMenuLink TopMenuLink_ResourceKeyName InternationInputType InternationalInputType_ResourceKeyName 8.Things to Note The name of your resource key must start with the resource type name. (i.e. Label, ErrorMessage, etc.). After the resource key type name, it must be followed by "ModuleName" (except for ListOption, FooterLink, InternationalInputType, and TopMenuLink). ModuleName is the name of the module which the resource applies to (i.e. Admin, POE, POI, etc.). After the module name, it must be followed by "SectionName" (except for ListOption, FooterLink, TopMenuLink, InternationalInputType and NavigationItem). SectionName is the name of the section or sub module which the resource applies to (i.e. Search, CreatePOE in POE module). For "ListOption", you must include the "ListName" instead of "ModuleName" as the second part. (i.e. ListOption_Country_UnitedStatesOfAmerica). 9.Examples Label_UserManagement_AddUser_FirstName ErrorMessage_EmailManagement_IssuerEmail_EnterSubject HelpText_POE_CreatePOE_FirstName CommunicationTemplate_UserManagement_AddUser_UserCreated EmailTemplate_SearchPOE_SendEnvelope_EnvelopeLinkBody ListOption_Module_Admin |