W3C home > Mailing lists > Public > www-international@w3.org > October to December 2016

[html] Issue: Strategy for translations of HTML5 spec with tracking of updates marked as meta

From: chaals via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Oct 2016 01:49:53 +0000
To: www-international@w3.org
Message-ID: <issues.labeled-176919659-None-sysbot+gh@w3.org>
chaals has just labeled an issue for https://github.com/w3c/html as 

== Strategy for translations of HTML5 spec with tracking of updates ==
Hello, my name is Emerson and, with assistance already confirmed 
willing partner, we want to translate  [HTML5: Techniques for 
providing useful text 
 but the most recent version points to W3C CR HTML 5.1. I haven’t 
found any updated reference procedures  about translation in a way 
that provides for tracking of updates on the official specification 
like [w3c/html](https://github.com/w3c/html). For now we would like to
 cherry-pick this part, and in following months some others involving 
accessibility and semantics.

**This issue is also a suggestion to stimulate translation to new 
languages HTML5+ oficial specification**, and go beyond just 
non-normative "summarized" versions. Only [russian translation is 
disponible for 

## Example of why is important translations of official documentation

I am familiar with English, but that’s not true to a good portion of 
the people around the world. And even for those who are able to speak 
English, some lack knowledge about technical english, particularly 
semantics and accessibility.

We will start with the Portuguese speaking community, first in Brazil 
and then worldwide.

The [latest version of HTML specification translated to portuguese is 
nearly 17 years 
 The closest [translation for modern HTML5 "official" specification 
from W3C 
Brasil](http://www.w3c.br/pub/Cursos/CursoHTML5/html5-web.pdf) is at 
best incomplete about new HTML5 semantics. Documents like this and 
other non-normative references are perceived as prescriptive when 
there is no official documentation, being used as reference in 
courses, lectures and by professionals. This is a problem because who 
learns something incomplete doesn’t even question its validity, 
thinking that that is an “absolute truth”, since it was said by an 

This case is about Portuguese-speaking countries, but may apply to all
 those who are not native English speakers. This maybe that's why #33,
 whatwg/html#83 and features are dropped from HTML5.1, not for lack of
 technical capability of web developers, rather than they never 
knowing of its existence since it lacks the proper documentation.

## About what we have interest in know

_For now, me and my partner partner would like to translate just small
 part of the HTML5.1 spec, but maybe in next months, with sufficient 
help or even with less people but crowdfunding us group will make it 
all. We have another translations to do it too._

**1. Which strategy tend to be a good one for make translation in a 
way that provides for tracking of updates on the official 
specification like this one?**

**2. At 14 set 2016, which branch would be better to start 

**3. When HTML 5.1 will  be “ready?**

**4. If groups like mine are interested in translating, can W3C 
International help start with things about how to setup travis, review
 if the way branchs/commits are managed is counterproductive, etc?** 
Not the translation, _how_ to manage it in a sane way to permit a 
HTML5.2 translation later

## About the group

For now, we are a small self-organized nonprofit working group at 
@webiwg (http://www.webiwg.org/en/). 

See https://github.com/w3c/html/issues/588
Received on Wednesday, 19 October 2016 01:50:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:11 UTC