程序案例-INFO30005 WEB

Localisation Internationalisation & RONAL SINGH INFO30005 WEB IT TOPICS Localisation (l10n) Internationalisation (i18n) What to consider Tips Your website looks great, works great, and it is really popular in Australia. Now you want to take it to the rest of the world. – language – time formats – Currency; Tax regulation – decimal system – units – implied meanings of symbols and colours Localisation l10n Adaptation to meet the language, cultural, and other requirements of a specific target market Internationalisation i18n Design and development that support localization – implementation efforts to make it easy to localise a website; Good Morning! Assumptions we make here: – Everyone may speak English – Everyone reads from left to right – It is morning (time zone): it’s morning in one part of world but night in another. – User can see: and the fact that users can see this message…we just covered the accessibility topic i18n is about Identifying these assumptions and making decisions to avoid these assumptions Good Morning! en Good Morning! en_AU Localisation translation > Localisation goes beyond than simple translation. Website designed for UK, American and Australian may be localised based on spelling differences, currency, culture. Locale = parameters that define language + region + preferences Special characters Text direction Currency symbols Displaying prices in local currency Following local tax regulations Localising your pricing structure kg or lb cm or in 01/02/21 February 1st January 2nd THINK ABOUT Language Currency Direction Units Local Regulations Sizing (paper, shoes, clothes) Devices, Browsers Social Media Don’t try to do it all by yourself! Legal Advice i18n Developers L10n review Translation There are experts offering a wide variety of services Text Data Widgets Frameworks Libs Media Any web application will be composed of many elements, including… code content separate the code from the content the code is locale independent, and the content is locale-specific Good Morning! en_UK Good Morning en_AU G’Day! fr_FR Bonjour! { “Good morning”: “G’day” } au.json { “Good morning”: “Good morning” } us.json { “Good morning”: “Bonjour!” } fr.json /locales au.json us.json fr.json You can have a collection of JSONs with keys matching different texts. app.get(‘say/:lang’,function(req,res){ i18n.setLocale(req,req.params.lang); console.log(res.__(‘Good morning’)); } i18n.configure({ locales:[‘au’, ‘us’, ‘fr’], directory:__dirname+’/locales’ }); App.js au https://www.npmjs.com/package/i18n fonts Does it support all chars needed Is it culturally appropriate Support for right set of chars Depending on different languages, you might need different font support. … Colours From the start: Identify your target locales Refactor the code Test for each locale Tools https://www.w3.org/standards/webdesign/i18n Localisation Management software Content repo Translation memory Automatic translation Collaboration tools Localisation Internationalisation & RONAL SINGH INFO30005 WEB IT