W3C   W3C Internationalization (I18n) Activity: Making the World Wide Web truly world wide!

Latest del.icio.us tags

Blog searches

Contributors

If you own a blog with a focus on internationalization, and want to be added or removed from this aggregator, please get in touch with Richard Ishida at ishida@w3.org.

All times are UTC.

Powered by: Planet

Planet Web I18n

The Planet Web I18n aggregates posts from various blogs that talk about Web internationalization (i18n). While it is hosted by the W3C Internationalization Activity, the content of the individual entries represent only the opinion of their respective authors and does not reflect the position of the Internationalization Activity.

June 18, 2015

W3C I18n Activity highlights

Announcing The Unicode® Standard, Version 8.0

Version 8.0 of the Unicode Standard is now available. It includes 41 new emoji characters (including five modifiers for diversity), 5,771 new ideographs for Chinese, Japanese, and Korean, the new Georgian lari currency symbol, and 86 lowercase Cherokee syllables. It also adds letters to existing scripts to support Arwi (the Tamil language written in the Arabic script), the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other languages of Africa. In total, this version adds 7,716 new characters and six new scripts. For full details on Version 8.0, see Unicode 8.0.

The first version of Unicode Technical Report #51, Unicode Emoji is being released at the same time. That document describes the new emoji characters. It provides design guidelines and data for improving emoji interoperability across platforms, gives background information about emoji symbols, and describes how they are selected for inclusion in the Unicode Standard. The data is used to support emoji characters in implementations, specifying which symbols are commonly displayed as emoji, how the new skin-tone modifiers work, and how composite emoji can be formed with joiners. The Unicode website now supplies charts of emoji characters, showing vendor variations and providing other useful information.

Some of the changes in Version 8.0 and associated Unicode technical standards may require modifications in implementations. For more information, see Unicode 8.0 Migration and the migration sections of UTS #10, UTS #39, and UTS #46.

by Richard Ishida at 18 June 2015 09:51 AM

June 17, 2015

ishida>>blog » i18n

UniView 8.0.0 available

Picture of the page in action.

>> Use UniView

Unicode 8.0.0 is released today. This new version of UniView adds the new characters encoded in Unicode 8.0.0 (including 6 new scripts). The scripts listed in the block selection menu were also reordered to match changes to the Unicode charts page.

The URL for UniView is now http://r12a.github.io/uniview/. Please change your bookmarks.

The github site now holds images for all 28,000+ Unicode codepoints other than Han ideographs and Hangul syllables (in two sizes).

I also fixed the Show Age filter, and brought it up to date.

by r12a at 17 June 2015 06:28 PM

June 15, 2015

Global By Design

When will more global websites support Arabic?

I read a brief report on digital Arabic content produced by the Wamda Research Lab, in partnership with Google and Taghreedat. A few data points jumped out at me, such as: By 2017 over half of the Arab world will have access to the Internet, an increase from the 32% that were online in 2012. Estimates suggest  … Read more

by John Yunker at 15 June 2015 07:15 PM

June 10, 2015

Global By Design

You Say .Sucks, I Say .Global: The flood of new domain names isn’t pretty but will create a truly global Internet

I sympathize with Internet old timers (such as myself) who look back wistfully at the good ol’ days, when the only decision you had to make when registering a new domain name was choosing between .com or .net. Today, there are more than 500 of these top-level domains from which to choose (with 400 more  … Read more

by John Yunker at 10 June 2015 05:13 PM

Wikimedia Foundation

Cx-suggestion-thumbnails.png

Cx-suggestion-thumbnails.png
The Content Translation Tool makes it easier to create new new Wikipedia articles from other languages. It is now available as a beta-feature in 148 Wikipedias. The tool now features an updated selector with image thumbnails for search results. Screenshot by Runa Bhattacharjee, freely licensed under CC0 1.0

Since our last blog post, much has happened in the world of Content Translation — a tool that makes it easier to translate Wikipedia articles into different languages. The Wikimedia Language Engineering team deployed as a beta-feature in January 2015 in the Catalan, Spanish and Portuguese Wikipedias; today, nearly 150 Wikipedias have access to the tool, and more than 5,000 articles have been created by more than 1,500 editors.

While on the one hand there are large Wikipedias, like English or German, where thousands of volunteers have written articles about millions of topics, there are over 100 smaller Wikipedias where a handful of volunteers are struggling to add more content. Translating from an existing article in another language is a common method adopted in such Wikipedias to create more content. Content Translation attempts to solve this rather daunting problem by simplifying the process, allowing editors to quickly create the first draft of the article and focus on improving the content. It includes an editing interface and translation tools that make it easy to adapt wiki-specific syntax, links, references, and categories. Machine translation support via Apertium is also available for a limited set of languages, which can considerably speed up the process; if it is currently missing for yours, we invite you to take our ongoing survey to test and provide feedback.

Even without machine translation, the tool has been used to translate from any of the available languages (i.e. from all Wikipedias) with features that allow automatic adaptation of links, images, references and categories. For instance, nearly 500 new articles have been created in the French Wikipedia using Content Translation and without machine translation.

New languages and feature improvements

At present, Content Translation is available on 148 Wikipedias as a beta-feature for logged-in users, including several large Wikipedias like French, Dutch and Polish. Being a beta-feature, only logged-in users can use it at present by enabling it from their preferences.

The tool presents a simple workflow—select the source language and article to translate, select the target language, translate the contents of the article, and publish it as a new page in the corresponding Wikipedia. For category adaptation, the corresponding category needs to exist in the target Wikipedia. Translators can also save the translations and work on it later.

Articles published using Content Translation in April and May 2015. Image by Pau Giner, freely licensed under CC BY-SA 4.0.

New translators who published articles using Content Translation in April and May 2015. Image by Pau Giner, freely licensed under CC BY-SA 4.0.

In the months of April and May, we focused on improving features that made it easy for users to start translating with Content Translation by quickly gaining access to it. We introduced a campaign that prompted users to try Content Translation instead, when they were creating a new article. Users could enable the feature directly from the campaign message screen and begin translating the page from another language. A call-out message was also added to the Contributions menu providing quick access to different kinds of contributions (including translations). As an outcome of these measures, we now see a sharp increase in the number of new articles being created every week by increasing number of new users (see images). We expect to get better insight into the usage numbers in the coming month.

Feature improvement highlights:

  • To prepare for deployment on wikis with Right-to-Left content, several bugs have been fixed.
  • Users will also see an improvement in the selector dialog, where results from articles searched are now displayed with a thumbnail and small description (see image).
  • The ULS input method has been integrated in the Content Translation editing interface
  • New articles created using Content Translation are now automatically linked through Wikidata

Deployment update and what’s coming next

In the coming month, we aim to continue adding Content Translation as a beta-feature to more Wikipedias so that more users can test the tool. This not only exposes special cases that we need to be aware of (like local gadgets or Wikipedia specific scripts) but also provides us with feature suggestions.

Upcoming features:

  • Improved link handling with provision for complex use-cases.
  • Redesigned statistics page with additional data.
  • Preliminary features for an integrated notification system using Echo, to better connect with our users

The Language team will be hosting two Content Translation workshops at Wikimania this year. You can sign up on the Wikimania website (here and here); it is open for all participants. You can read more about Content Translation on the project page and also in the new User Guide (translations are very welcome!).

Read more about Content Translation developments and other updates from the Language Engineering team in our monthly report. We would also like to invite everyone for our online office hour session on June 10 at 14:30 UTC.

Runa BhattacharjeeLanguage Engineering, EditingWikimedia Foundation

by Wikimedia Blog at 10 June 2015 04:17 AM

June 08, 2015

Global By Design

Global gateway fail: DeWalt

DeWalt greets visitors with a pull-down global gateway shown here: This type of landing page is not ideal in this day and age. Using geolocation (see Geolocation for Global Success), DeWalt could take the user directly to the localized website and display an overlay asking the user to confirm or change locale setting. But this is  … Read more

by John Yunker at 08 June 2015 08:55 PM

June 02, 2015

Global By Design

Country codes are maturing — but not retiring

Country codes are still adding registrations but the more developed markets are seeing a decline in growth rate. Shown below is a visual from the registry behind the .FR domain: Of course, AFNIC is keen to point out that the growth rate for country codes is still much higher than “legacy” domains like .com and  … Read more

by John Yunker at 02 June 2015 05:45 PM

May 30, 2015

Wikimedia Foundation

translatewiki

translatewiki
The Translatewiki.net project enables communities to localize open source software. It was recently used for a “Translation Rally” that engaged volunteers around the world to translate over 44,000 messages in nine days. Photo by Christian Mehlführer, CC BY-SA 3.0.

How can we engage volunteers to contribute in important yet monotonous tasks? Over the past year, Wikimedia Sverige (Sweden) has been experimenting with ways to strengthen its community on translatewiki.net — a little-known project that nevertheless benefits hundreds of millions of people each month.

Translatewiki is a platform for translating the texts that appear in open source software, including the MediaWiki software used on Wikipedia. These translations make it possible for you to get all the buttons and system messages on Wikipedia in your preferred language; it is preparatory work to make it as easy as possible for writers and readers to use Wikipedia and other open source software.

Translating technical messages is therefore a very important task, but it is often rather isolated and and independent work. Wikimedia Sverige aimed to change that, to make it fun to jointly produce an effort which differs from the regular activity, and therefore invited Translatewiki‘s volunteer translators to a “Translation Rally” for nine days in mid-May with a sum of 500 euros to be divided between all participants reaching more than 500 translations of some of the most important messages. This concept was originally developed by Wikimedia Nederland (Netherlands).

We initially aimed to complete the messages in MediaWiki’s core software—the central messages used on the Wikimedia projects. When finished, the participants could continue with 11 other selected projects. There are almost 65,000 messages to translate to each language, of which MediaWiki constitutes approximately 24,500. Some are only one word long (e.g. “Save”), while others may be several sentences long. As the translations are completed by volunteers, some languages ​​are almost completely translated—but others are almost entirely untranslated. Many even lack translations of the core messages. Participants were given the opportunity to either keep the money for themselves or donate them to Translatewiki‘s continued operation. The majority of the translations were made into non-European languages, but these languages also benefited; for example, hundreds of messages were translated into Swedish.

Number of edits during the Translation Rally in May 2015. Graph by Translatewiki.net, freely licensed under CC BY-SA 3.0.

Prior to the Translation Rally, an email was sent to all registered users asking them to join; this was an important step, as it brought in older users whose activity had dropped off over the years. During the rally’s nine days, the website’s activity was around four times higher than normal. 201 users contributed at least one new translation, and a massive 44,844 messages were added.

Sites using MediaWiki software are now easier to use in the 116 languages improved; it is clear that a much higher activity was achieved thanks to the Rally. However, most of the volunteers did not reach the minimum of 500 translations and couldn’t claim a slice of the 500 euros; 23 of them had valid claims and will split the prize. The winner with the most qualified translations are yet to be appointed.

A remaining question is if this type of activity has a positive or negative effect on the community in the long term. The benefit for community engagement is that people are invited and engaged in something new and exiting; you can create a noticeable buzz. However, there are potential risks when adding money or prizes into the mix. Will that reduce interest to participate in the long run, when there are no more prices? Can conflicts increase because of this? Will participants be more sloppy with their translations (this seem to have happened this time)? What can we then do to mitigate these risks? These types of predictions are notoriously hard to do without proper research, as different methods might have different problems and gains. We would greatly welcome more studies in this area.

The only thing we can say with some certainty right now is that for a limited cost, there has been a massive short-term positive effect, especially for languages spoken in poorer countries. From the graphs we developed, you can see that activity has regressed to its previous norm now that the rally ended.

The Translation Rally was organized and sponsored by Wikimedia Sverige, with a generous support from Internetfonden, and the rally itself was run by Siebrand Mazeland at the Wikimedia Foundation.

John AnderssonWikimedia Sverige

by Wikimedia Blog at 30 May 2015 02:11 AM

May 28, 2015

Internet Globalization News

Why Country Sites of International Companies are so Bad

The worst sites are usually not the truly local sites designed by local businesses or government agencies. Instead, the offenders often come from multinational corporations (small and large) that create country sites with horrible usability - and usually without a true understanding of the local market and users. via www.nngroup.com How can multinational companies solve this problem and get better country sites? By reversing the causes of the bad design: Don't let your local office throw away money to advertising agencies that don't understand Internet marketing. Instead, consider local sites as part of a global Internet strategy. Specifically: Document the design rationale for your website and your product line strategy, and ensure that local teams understand why the web team at headquarters does things in particular ways. Train local staff in web usability, Internet marketing, and other topics that will empower them to say no to inane design ideas from...

by blogalize.me at 28 May 2015 09:19 PM

May 27, 2015

Global By Design

No Ordinary Disruption: It’s time to reset intuitions

I was given a review copy of No Ordinary Disruption: The Four Global Forces Breaking All the Trends, which I read over the weekend. The authors are Richard Dobbs, James Manyika, and Jonathan Woetzel — all directors at the McKinsey Global Institute. Readers of this blog are not going to be surprised by some of the disruptions  … Read more

by John Yunker at 27 May 2015 03:26 PM

May 26, 2015

Global By Design

Hotels.com, Hotels.ng and the value of country codes

I read today about the Nigerian startup Hotels.ng and my first thought was why Hotels.com didn’t already own the Nigerian country code. After all, Hotels.com owns country codes for France and Italy and Japan, among others. But was apparently late to registering country codes for Germany and Netherlands — as well as Nigeria (Africa’s most populous country). Now,  … Read more

by John Yunker at 26 May 2015 03:24 PM

May 19, 2015

Global By Design

Global gateway fail: App Annie

I want to focus on App Annie because it appears the company is planning to significantly expand its global reach — and therefore needs a gateway suited to task. Currently, App Annie supports five languages. But you might not know this because the gateway is buried in the footer, as shown here: To App Annie’s  … Read more

by John Yunker at 19 May 2015 04:12 PM

May 15, 2015

Global By Design

The humans behind machine translation

Google Translate is the world’s most popular machine translation tool. And, despite predictions by many experts in the translation industry, the quality of Google Translate has improved nicely over the past decade. Not so good that professional translators are in any danger of losing work, but good enough that many of these translators will use Google  … Read more

by John Yunker at 15 May 2015 08:37 PM

May 12, 2015

Global By Design

Who needs BRIC when you have the Blue Banana?

Perhaps it’s human nature (or perhaps just savvy marketing) to think up new and unique ways of organizing our world. BRIC (Brazil, Russia, India, China) is one popular grouping. And did you know about MINT (Mexico, Indonesia, Nigeria, Turkey)? Or MIST (Mexico, Indonesia, South Korea, Turkey)? And if you think those groupings sound odd, consider CIVETS (Colombia, Indonesia, Vietnam,  … Read more

by John Yunker at 12 May 2015 05:35 PM

May 07, 2015

Global By Design

Greece gets an Internationalized Domain Name (IDN)

Greece has received string approval for an IDN, shown below in red: This brings to 35 the number countries with approved IDNs — and an impressive range of scripts, shown here: I’ve just updated the IDN map of the world. If you’d like to order a copy — or a custom variation —  contact me.

by John Yunker at 07 May 2015 07:10 PM

May 03, 2015

Global By Design

Translators Without Borders and the Wikipedia 100-language project

Translators Without Borders is an amazing organization of volunteer translators using their skills to make the world a better place. One project worth noting is an ambitious effort to translate valuable Wikipedia articles into 100 languages: The 100 x 100 Wikipedia Project envisions the translation of the 100 most widely read Wikipedia articles on health issues  … Read more

by John Yunker at 03 May 2015 03:13 PM

April 27, 2015

Global By Design

Will FedEx plus TNT equal an improved global website?

As FedEx closes its acquisition of TNT Express, I see an opportunity for FedEx to improve its global website. In the recent Web Globalization Report Card, among delivery services companies, FedEx finished dead last. TNT supports 37 languages, compared with the relatively paltry 27 languages that FedEx supports. Hopefully FedEx will embrace a new language baseline  … Read more

by John Yunker at 27 April 2015 05:28 PM

April 24, 2015

W3C I18n Activity highlights

Updated Working Draft: Language Tags and Locale Identifiers for the World Wide Web

Language Tags and Locale Identifiers for the World Wide Web describes the best practices for identifying or selecting the language of content as well as the the locale preferences used to process or display data values and other information on the Web. It describes how document formats, specifications, and implementations should handle language tags, as well as extensions to language tags that describe the cultural or linguistic preferences referred to in internationalization as a “locale”.

Changes in this update include the following: All references to RFC3066bis were updated to BCP 47 or to RFC5646 or RFC 4647 as appropriate.References to HTML were changed to point to HTML5. Imported and rewrote the text formerly containing in Web Services Internationalization Usage Scenarios defining internationalization, locale, and other important terms. Modified and reorganized the other sections of this document. Moved the Web services materials to an appendix.

by Richard Ishida at 24 April 2015 09:28 AM

April 23, 2015

Global By Design

Do your web developers know about Globalize?

Today, the JQuery Foundation has announced availability of Globalize 1.0: Globalize provides developers with always up-to-date global number formatting and parsing, date and time formatting and parsing, currency formatting, and message formatting. Based on the Unicode Consortium standards and specifications, Globalize uses the Common Locale Data Repository (CLDR), the most extensive and widely-used standard repository of  … Read more

by John Yunker at 23 April 2015 11:55 PM

April 08, 2015

Wikimedia Foundation

The Content Translation tool makes it easier to create new Wikipedia articles from other languages. You can now start translations from your Contributions link, where you can find articles missing in your language. Screenshot by Runa Bhattacharjee, freely licensed under CC0 1.0

The Content Translation tool makes it easier to create new Wikipedia articles from other languages. You can now start translations from your Contributions link, where you can find articles missing in your language. Screenshot by Runa Bhattacharjee, freely licensed under CC0 1.0
The Content Translation tool makes it easier to create new Wikipedia articles from other languages. You can now start translations from your Contributions link, where you can find articles missing in your language. Screenshot by Runa Bhattacharjee, licensed under CC0 1.0

Since it was first introduced three months ago, the Content Translation tool has been used to write more than 850 new articles on 22 Wikipedias. This tool was developed by Wikimedia Foundation’s Language Engineering team to help multilingual users quickly create new Wikipedia articles by translating them from other languages. It includes an editing interface and translation tools that make it easy to adapt wiki-specific syntax, links, references, and categories. For a few languages, machine translation support via Apertium is also available.

Content Translation (aka CX) was first announced on January 20, 2015, as a beta feature on 8 Wikipedias: Catalan, Danish, Esperanto, Indonesian, Malay, Norwegian (Bokmal), Portuguese, and Spanish. Since then, Content Translation has been added gradually to more Wikipedias – mostly at the request of their communities. As a result, the tool is now available as a beta feature on 22 Wikipedias. Logged-in users can enable the tool as a preference on those sites, where they can translate articles from any of the available source languages (including English) into these 22 languages.

Here is what we have learned by observing how Content Translation was used by over 260 editors in the last three months.

Translators

Number of users who enabled this beta feature over time on Catalan Wikipedia. Graph by Runa Bhattacharjee, CC0 1.0

To date, nearly 1,000 users have manually enabled the Content Translation tool — and more than 260 have used it to translate a new article. Most translators are from the Catalan and Spanish Wikipedias, where the tool was first released as a beta feature.

Articles

Articles published using Content Translation. Graph by Runa Bhattacharjee, CC0 1.0

Articles created with the Content Translation tool cover a wide range of topics, such as fashion designers, Field Medal scholars, lunar seas and Asturian beaches. Translations can be in two states: published or in-progress. Published articles appear on Wikipedia like any other new article and are improved collaboratively; these articles also include a tag that indicates that they were created using Content Translation. In-progress translations are unpublished and appear on the individual dashboard of the translator who is working on it. Translations are saved automatically and users can continue working on them anytime. In cases where multiple users attempt to translate or publish the same article in the same language, they receive a warning. To avoid any accidental overwrites, the other translators can publish their translations under their user page — and make separate improvements on the main article. More than 875 new articles have been created since Content Translation has been made available — 500 of which were created on the Catalan Wikipedia alone.

Challenges

When we first planned to release Content Translation, we decided to monitor how well the tool was being adopted — and whether it was indeed useful to complement the workflow used by editors to create a new article. The development team also agreed to respond quickly all queries or bugs. Complex bugs and other feature fixes were planned into the development cycles. But finding the right solution for the publishing target proved to be major challenge, from user experience to analytics. Originally, we did not support publishing into the main namespace of any Wikipedia: users had to publish their translations under their user pages first and then move them to the main namespace. However, this caused delays, confusion and sometimes conflicts when the articles were eventually moved for publication. In some cases, we also noticed that articles had not been counted correctly after publication. To avoid these issues, that original configuration was changed for all supported sites. A new translation is now published like any other new article and in case an article already exists or gets created while the translation was being done, the user is displayed warnings.

New features

Considering the largely favorable response from our first users, we have now started to release the tool to more Wikipedias. New requests are promptly handled and scheduled, after language-specific checks to make sure that proposed changes will work for all sites. However, usage patterns have varied across the 22 Wikipedias. While some of the causes are outside of our control (like the total number of active editors), we plan to make several enhancements to make Content Translation easily discoverable by more users, at different points of the editing and reading workflows. For instance, when users are about to create a new article from scratch, a message gives them the option to start with a translation instead. Users can also see suggestions in the interlanguage link section for languages that they can translate an article into. And last but not least, the Contributions section now provides a link to start a new translation and find articles missing in your language (see image at the top of this post).

In coming months, we will continue to introduce new features and make Content Translation more reliable for our users. See the complete list of Wikipedias where Content Translation is currently available as a beta feature. We hope you will try it out as well, to create more content

Runa Bhattacharjee, Language Engineering, Wikimedia Foundation

by Wikimedia Blog at 08 April 2015 05:10 PM

April 07, 2015

Global By Design

Starbucks: The best global retail website

For the 2015 Web Globalization Report Card, we studied 10 retail websites: Best Buy Costco GameStop Gap H&M IKEA McDonald’s Staples Starbucks Toys R Us UNIQLO Walmart Zara Out of those 10 websites, Starbucks emerged as number one. Here is a screen shot from the German site: McDonald’s leads the category in languages supported, with 39 (in  … Read more

by John Yunker at 07 April 2015 05:30 PM

April 06, 2015

Wikimedia Foundation

Group photo

Group photo
The Content Translation tool has made it a lot easier for Catalan Wikimedians to convert articles to and from different languages. Photo by Flamenc, freely licensed under CC BY-SA 3.0

Catalan Wikimedians are a very enthusiastic wiki community. In relation to the whole movement, we are mid-sized but one of the most active in terms of editors per millions of speakers.

Surprisingly Catalan, our mother language, was banished for more than 40 years. Thankfully, editors like to use wikis for digital language activism. With Wikipedia (Viquipèdia, in Catalan) we founded a digital space where we can freely spread our language without real life restrictions (governments, markets).

Almost 99% of Catalan speakers are bilingual and also speak Spanish. This means that content translation from Spanish Wikipedia happens frequently on our project. Some translate by hand, others use commercial platforms like Google Translate or freely licensed translation engines like Apertium. Some users even create their own translation bots, like the AmicalBot or EVA, which our community loves and uses often.

A few months ago, we heard news of the upcoming Wikimedia’s ContentTranslation tool, and we’re really happy to find that the very first language tests were planned between Spanish and Catalan. Our community responded to this news with great enthusiasm and we have been testing the tool for months now. The development team has kindly listened to our comments and demands, while implementing many of our shared recommendations.

At a personal level, I found the tool really helpful. It is easy to use and understand, and it greatly facilitates our work. I can now translate a 20- line article in less than 5 minutes, saving lots of time. Before, the worst part of translating articles was spending extra time translating reference templates and some of the wikicode. We understand the tool is not perfect yet, but nothing is perfect in a wiki environment: it is continuously being improved.

One of our community’s biggest challenges is updating different language wikis. We have good content about Catalan culture in the Catalan language, but we are not that good at exporting this content to other wikis. I personally hope that this tool can help us with both tasks.

I recommend that you try the ContentTranslation tool with an open mind and spend some time with it. Translate a few articles and if you find any bugs, please report them. When we say Wikipedia is a global project, we mean that it is multilingual, and this tool really helps us reach our shared vision to help every single human being can freely share in the sum of all knowledge.

Alex Hinojo, Amical Wikimedia community member

by Wikimedia Blog at 06 April 2015 10:08 PM

Global By Design

Adobe points to external localized tutorials

Adobe provides French, German and Japanese tutorials for Photoshop Elements. But what about other languages? Until the funding comes along for additional translation, Adobe directs users to tutorials created in Spanish, Polish, Dutch and Russian. Simple and smart. I don’t know what more software companies don’t do this. PS: Adobe ranked #9 overall in this year’s Web  … Read more

by John Yunker at 06 April 2015 05:20 PM

March 25, 2015

W3C I18n Activity highlights

Program published for W3C MultilingualWeb Workshop in Riga, 29 April

See the program. The keynote speaker will be Page Williams, Director of Global Readiness, Trustworthy Computing, Microsoft. She is followed by a strong line up in sessions entitled Developers and Creators, Localizers, Machines, and Users, including speakers from Microsoft, the European Parliament, the UN FAO, Intel, Verisign, and many more. The workshop is made possible with the generous support of the LIDER project.

Participation in the event is free. Please register via the Riga Summit for the Multilingual Digital Single Market site.

The MultilingualWeb workshops, funded by the European Commission and coordinated by the W3C, look at best practices and standards related to all aspects of creating, localizing and deploying the multilingual Web. The workshops are successful because they attract a wide range of participants, from fields such as localization, language technology, browser development, content authoring and tool development, etc., to create a holistic view of the interoperability needs of the multilingual Web.

We look forward to seeing you in Riga!

by Richard Ishida at 25 March 2015 08:28 AM

March 24, 2015

Global By Design

BMW & Chevrolet: The Best Global Automotive Websites

For the 2015 Web Globalization Report Card, we studied 14 automotive manufacturers and one supplier (Michelin). Audi BMW Chevrolet Ford Goodyear Honda Hyundai Land Rover Lexus Mercedes Michelin Mini Nissan Toyota Volkswagen Out of those 15 websites, BMW and Chevrolet emerged in a numerical tie for number one. BMW and Chevrolet both support an impressive 41 languages, in addition to  … Read more

by John Yunker at 24 March 2015 04:25 PM

March 16, 2015

Global By Design

Why you should be using geolocation for global navigation

In the 2015 Web Globalization Report Card, slightly more than half of the websites studied use geolocation specifically to improve global navigation. This is up significantly from just a few years ago. Geolocation is the process of identifying the IP address of a user’s computer or smartphone and responding with localized content or websites. Companies that  … Read more

by John Yunker at 16 March 2015 11:12 AM

March 14, 2015

Global By Design

Armenia gets an IDN: հայ

This is not exactly breaking news, but Armenia now has an IDN: հայ Here it is in my fast-evolving IDN map: This means that 34 countries now have delegated IDNs.  

by John Yunker at 14 March 2015 08:59 PM

March 11, 2015

W3C I18n Activity highlights

Unicode 8.0 Beta Review

The Unicode® Consortium announced the start of the beta review for Unicode 8.0.0, which is scheduled for release in June, 2015. All beta feedback must be submitted by April 27, 2015.

Unicode 8.0.0 comprises several changes which require careful migration in implementations, including the conversion of Cherokee to a bicameral script, a different encoding model for New Tai Lue, and additional character repertoire. Implementers need to change code and check assumptions regarding case mappings, New Tai Lue syllables, Han character ranges, and confusables. Character additions in Unicode 8.0.0 include emoji symbol modifiers for implementing skin tone diversity, other emoji symbols, a large collection of CJK unified ideographs, a new currency sign for the Georgian lari, and six new scripts. For more information on emoji in Unicode 8.0.0, see the associated draft Unicode Emoji report.

Please review the documentation, adjust code, test the data files, and report errors and other issues to the Unicode Consortium by April 27, 2015. Feedback instructions are on the beta page.

See more information about testing the 8.0.0 beta. See the current draft summary of Unicode 8.0.0.

by Richard Ishida at 11 March 2015 12:29 PM

March 04, 2015

Global By Design

Google to the Internet: Go mobile or watch your sales rank fall

Four years ago, for the Web Globalization Report Card, I began noting (and rewarding) those websites that supported mobile devices. Even then one could easily see the virtual grounds shifting in favor of mobile devices. But at the time, only about 20% of the websites studied supported mobile devices. In this year’s Report Card, the majority of websites are  … Read more

by John Yunker at 04 March 2015 03:14 PM

February 26, 2015

W3C I18n Activity highlights

Speaker deadline for Riga MultilingualWeb Workshop is Sunday, 8 March

We would like to remind you that the deadline for speaker proposals for the 8th MultilingualWeb Workshop (April 29, 2015, Riga, Latvia) is on Sunday, March 8, at 23:59 UTC.

Featuring a keynote by Paige Williams (Director of Global Readiness, Trustworthy Computing at Microsoft) and sessions for various audiences (Web developers, content creators, localisers, users, and multilingual language processing), this workshop will focus on the advances and challenges faced in making the Web truly multilingual. It provides an outstanding and influential forum for thought leaders to share their ideas and gain critical feedback.

While the organizers have already received many excellent submissions, there is still time to make a proposal, and we encourage interested parties to do so by the deadline. With roughly 150 attendees anticipated for the Workshop from a wide variety of profiles, we are certain to have a large and diverse audience that can provide constructive and useful feedback, with stimulating discussion about all of the presentations.

The workshop is made possible by the generous support of the LIDER project and will be part of the Riga Summit 2015 on the Multilingual Digital Single Market. We are organizing the workshop as part of the Riga Summit to strengthen the European related community at large. Depending on the number of submissions to the MultilingualWeb workshop we may suggest to move some presentations to other days of the summit. For these reasons we highly recommend you to attend the whole Riga Summit! See the line-up of speakers already confirmed for the various events during the summit.

For more information and to register a presentation proposal, please visit the Riga Workshop Call for Participation. For registration as a regular participant of the MultilingualWeb workshop or other events at the Riga Summit, please register at the Riga Summit 2015 site.

by Richard Ishida at 26 February 2015 11:30 AM


Contact: Richard Ishida (ishida@w3.org).