Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 123 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 129 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 136 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 170 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 200 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 206 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 231 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 242 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 254 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 293 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 351 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 352 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 353 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 354 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 355 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 571 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 197 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 202 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_connect_db.inc.php on line 27 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/sessions/_session.class.php on line 222 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/generic/_genericelement.class.php on line 112 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 428 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 437 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/collections/_category.funcs.php on line 390 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 549 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 563 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist.class.php on line 602 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_item.class.php on line 2952 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 306 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 120 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 796 Deprecated: Function ereg() is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 413 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/skins/_skin.funcs.php on line 71
background-break and border-break into box-break; fantasai to draft proposal into Editor's Draft for discussion.min() and max() functions to calc(); min() and max() may also appear as standalone functions, their contents parsed as if wrapped in calc().
tcworld magazine has published an article by Tony Graham about the recently published W3C Note, Requirements for Japanese Text Layout.
In order to help ensure interoperable W3C Widget runtimes, Vodafone are kindly hosting the first ever W3C Widget test cases creation event. The dates are set for the 2009-09-21 (Monday) till 2009-09-23 (Wednesday) and the venue will be in Düsseldorf in Western Germany.
Interested in Web Widgets? Tired of fragmentation? Able to write some tests? Please join us by registering for the event.
The aim is to complete the Widget test suite. Once registering to prepare for the event, please review the test plan and existing tests. A contribution guide and event details will follow soon.
Continuing the work of repackaging the tests in the Internationalization test suite around 87 more tests, this time relating to right-to-left and bidirectional text have been updated. Each of the 87 tests are implemented for HTML 4.0, XHTML 1.0 served as text/html, XHTML 1.0 served as XML, and XHTML 1.1 served as XML (ie. totally around 350 test cases).
There are also tables covering the results of the tests, and summaries of the findings. Most of these are new. The tests were run on recent versions of major browsers.
The tests and results are linked from here:
(Note that the vertical text tests are not included in this announcement, since they are still in the early stages of development.)
Scientific research is becoming both increasingly interdisciplinary, and dependent for dissemination on the Web. Yet the form of the discourse has remained for the most part, a digital analog of the paper research article. This situation persists despite the emergence of Web 2.0 paradigms (blogs, wikis, online communities), application of Semantic Web technologies to problems in biomedicine, and the introduction of virtual research environments in certain areas. We will bring together experts in semantic technology, scientific informatics, virtual research environments, Web communities and scientific publishing to contribute to the development of new thinking on how scientific research can be communicated, characterized, annotated, searched and shared on the Web.
Details about the workshop including logistics, the deadline for paper submissions, and program committee members are available on the Web site for the workshop.Scientific research is becoming both increasingly interdisciplinary, and dependent for dissemination on the Web. Yet the form of the discourse has remained for the most part, a digital analog of the paper research article. This situation persists despite the emergence of Web 2.0 paradigms (blogs, wikis, online communities), application of Semantic Web technologies to problems in biomedicine, and the introduction of virtual research environments in certain areas. We will bring together experts in semantic technology, scientific informatics, virtual research environments, Web communities and scientific publishing to contribute to the development of new thinking on how scientific research can be communicated, characterized, annotated, searched and shared on the Web.
Details about the workshop including logistics, the deadline for paper submissions, and program committee members are available on the Web site for the workshop.
As part of the ongoing work of repackaging the tests in the Internationalization test suite around 70 tests relating to character encodings and language declarations have been updated. Each of the 70 tests are implemented for HTML 4.0, XHTML 1.0 served as text/html, XHTML 1.0 served as XML, and XHTML 1.1 served as XML (ie. totally around 280 test cases).
There are also tables covering the results of each test, and summaries of the findings. The tests were run on recent versions of major browsers.
The tests and results are linked from here:
Thanks to Dénes Kohn, Metaphraser - Translation Company, the following articles have been translated into Hungarian. These are our first Hungarian translations on the Internationalization subsite.
Honosítás és Internacionalizálás (Localization vs. Internationalization)
Nemzetközi és többnyelvű weboldalak (International & multilingual web sites)
Szövegméret a fordításban (Text size in translation)
[search key: qa-i18n] [search key: qa-international-multilingual] [search key: article-text-size]
0 0 rgba(0,0,0,0.0).::before/::after (but not other pseudo-elements).rgba() transitions premultiplied or not.
The Internationalization Core Working Group has published an updated Working Draft of Best Practices for Authoring HTML: Handling Right-to-left Scripts.
This document provides advice for the use of HTML markup and CSS style sheets to create pages containing languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
The Working Group believes this document is complete and does not anticipate any substantive changes. This draft is provided as a last chance for review and feedback before publication as a Working Group Note.
Please send comments on this document to www-international@w3.org (publicly archived) by 28 July 2009.
Editor: Richard Ishida. [search key: tr-bp-bidi]
Thanks to the Spanish Translation Team, Spanish Translation US, the article "Setting the HTTP charset parameter" has now been translated into Spanish. [search key: article-o-http-charset]
Thanks to K. Wiśniewski the Getting Started article "Language on the Web" has now been updated in Polish. [search key: gs-language]
The Mobile Web Best Practices Working Group (BPWG) and the WAI Education and Outreach Working Group (EOWG) published the W3C Working Group Note: Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG). People with disabilities using computers have similar interaction limitations as people without disabilities who are using mobile devices. This note describes the similarities and differences between the requirements Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Following these two guidelines makes your Web content more accessible to everyone regardless of situation, environment, or device. Designing the guidelines together, instead of separately, can make the process more efficient. This note includes the following pages:
Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices.
FAQ-based article: If I'm unable to use markup to correctly order bidirectional text, what can I do?
By Richard Ishida, W3C. [search key: qa-bidi-unicode-controls]
This tutorial was updated to incorporate changes made to the article What you need to know about the bidi algorithm and inline markup, but various additional changes were made, including a new approach to handling examples. For a detailed list of changes read the full post.
Translators should consider retranslating the whole tutorial. [search keys: tutorial-bidi-xhtml]
The title was changed from 'Creating (X)HTML Pages in Arabic & Hebrew' to 'Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts'.
This article was revised to provide more clarity. More examples were added, and a new approach was taken, using images for examples and providing links to live code.
The term 'directional context' was replaced with 'base direction', the meaning and impact of that was expressed better. It also shows a little more clearly the types of problem the bidi algorithm needs help with, and how the proposed solutions related to each other.
This article was revised substantially.
Translators should consider retranslating the whole article. [search keys: article-inline-bidi-markup]
This article was revised to provide more clarity. More examples were added, and a new approach was taken, using images for examples and providing links to live code.
The term 'directional context' was replaced with 'base direction', the meaning and impact of that was expressed better. It also shows a little more clearly the types of problem the bidi algorithm needs help with, and how the proposed solutions related to each other.
The Introduction to W3C's Mobile Web Best Practices course has been running successfully since the beginning of June and will come to an end later this month. The current participants have formed an active community with a bunch of shared bookmarks and an active Twitter feed.
If you'd like to learn more about how to make your content available on the mobile channel, this course is for you! Lead by members of the MWI team, you'll:
Registration is now open for two versions of the course:
Details of the course content, who will benefit from it most, and links to the registration options are available.
The Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group have published Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) as a final W3C Working Group Note.
The groups encourage people to start by reading Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices, which shows how design goals for accessibility and mobile access overlap. A third document, Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities, provides examples of barriers that people (without disabilities) face when interacting with Web content via mobile devices, and similar barriers for people with disabilities using desktop computers.
The CSS Working Group has just published a Last Call Working Draft of the CSS Multi-column Layout module Level 3. This module defines properties to flow content into multiple columns, a common layout feature in print publications such as newspapers. Major changes since the last publication include changes to the syntax of column-breaking controls and an example of text wrapping around floats in a later column.
The deadline for comments is 1 October 2009. This is an unusually-long Last Call period because we want to encourage a wider review of the module and to make sure implementors are ready for everything in the draft to be locked down for CR. Please send comments to www-style@w3.org with [css3-multicol] and your comment topic in the subject header. (And if you insist on posting your comments elsewhere, at least have someone forward them there. Seriously.)
The Workshop will take place in Arlington, Virginia, on the 5-6 October, 2009. The Workshop is co-organized by W3C and XBRL International, and is hosted by FDIC.The goal of this workshop is to identify opportunities and challenges for interactive access to financial data expressed in XBRL and related languages, and the broader opportunities for semantic technologies. What are the use cases? Who are the stakeholders? What are the potential roadblocks and how can they be addressed? How can new applications be created based upon integrating XBRL with other sources of information?
The main outcome of the workshop will be the publication of a report that will serve as a guide for further work in both W3C and XBRL International.
The MW4D IG held its 20th teleconference on June 29th 2009.
The approved minutes are available at http://www.w3.org/2009/06/29-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
Version 1.2 of the W3C mobileOK Checker, released on Tuesday, helps Web authors focus on the failures that most affect the mobile-friendliness of their content, and returns the POWDER document Web authors may use as the basis of a mobileOK® conformance claim.
The reports returned by the mobileOK Checker can be long. That's not a bad thing, failure points need to be clarified. That said, scrolling over a long list of details is a tedious process and does not reveal the big picture. The new version adds unobtrusive (as in "works fine when Javascript is not enabled") Javascript to hide/show details. Details are hidden by default, simply click on a failure message to reveal its details!
A missing width attribute on an img element? That's a failure. Using frames? That's a failure. Obviously, the former case only slightly affects the mobile-friendliness of the page, while some mobile browsers won't even be able to render the page in the latter case. And yet both failures looked alike in the report, leaving the difficult task to evaluate the impact of a failure on the overall mobile-friendliness of the page to the reader.
Each failure now comes with a severity level:
Web authors who only have limited time available to fix failures may want to focus on the most severe failures first. The "Where to start..." section near the top of the report lists the top 3 failures to address right away.
So your content is mobileOK? Congratulations! You may now wish to identify your content as mobileOK conformant. The Mobile Web Best Practices Working Group recently published the W3C mobileOK Scheme 1.0 note. It provides an overview of the mobileOK scheme and explains in particular how to claim mobileOK conformance.
One way to make such a claim is to use POWDER. When the page is mobileOK, the mobileOK Checker now returns a POWDER document you may use to advertise that the page is mobileOK®. For instance, the mobileOK checker returns the following POWDER document when http://www.w3.org/Mobile/ is checked:
<?xml version="1.0"?>
<powder xmlns="http://www.w3.org/2007/05/powder#">
<attribution>
<issuedby src="http://www.w3.org/data#W3C" />
<issued>2009-07-03T08:37:21Z</issued>
<supportedby src="http://validator.w3.org/mobile/" />
</attribution>
<dr>
<iriset>
<includeresources>http://w3.org/Mobile/</includeresources>
</iriset>
<descriptorset>
<typeof src="http://www.w3.org/2008/06/mobileOK#Conformant" />
<displaytext>The page is mobileOK</displaytext>
<displayicon src="http://www.w3.org/2005/11/MWI-Icons/mobileOK.png" />
</descriptorset>
</dr>
</powder>
For more information on POWDER, please refer to the POWDER Primer.
A few other features compose this summer release, such as the size of each resource that composes the page, or the repartition of points lost per severity level. The complete change log is detailed in the What's new? page.
Feedback welcome!
A new extension to the W3C mobileOK open source library is available that can be used to validate pages served via the file URI scheme. The W3C mobileOK open source Java library has been developed in such a way that it is very easy to extend. We strongly encourage people to extend this library so that a better infrastructure is provided to designers for creating mobile-friendly content.
The mobileOK Basic Tests 1.0 Checker library provides a reference implementation of the tests specified in the W3C mobileOK Scheme 1.0. This scheme requires that pages are served via HTTP protocol, however there might be some cases where validating pages that are stored locally would be useful. Therefore, this new extension has been created and can be used to validate pages served via file URI scheme. The extension is designed and implemented in a way that does not affect the basic reference implementation. It is also important to note that validating pages only with this extension does not guarantee that the page is mobileOK as some tests require HTTP connection. This extension has to be used in-coordination with the W3C mobileOK Checker and does not replace the core mobileOK library.If you want to use this extension with the main library then you need to download and install it.
A technical documentation explains in detail how this extension can be installed and used.
This extension has been developed as part of the UK EPSRC funded RIAM (Reciprocal Interoperability of Accessible and Mobile Webs) project with the help of the Mobile Web Best Practices Checker Task Force.