Portuguese Translation Progress

[iliakan]

Maintainer List

@luizclr, @odsantos, @Mr-Saxobeat, @jonnathan-ls, @leopoldovcfonseca, @nazarepiedady, @murillorossetti

For New Translators

Please read this first (click to open)

To translate an article: 1. Check that no one else has claimed your article in the checklist below. 2. Comment below with the title of the article that you would like to translate, exactly as listed, e.g. `An Introduction to JavaScript`. - Please take only one article at a time. 3. Fork this repo, translate the article in your fork and submit a pull request! - The pull request title should be same as the article, e.g. `An Introduction to JavaScript` (just like comment) Please be prompt with your translations! If you find that you can't commit any more, let maintainers know so they can assign the page to someone else.

For Maintainers

Click to open

We recommend that a translation has 2 reviews to be merged. Please let others know what you do, on community boards and chats, invite them to join. Translations become better if more people see them. Translations are tracked below, like this: * [ ] [Home Page](url) (@iliakan) #1 Our helpful bot watches comments and adds the translator nick and PR id, marks completed, when PR is merged. You can read the details at . If something doesn't work right, please contact @iliakan.

Team translation

More details about team translation: https://javascript.info/translate/bot.

Only maintainers can check/uncheck items below. If you're not, please write in a comment what you take to translate, the title, exactly as in the list.

The JavaScript language

An introduction

• [X] An Introduction to JavaScript (@mrodrigochaves)
• [X] Manuals and specifications (@Mr-Saxobeat) #53
• [X] Code editors (@mrodrigochaves)
• [X] Developer console (@mrodrigochaves)

JavaScript Fundamentals

• [X] Hello, world! (@mrodrigochaves)
• [X] Code structure (@mrodrigochaves)
• [X] The modern mode, "use strict" (@daliannyvieira)
• [X] Variables (@mrodrigochaves)
• [X] Data types (@mrodrigochaves) and (@jonnathan-ls) #243
• [X] Interaction: alert, prompt, confirm (@EvertonCosmo)
• [X] Type Conversions (@PauloBacelar) #212
• [X] Basic operators, maths (@betofc89) and (@Peruibeloko ) #412
• [X] Comparisons (@Andres-ibanez) #15
• [X] Conditional branching: if, '?' (@jonnathan-ls) #246
• [X] Logical operators (@jonnathan-ls) #401
• [X] Nullish coalescing operator '??' (@ermogenes) #195
• [ ] Loops: while and for (@alvar-o) #77
• [X] The "switch" statement (@odsantos) #108
• [ ] Functions (@Dheyson)
• [ ] Function expressions (@AlexPHorta) #162
• [ ] Arrow functions, the basics (@allanpaza) #163
• [ ] JavaScript specials (@odsantos) #146

Code quality

• [X] Debugging in the browser (@zenobiopereira) #399
• [ ] Coding Style (@odsantos) #167
• [ ] Comments (@odsantos) #168
• [ ] Ninja code (@Mr-Saxobeat) #182
• [ ] Automated testing with Mocha (@odsantos) #164
• [X] Polyfills and transpilers (@odsantos) #215

Objects: the basics

• [X] Objects (@odsantos)
• [X] Object references and copying (@danilolmc) #408
• [ ] Garbage collection (@odsantos) #174
• [ ] Object methods, "this" (@odsantos) #176
• [X] Constructor, operator "new" (@PedroDousseau) #400
• [ ] Optional chaining '?.'
• [X] Symbol type (@danilolmc) #409
• [ ] Object to primitive conversion (@odsantos) #193

Data types

• [X] Methods of primitives (@DouglasMV)
• [ ] Numbers (@nazarepiedady)
• [ ] Strings (@odsantos) #197
• [ ] Arrays (@odsantos) #105
• [ ] Array methods (@adriavieira314) #109
• [ ] Iterables (@marcoarib) #118
• [X] Map and Set (@gabifs) #405
• [ ] WeakMap and WeakSet (@kiniggit)
• [ ] Object.keys, values, entries (@marcoarib)
• [ ] Destructuring assignment (@theomelo)
• [ ] Date and time (@nataliakeller)
• [ ] JSON methods, toJSON (@dlgasparotto) #185

Advanced working with functions

• [ ] Recursion and stack (@allanpaza)
• [ ] Rest parameters and spread syntax (@anapaulalemos)
• [ ] Variable scope, closure (@dlgasparotto)
• [ ] The old "var" (@EvertonCosmo)
• [X] Global object (@anapaulalemos) #123
• [ ] Function object, NFE (@odsantos) #204
• [X] The "new Function" syntax (@tfbio) #156
• [ ] Scheduling: setTimeout and setInterval (@vmlage)
• [X] Decorators and forwarding, call/apply (@nazarepiedady) #218
• [ ] Function binding (@sidglas)
• [X] Arrow functions revisited (@mauehara)

Object properties configuration

• [ ] Property flags and descriptors (@herbertpdl) #219
• [ ] Property getters and setters (@herbertpdl)

Prototypes, inheritance

• [X] Prototypal inheritance (@flaviohblima) #230
• [X] F.prototype (@flaviohblima) #231
• [X] Native prototypes (@flaviohblima) #233
• [ ] Prototype methods, objects without proto

Classes

• [X] Class basic syntax (@thiagocardoso1988) #248
• [ ] Class inheritance (@PauloBacelar)
• [ ] Static properties and methods (@thiagocardoso1988)
• [X] Private and protected properties and methods (@danilolmc) #410
• [X] Extending built-in classes (@danilolmc) #413
• [X] Class checking: "instanceof" (@danilolmc) #398
• [X] Mixins (@danilolmc) #382

Error handling

• [ ] Error handling, "try...catch" (@jpvasquesc)
• [ ] Custom errors, extending Error (@rkaustchr)

Promises, async/await

• [ ] Introduction: callbacks (@nildo)
• [ ] Promise (@portothree)
• [X] Promises chaining (@kiniggit) #120
• [ ] Error handling with promises (@kiniggit)
• [ ] Promise API (@mjfneto)
• [ ] Promisification (@kiniggit)
• [ ] Microtasks (@kiniggit)
• [ ] Async/await (@adroaldopagliari)

Generators, advanced iteration

• [X] Generators (@danilolmc) #414
• [X] Async iteration and generators (@danilolmc) #418

Modules

• [ ] Modules, introduction (@adriavieira314)
• [X] Export and Import (@anapaulalemos)
• [X] Dynamic imports (@danilolmc) #419

Miscellaneous

• [ ] Proxy and Reflect (@danilolmc) #422
• [ ] Eval: run a code string (@odsantos) #270
• [ ] Currying (@dekisr)
• [X] Reference Type (@danilolmc) #423
• [X] BigInt (@danilolmc) #430
• [X] Unicode, String internals (@notFaceroll) #426
• [ ] WeakRef and FinalizationRegistry

Browser: Document, Events, Interfaces

Document

• [ ] Browser environment, specs (@daniellic9)
• [ ] DOM tree (@almirleandro)
• [ ] Walking the DOM (@exploitmik)
• [X] Searching: getElement, querySelector (@danilolmc) #432
• [ ] Node properties: type, tag and contents (@addev93)
• [ ] Attributes and properties (@denis-rossati)
• [ ] Modifying the document
• [X] Styles and classes (@danilolmc) #433
• [ ] Element size and scrolling (@danilolmc)
• [ ] Window sizes and scrolling
• [ ] Coordinates

Introduction to Events

• [ ] Introduction to browser events (@cesarkohl)
• [ ] Bubbling and capturing
• [ ] Event delegation
• [ ] Browser default actions
• [ ] Dispatching custom events

UI Events

• [ ] Mouse events
• [ ] Moving the mouse: mouseover/out, mouseenter/leave
• [ ] Drag'n'Drop with mouse events
• [ ] Pointer events
• [ ] Keyboard: keydown and keyup
• [ ] Scrolling (@vnscosta)

Forms, controls

• [ ] Form properties and methods (@recalderon)
• [ ] Focusing: focus/blur
• [ ] Events: change, input, cut, copy, paste
• [ ] Forms: event and method submit

Document and resource loading

• [ ] Page: DOMContentLoaded, load, beforeunload, unload
• [X] Scripts: async, defer (@larissaiurk) #229
• [ ] Resource loading: onload and onerror

Miscellaneous

• [ ] Mutation observer
• [ ] Selection and Range
• [ ] Event loop: microtasks and macrotasks

Frames and windows

• [ ] Popups and window methods
• [ ] Cross-window communication
• [ ] The clickjacking attack

Binary data, files

• [ ] ArrayBuffer, binary arrays
• [ ] TextDecoder and TextEncoder
• [ ] Blob
• [ ] File and FileReader

Network requests

• [ ] Fetch (@vitorinoaraujo)
• [ ] FormData
• [ ] Fetch: Download progress
• [ ] Fetch: Abort
• [ ] Fetch: Cross-Origin Requests
• [ ] Fetch API
• [ ] URL objects
• [ ] XMLHttpRequest
• [ ] Resumable file upload
• [ ] Long polling
• [ ] WebSocket
• [ ] Server Sent Events

Storing data in the browser

• [ ] Cookies, document.cookie
• [ ] LocalStorage, sessionStorage
• [ ] IndexedDB

Animation

• [ ] Bezier curve (@lucastrvsn)
• [X] CSS-animations (@mauehara) #128
• [ ] JavaScript animations (@karlasamantha)

Web components

• [ ] From the orbital height
• [ ] Custom elements (@gabifs)
• [ ] Shadow DOM and events
• [ ] Template element (@HakaCode)
• [ ] Shadow DOM slots, composition
• [ ] Shadow DOM styling
• [ ] Shadow DOM and events

Regular expressions

• [X] Patterns and flags (@fsdude) #147
• [X] Character classes (@odsantos) #274
• [X] Unicode: flag "u" and class \p{...} (@Peruibeloko) #415
• [X] Anchors: string start ^ and end $ (@Peruibeloko) #420
• [ ] Multiline mode of anchors ^ $, flag "m" (@Peruibeloko) #421
• [X] Word boundary: \b (@Peruibeloko) #424
• [ ] Escaping, special characters (@Peruibeloko) #425
• [ ] Sets and ranges [...] (@Peruibeloko) #427
• [X] Quantifiers +, *, ? and {n} (@Peruibeloko) #429
• [ ] Greedy and lazy quantifiers (@Peruibeloko)
• [ ] Capturing groups
• [ ] Backreferences in pattern: \N and \k\<name>
• [ ] Alternation (OR) |
• [ ] Lookahead and lookbehind
• [ ] Catastrophic backtracking
• [ ] Sticky flag "y", searching at position
• [X] Methods of RegExp and String (@fsdude) #141

[rafaelgou]

Hi, @mrodrigochaves, can I join the effort? Do we have a glossary/style guide? If not, is there any from other languages that we could use as a starting point?

Thanks!

[iliakan]

Maybe there is a well-known glossary for web terms ?

[iliakan]

@rafaelgou you don’t need a permission to join. Just tell us what is you’re translating.

[rafaelgou]

Thanks, @iliakan. I'm researching a starting glossary and a way to store what we decide to unify during translation.

[mrodrigochaves]

Welcome, @rafaelgou ! I'm following a list according to the topic above: For new translators.

[DouglasMV]

Hi I'm going to help translate. I will start with the "Methods of primitives" article at 1-js/05-data-types/01-primitives-methods

[iliakan]

When I look at Wikipedia, there's only pt.wikipedia.org.

Does it really make sense to have separate pt-br.javascript.info and pt-pt.javascript.info? Or we can join the efforts to have just pt.javascript.info?

[DouglasMV]

As a brazilian i can tell you that if i read a technical text, wich is the case, in Portugal's portuguese, I can understand but i cleary know i'm reading pt-pt not pt-br. But i cannot write in pt-pt only in pt-br. I hope that helps to clear a little bit how they are different.

[mrodrigochaves]

Hello @iliakan,

I understand your placement. My suggestion is: either keep pt-br.javascript.info, or switch to pt.javascript.info.

However, I would have to keep native contributors from Brazil or Portugal, not from both countries, because of the difference that @DouglasMV commented above.

[iliakan]

Thanks, I saw that Wikipedia has only PT, so I joined pt-br and pt-pt into PT. If Wiki is ok with that, we should be fine too =)

[iliakan]

For Wiki: an article must be either pt-pt or pt-br, not mixed.

I guess, if both regions understand each other, that rule is enough to keep both contributors. That said, pt-pt version did not ever came to life.

[iliakan]

@mrodrigochaves may I wonder, what's your email? I'm making a non-public list of emails of all maintainers, to have a backup contact (if the translation appears to be dead or something).

[DouglasMV]

I'm translating 1-js/05-data-types/02-number/

[Andres-ibanez]

I'm translating Comparisons and Operators

[Andres-ibanez]

Logical operators

[DouglasMV]

Translating /1-js/05-data-types/03-string/

[DouglasMV]

Translating /1-js/05-data-types/04-array/

[DouglasMV]

Translating /1-js/05-data-types/05-array-methods

[DouglasMV]

Translating /1-js/05-data-types/06-iterable/

[DouglasMV]

Translating /1-js/05-data-types/07-map-set-weakmap-weakset/

[DouglasMV]

Translating /1-js/05-data-types/08-keys-values-entries/

[LASalvador]

Operators

[Mr-Saxobeat]

Manuals and specifications

[luizclr]

Operators

[romulomessias]

Hi. I want to help translate. I will start with Conditional operators: if, '?'

[iliakan]

Anyone wants to become a maintainer? @mrodrigochaves seems to be offline.

[luizclr]

@iliakan I do.

[iliakan]

@Luizlc10 done!

[luizclr]

Hi, @rmasouza. To take an item from the checklist you should comment only its title as this one https://github.com/javascript-tutorial/pt.javascript.info/issues/1#issuecomment-521220542

[romulomessias]

Hi, @rmasouza. To take an item from the checklist you should comment only its title as this one #1 (comment)

ok, thanks

[romulomessias]

Conditional operators: if, '?'

[javascript-translate-bot]

Error: the article already has meta information in the Progress Issue "(@rmasouza)" :interrobang:

[luizclr]

Hi, @rmasouza . I've already added you to this chapter. That's the reason of the error above. Just for the next time you will choose a chapter, comment only its title. =)

[dheysonalves]

Functions

[EvertonCosmo]

Interaction: alert, prompt, confirm

[luizclr]

Please translate only one chapter/Item per pull request (check the list above - e.g. Strings, Array, Array methods and so on). Do not translate a whole section in a single pull request. This way is easier to make code review. =D

[Mr-Saxobeat]

Hi, In the section 1 in english ("An introduction") there are four articles, where the article 1.2 ("Manuals and Specifications") is what I'm translating. But here in the portuguese repo already has a 1.2 article wich is named as the 1.3 ("Code Editors") article in the english version. What is suposed to do? Rename the articles folder?

[iliakan]

Maybe upstream changes not merged? Please compare it with the English version and bring in sync.

[luizclr]

Hi, @Mr-Saxobeat . Yes, this is not up to dated! I've just became a maintainer and didn't have time to sync it with master yet. I will be busy this weekend at least but I'll do it soon.

[LASalvador]

The "switch" statement

[thiagocardoso1988]

Object methods, "this"

[paimfp]

Ninja code

[alvar-o]

Loops: while and for

[odsantos]

Hi @mrodrigochaves , Would it be possible to contribute for the Portuguese translation ? Thanks, Osvaldo .

[iliakan]

I can update the list of maintainers, if existing ones don't respond. Please let me know if you know JS well enough to review PRs of others.

[odsantos]

Hi @iliakan, if you do not mind, I would like to begin translating basic articles, and if in conformance to your standards you might add me to a reviewer role.

However, from a quick look at the list of topics, I believe to be able to review most of the articles' translations with main exceptions to promises, yet some from Code quality, and a few more which I'm unsure of. So, I would also be pleased to additionally contribute as a reviewer.

I also have a legal copy of Flanagan's JavaScript, the Definitive Guide (updated to this year, although still appearing to have only new features from ECMAScript 5) for support.

Some suggestions for glossary terms research might be Gramática léxica , Wikipédia:Dicionário and Política de Privacidade - Glossário de termos-chave/pt-pt.

Thanks.

[odsantos]

I am starting by translating Logical operators. Thanks.

[iliakan]

Do we have enough maintainers for Portuguese Translation?

Please let me know if you'd like to join and know JS enough to review PRs of others =)

[odsantos]

I am afraid I do not know, @iliakan Ilya. I would be glad to join and review PR's. Please do add me as a maintainer. I believe to also have finished the first page translation and hope to soon open an issue an PR. Thanks.

[iliakan]

@odsantos I checked your github profile and couldn't find any evidence that you're good at JS. Are you? Do you have enough experience with JS?