-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tradução para Português #4
base: traducao-pt-final
Are you sure you want to change the base?
Conversation
…ta about the language(s) of the intended audience
…panhamento de alterações; B. Agradecimentos
Tenho especial dúvida quanto ao nome título h2 em 5b4257a#diff-eacf331f0ffc35d4b482f1d15a887d3bR253 <!--
NT: Estava "W3C Working Group Note 03 June 2014". Preciso de ajuda para ter certeza se traducao para
"Observação de W3C Working Group em 3 de junho de 2014" é a ideal (@fititnt, 2016-09-29 11:24)
--> |
…s Reserved." para "Todos os direitos reservados.";
@@ -1,9 +1,9 @@ | |||
<!DOCTYPE html> | |||
<html lang="en" dir="ltr" typeof="bibo:Document w3p:NOTE" about="" property="dcterms:language" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A comment from who comes here from w3c/html#588 (comment)
A better example is
Specifying the language of content is useful for a wide number of applications,
from linguistically-sensitive searching to applying language-specific display properties.
In some cases the potential applications for language information are still waiting for implementations to catch up, whereas in others it is a necessity today.
Adding markup for language information to content is something that can and should be done as content is first developed.
If not, it will be much more difficult to take advantage of any future developments.
and not
Specifying the language of content is useful for a wide number of applications, from
linguistically-sensitive searching to applying language-specific display properties.
In some cases the potential applications for language information are still
waiting for implementations to catch up, whereas in others it is a necessity
today. Adding markup for language information to content is something that
can and should be done as content is first developed. If not, it will be much
more difficult to take advantage of any future developments.
We have other texts that have a better line break by sentences, but this one, that was originally used as example, is not a good one.
A better diff is on this link webiwg/acessibilidade-web-pt@a449b72#diff-c7977ccbd401f475c5dff983d52c84d1R134
…e depois da tradução
O ramo "master" deve ter sempre a ultima versão do ramo de trabalho. Esse pull request serve para usarmos a ferramenta do github para ficar comparando com relação ao original.
A versão do ramo
traducao-pt-final
neste momento contém exatamente a versão original em inglês, porém o código foi identado. o PR #1 foi cancelado porque isso não tinha sido feito