Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Derek Featherstone - More reasons why we don’t use accesskeys #7

Open
3 of 7 tasks
fititnt opened this issue Aug 29, 2016 · 0 comments
Open
3 of 7 tasks

Derek Featherstone - More reasons why we don’t use accesskeys #7

fititnt opened this issue Aug 29, 2016 · 0 comments
Assignees
@rcgivisiez
Labels
traducao traducao-autorizada traducao-bloqueado:4-resp-revisao traducao-bloqueado:4-resp-traducao

Comments

@fititnt
Copy link
Member

fititnt commented Aug 29, 2016 •
edited
Loading

Link do original: http://john.foliot.ca/more-reasons-why-we-dont-use-accesskeys/
Link da tradução:http://historia.pt.webiwg.org/especialista/derek-featherstone/futuro-das-accesskeys/
Arquivo da tradução: https://github.com/webiwg/historia-web-pt/blob/master/especialista/derek-featherstone/mais-razoes-de-nao-usarmos-accesskeys/index.md
Descrição: The topic of accesskeys regularly appears on mailing lists, forums, and other arenas. Developers ask what the concensus is, and the answer is — there isn’t one. We believe that the functionality accesskeys provide is worthwhile, but their implementation and standardization leave something to be desired.
Existe traduções em português: não investigado

Ações

  • Definir pertinência
  • Descobrir se é necessário autorização prévia para traduzir
  • Caso seja necessário, solicitar autorização para traduzir
  • Adicionar versão original ao repositório
  • Definir duas ou mais pessoas para traduzir original
  • Completar tradução para português
  • Revisar tradução feita
@rcgivisiez rcgivisiez self-assigned this Sep 6, 2016
@rcgivisiez rcgivisiez mentioned this issue Sep 6, 2016
Open
7 tasks
fititnt added a commit that referenced this issue Oct 6, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, adicionado HTML original
381e68a
@fititnt fititnt mentioned this issue Oct 6, 2016
Merged
fititnt added a commit that referenced this issue Oct 6, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, convertido para markdown bruto; usado co…
458dcfb 
…mando: pandoc _original.html -f html -t markdown_strict --wrap=auto --columns=80 -o index.md
fititnt added a commit that referenced this issue Oct 6, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, reformatado semimanualmente com fititnt/…
e3e2afa 
…webiwg-format
fititnt added a commit that referenced this issue Oct 8, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, formatacao de texto em linhas por frase
6809c38
fititnt added a commit that referenced this issue Oct 8, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, identacao de demais textos, tags <kbd>, …
ac4cda9 
…remoção de html desnecessário
fititnt added a commit that referenced this issue Oct 8, 2016
@fititnt
#6 #7 #8 #9 #10: preparação, reorganização de pastas, 3 textos são de…
119145f 
… Derek Featherstone
fititnt added a commit that referenced this issue Oct 8, 2016
@fititnt
Merge pull request #24 from webiwg/preparacao-john-foliot
a81f842 
#6 #7 #8 #9 #10: Preparação de tradução de 5 artigos de John Foliot
@fititnt fititnt changed the title John Foliot - More reasons why we don’t use accesskeys Derek Featherstone - More reasons why we don’t use accesskeys Oct 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rcgivisiez rcgivisiez

Labels
traducao traducao-autorizada traducao-bloqueado:4-resp-revisao traducao-bloqueado:4-resp-traducao
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fititnt @rcgivisiez