Closed Bug 232372 Opened 22 years ago Closed 21 years ago

There is no Brazilian Portuguese Translation to this letter

Categories

(Tech Evangelism Graveyard :: Portuguese, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vmedina, Assigned: vmedina)

References

()

Details

Attachments

(3 files, 5 obsolete files)

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i586; pt-BR; jpeg;q=0.6) Gecko/20031007 I am a member of a Mozilla users mail list linked to the Mozilla.org.br project and we have plenty of mail from persons that hava reached websites that don't show correctly in mozilla. One of this user pointed this letter and i started to translate it. Reproducible: Always Steps to Reproduce: 1. 2. 3. I already have this page up and running. I would like to contribute with this file to the mozilla project. Thanks!
Comment on attachment 140025 [details] My Brazilian Portuguese translation to this letter I hope that you like the translation <vmedina@click21.com.br>
Component: User → Portuguese
Product: Documentation → Tech Evangelism
hmm. Not sure what is the right component for this bug, so moving to mozilla.org: webmaster.
Assignee: rlk → endico
Component: Portuguese → webmaster@mozilla.org
Product: Tech Evangelism → mozilla.org
Version: unspecified → other
what character encoding is the letter in? I'm seeing gibberish
Assignee: endico → bc
Attachment #140025 - Attachment is patch: false
Attachment #140025 - Attachment mime type: text/plain → application/x-bzip2
had the wrong mime-type on it. It's a bzip2'd tarball.
I'm not shure if it was necessary but it needed some files of an folder. i choose bzip2 for having a strong compress rate. Sorry if it is not the right thing to do. It is my first time!
that's fine (I think). What happened is you checked the "patch" checkbox when uploading it instead of letting it detect the filetype. The patch checkbox forces the filetype to text, so it was trying to show us a text file instead of giving us a file download. Patch is used for files generated by the "diff" program. No big deal though, now you know for next time. :)
Vinicius, thanks! Some comments: link to the existing letter-en.css file since you have not made any specific pt changes. If you do need pt specific changes or would like to clone the en version into a pt version, that is ok but please just put the css file in the same directory as was done for the other letters. Please update the title which contains "Technical Letter (english)" to mention Portuguese instead of English. Please add a lang attribute for pt to the html tag. Upload another version with the css and other changes. we will need to find another Portuguese speaker to review this. Marcio, can you look at this?
Assignee: bc → vmedina
Blocks: 86690
Component: webmaster@mozilla.org → Portuguese
OS: Linux → All
Product: mozilla.org → Tech Evangelism
Hardware: PC → All
Summary: There is no Brazilian Portuguese Ttranslation to this letter → There is no Brazilian Portuguese Translation to this letter
Version: other → unspecified
Kiko might be able to look at it, too
I will be doing that changes tonight. I catch up almost everything, but i can't figure this "Please add a lang attribute for pt to the html tag.". Wich tag i would add. something like this "<HTML LANG=pt-BR>"? (In reply to comment #8) > Vinicius, thanks! > > Some comments: > > link to the existing letter-en.css file since you have not made any specific pt > changes. If you do need pt specific changes or would like to clone the en > version into a pt version, that is ok but please just put the css file in the > same directory as was done for the other letters. > > Please update the title which contains "Technical Letter (english)" to mention > Portuguese instead of English. > > Please add a lang attribute for pt to the html tag. > > Upload another version with the css and other changes. > > we will need to find another Portuguese speaker to review this. Marcio, can you > look at this?
Ok i will do this. Thanks
I don't need to change the css, so it's not included this time. I used the css stylesheet from the en language. Added the lang=pt-BR, using language and country code (because a long list of countries use portuguese as they language and each of then speak and write diferently, so i think it was a good thing to use the country code), and translate the title too. If something still isn't right just tell me.
Attachment #140025 - Attachment is obsolete: true
Thanks! All of my issues have been addressed. All we need now is someone to review the letter's contents. Marcio? Kiko?
I'll take a look at this asap (I'm a bit overwhelmed by worka at the moment).
Is this a dupe of bug 142494 ? Maybe we can merge the 2 letters... to me both are good go.
good to go
Bug 142494 got marked fixed without getting checked into www.mozilla.org. Should we merge them or simply list both? Are they sufficiently different?
I think merging is better, they are very similar.
(In reply to comment #18) > Bug 142494 got marked fixed without getting checked into www.mozilla.org. Should > we merge them or simply list both? Are they sufficiently different? The only difference that those 2 have is what was asked by you bob. In the text not was changed, so i marked the first obsolete. The letter that is most up-to-date is the second.
Hi Vinicius, we are talking about another translation of this same letter, present on bug 142494
Ok, someone create a merged version and I will check it in.
(In reply to comment #21) > Hi Vinicius, we are talking about another translation of this same letter, > present on bug 142494 After we talked on the list i realized that! I was a little sleepy when i read this. So what will happen with my translation? Will be combined with the other? Sorry i don't made a decent search to find out if i was doing such a mess. If the decision is for the combination it will be a honor to comtribute.
So, I think we should mark it as duplicate.
(In reply to comment #24) > So, I think we should mark it as duplicate. > And how that affect the translation that i have done?
Vinicius, lets use your letter as a base, and improove it with parts of the other, we can do this here or attach your letter on the other bug and continue, for me it doesnt matter. Your work will not be waste.
(In reply to comment #26) > Vinicius, lets use your letter as a base, and improove it with parts of the > other, we can do this here or attach your letter on the other bug and continue, > for me it doesnt matter. Your work will not be waste. That is really my only concern on this matter is of the waste of my work. I tink all the rest is fine.
I've made some changes to the Vinicius's translation and I'm sending a 'comented' diff, explaining my thoughs and why's on it. Mostly small things. Really my two cents. The comments themselves are in portuguese, as they are directed to a portuguese speaker reviewer. If this is unfit, please let me know. The real 'patch' (without coments) will follow.
Attached file Comments on the diff of bruno abdon (obsolete) —
I have submited this text file with some comments on Bruno's correction. It's just comments, because it was to large for a comment. If it is worng tell me. bye!
That is what i liked and disliked on the commented diff that bruno abdon has send. Why a dislike of some things is explained om my comment on his diff.
More comments on the ongoing translation. The points where we agreed were striped off. We are still discussing in portugues, as it would be too weird discuss an english to portuguese translation (made by portugues speakers) in english. I dont still know how it fits in the mozilla bugzilla etiquette, but... as nobody has complained yet... :)
It is fine with me. Just let me know when you are finished and what you would liked checked in.
(In reply to comment #31) > Created an attachment (id=140861) > More comments on the ongoing translation. > > More comments on the ongoing translation. The points where we agreed were > striped off. > > We are still discussing in portugues, as it would be too weird discuss an > english to portuguese translation (made by portugues speakers) in english. I > dont still know how it fits in the mozilla bugzilla etiquette, but... as nobody > has complained yet... :) Hey Bruno! I'm having a trouble with time, specially the lack of it, so for look and repair the latest letter i'm taking the weekend to do this. I'm having some troubles with bluefish(my html editor of choice) someone have some other sugestion of editor, for gnome, i would like (unless it is quanta that i dislike). So, for now is it. I will be checking this site from times to times, and will be answering everything. But large things only on the weekends. Hope it's not a bad thing, i know that it is a delay for the resolution of this bug and that it's not a god thing, but is better than doing some things (like doing the latest repair of the translation, and that is why , bruno, i do forget some of the things we agreed :) sorry friend!) with the mind in the dream land. :) hope you all understand my point of view. If you don't think i'm right please do tell me and i will try to work the things out. Bye everyone!
This is the latest technical letter. Everything next in this post is in portuguese. []s! ------------- Portuguese Readers Only :) ----------------------------------------- Agora vou responder aqui, afinal só nove comentários dá :) . Sobre estarmos fazendo uma tradução e sermos fiéis ao autor, acho que temos uma fidelidade maior, compartilhada obviamente com o autor, que é com a comunidade. E se para termos uma maior abrângência em nossa lingua for necessário adaptar SEM SAIR DOS RUMOS DA CARTA acho que deve ser feito. Ainda mais quando são pequenos detalhes linguísticos e técnicos. Onde eu não modifiquei mas concordei foi por puro cansaço quando corrigi. Conheço, e usava, esta prática sombria. :P Mas aí eu conheci o UTF-8 e minha vida mudou.:P Mas a sério agora, eu acho que não foi você que viu mas no topo da página temos uma coisa que eu gostaria de ressaltar: <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> Que manda o navegador alvo usar UTF-8. Achei muito melhora ativar essa função, do que ficar lotando o código dessas gambiarras que são os &atilde (se bem me lembro) que são comuns no Composer e em outros editores. Aqui no meu mozilla rodou bem! Sobre o IMHO nda que digitar define: IMHO no google não tenha resolvido! :P 1) Relatorio vs Relatorios Esqueci, mudei agora 2) Exemplos Funcionais Minha resposta sobre fidelidade cai aqui, e com mais o agravante de que essa construção é tão comum no português quanto um dodô num zoológico. 3) Internet vs Web Realmente aí eu concordo. ficaria incoerente 4,5,6,7,8) os DOMs da discórdia, user agent, sidebars, onde/aonde Concordo, corrigido! 9)Pedinte digital e o resto Incluí mas contrariado. Tô quase metendo um customize neste ponto! :P "quaisquer questões adicionais" fica melhor não? Bem é só isso. []s!
Attachment #140125 - Attachment is obsolete: true
Attachment #140640 - Attachment is obsolete: true
Attachment #140856 - Attachment is obsolete: true
This is the latest technical letter. Everything next in this post is in portuguese. []s! ------------- Portuguese Readers Only :) ----------------------------------------- Agora vou responder aqui, afinal só nove comentários dá :) . Sobre estarmos fazendo uma tradução e sermos fiéis ao autor, acho que temos uma fidelidade maior, compartilhada obviamente com o autor, que é com a comunidade. E se para termos uma maior abrângência em nossa lingua for necessário adaptar SEM SAIR DOS RUMOS DA CARTA acho que deve ser feito. Ainda mais quando são pequenos detalhes linguísticos e técnicos. Onde eu não modifiquei mas concordei foi por puro cansaço quando corrigi. Conheço, e usava, esta prática sombria. :P Mas aí eu conheci o UTF-8 e minha vida mudou.:P Mas a sério agora, eu acho que não foi você que viu mas no topo da página temos uma coisa que eu gostaria de ressaltar: <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> Que manda o navegador alvo usar UTF-8. Achei muito melhora ativar essa função, do que ficar lotando o código dessas gambiarras que são os &atilde (se bem me lembro) que são comuns no Composer e em outros editores. Aqui no meu mozilla rodou bem! Sobre o IMHO nda que digitar define: IMHO no google não tenha resolvido! :P 1) Relatorio vs Relatorios Esqueci, mudei agora 2) Exemplos Funcionais Minha resposta sobre fidelidade cai aqui, e com mais o agravante de que essa construção é tão comum no português quanto um dodô num zoológico. 3) Internet vs Web Realmente aí eu concordo. ficaria incoerente 4,5,6,7,8) os DOMs da discórdia, user agent, sidebars, onde/aonde Concordo, corrigido! 9)Pedinte digital e o resto Incluí mas contrariado. Tô quase metendo um customize neste ponto! :P "quaisquer questões adicionais" fica melhor não? Bem é só isso. []s!
Attachment #141483 - Attachment is obsolete: true
Attachment #141483 - Attachment description: New version of the letter. → New version of the letter.(old/not really the latest)
QA Contact: stolenclover → portuguese
> ... que temos uma fidelidade maior, compartilhada obviamente > com o autor, que é com a comunidade. ok, ok... mas cada coisa no seu lugar. tambem discordo de algumas passagens da carta original, mas a traducao nao eh o lugar pra a gente expressar nossa opiniao. sobre o utf-8... eu nao entendo direito... no mozilla aqui ficou o.k. mas quando abri no vi ficou muito estranho. os '&atilde;' etc. nao sao uma gambiarra. eles permitem representar caracteres especais em charsets mais simples. mas em geral sobre a traducao, acho que estamos quase acabando. devo estar mandando uns comentarios... mas agora soh depois do carnaval. vou estar longe da rede esses dias.
(In reply to comment #36) > > ... que temos uma fidelidade maior, compartilhada obviamente > > com o autor, que é com a comunidade. > > ok, ok... mas cada coisa no seu lugar. tambem discordo de algumas passagens da > carta original, mas a traducao nao eh o lugar pra a gente expressar nossa opiniao. > > sobre o utf-8... eu nao entendo direito... no mozilla aqui ficou o.k. mas quando > abri no vi ficou muito estranho. os '&atilde;' etc. nao sao uma gambiarra. eles > permitem representar caracteres especais em charsets mais simples. > > mas em geral sobre a traducao, acho que estamos quase acabando. devo estar > mandando uns comentarios... mas agora soh depois do carnaval. vou estar longe da > rede esses dias. Em comparação com só escrever a carta em outro codificação que permita que eu acentue sem todas aquelas firulas é. Mas todos os navegadores mais atuais reconhecem, e como a tag charset recebendo utf-8 fica tudo ok. Se era só isso EU acho que vou perguntar pro pessoal agora se eles podem avaliar como versão final. Se alguem quiser revisar a hora é essa e todos são bem vindos. Adoro debates. :) Fabrício, quer incluir algo da sua? []s!
Nao. Pode mandar brasa.
(In reply to comment #38) > Nao. Pode mandar brasa. Eu vou esperar até o fim do carnaval pelo Bruno. Você conhece pessoas que podem dar uma olhada tb?
Ok I think we have this letter done, since none of the other brazilians have anymore to add/correct. Can anyone of Mozilla come to see it? Or are anyone who knows who i must contact?
Cool - worksforme. IMHO: "internet" -> Internet "ou outros navegadores baseados no Renderizador Gecko" -> ou outros navegadores baseados neste como -- The minor fixes should not be a blocker. Let's go ahead and check in the page.
checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment on attachment 141484 [details] New Version of the letter As all good reviews, this one comes a few hours late. Would it make sense to include a quick link to an automated checker the person can run to get an idea of what/how much needs to be changed to fix the problem? pt_BR starts here: >não é compatível com o navegador Mozilla ou outros navegadores baseados ou? Seria mais correto "e"? >no Renderizador Gecko como Netscape 6, Netscape 7, AOL "como" -> ", como o" ><P>Existe um relatório encaminhado sobre este problema no sistema de Talvez "Foi aberto um chamado sobre ..." ? ><P>Seguindo as recomendações da ECMA para ECMAScript (JavaScript) e as >recomendações do W3C para HTML, CSS, e DOM (Document Object Model) no >seu conteúdo, o site irá funcionar com os navegadores de ultima >geração citados acima assim como outros que suportam "acima assim como" -> "acima, assim como" ><P>Os seguintes sites vão lhe ajudar a suportar padrões abertos e ao "vão lhe ajudar ... abertos e ao"-> "contém informações que podem lhe ajudar a adequar seu site a estes padrões, e ao" >o Microsoft Internet Explorer. A informação para detecção do Navegador >Netscape Gecko também é importante.</P> Não entendi o que essa frase quer dizer. >---------------------------------------------------------<BR/> >O W3C define os padrões públicos para a Web que o Mozilla "que o Mozilla" -> "que desenvolvedores de navegatores Web, incluindo o Mozilla" >---------------------------------------------<BR/> >Venkman é um completo debugger interativo para Mozilla e Netscape 7 que "completo debugger interativo" -> "depurador interativo"
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: