INFO30005 WEB IT
RONAL SINGH
Copyright By PowCoder代写 加微信 powcoder
Localisation (l10n)
Internationalisation (i18n)
What to consider?
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
– implied meanings of symbols and colours
Localisation
Adaptation to meet the language, cultural, and other requirements of a specific target market
Internationalisation
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!
Good Morning!
Localisation
> translation
Localisation goes beyond than simple translation.
Website designed for UK, American and Australian may be localised based on spelling differences, currency, culture.
= 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?
February 1st?
January 2nd?
Direction Language
Local Regulations
Sizing (paper, shoes, clothes)
Social Media
Devices, Browsers
THINK ABOUT
Don’t try to do it all by yourself!
Legal Advice i18n Developers Translation L10n review
There are experts offering a wide variety of services
Data Media
Any web application will be composed of many elements, including…
Widgets Frameworks
separate the code from the content
the code is locale independent, and the content is locale-specific
Good Morning!
Good Morning
{ “Good morning”: “G’day”
You can have a collection of JSONs with keys matching different texts.
“Good morning”: “Good morning”
“Good morning”: “Bonjour!”
i18n.configure({
locales:[‘au’, ‘us’, ‘fr’],
directory:__dirname+’/locales’
app.get(‘say/:lang’,function(req,res){ i18n.setLocale(req,req.params.lang);
console.log(res.__(‘Good morning’));
https: //www. npmjs. com/package/i18n
Depending on different languages, you might need different font support.
Does it support all chars needed? Support for right set of chars?
Is it culturally appropriate?
From the start:
Identify your target locales Refactor the code Test for each locale
https: //www. w3. org/standards/webdesign/i18n
Localisation Management software
Content repo Translation memory
Collaboration tools Automatic translation
INFO30005 WEB IT
RONAL SINGH
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com