View source for Help:Extension:Linter/pt-br

<languages />
A extensão '''{{ll|Extension:Linter|Linter}}''' identifica padrões de wikitext que devem ou podem ser consertados em páginas, juntamente com algumas orientações sobre quais os problemas com esses padrões e como corrigi-los.

<span class="mw-translate-fuzzy">Os grupos de páginas do [[Special:LintErrors|Special:LintErrors]]  com erros por tipo. Algumas dessas questões podem ser mais fáceis de encontrar com [[Special:Expandtemplates|Special:Expandtemplates]]. Nesta página, classificaremos questões de fiabilidade de acordo com a gravidade da questão em relação aos objetivos bloqueados por essas questões. Mais informações e discussões sobre isso são fornecidas abaixo.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Some of these issues may be easier to find with [[Special:Expandtemplates|{{int|expandtemplates}}]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">On this page, we will classify lint issues according to the severity of the issue vis-à-vis goals that are blocked by those issues.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">More information and discussion about this is provided further below.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">There is a new feature "Show all linter errors for a specific page" at the bottom of [[Special:LintErrors|{{int|linterrors}}]] page which allows an editor to get a report of all errors on a single page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The report contains the category and other useful information and each error has a clickable link that loads the page and highlights the error.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">(Note: if your source editor has syntax highlighting enabled, the highlighting may not work).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">By working from the end of the list upward, changes to the page will not invalidate the character offsets of earlier errors and is the recommended way to work if you are fixing all errors on a page.</span>

Continuaremos a melhorar a funcionalidade para eliminar o ruído, corrigir erros e tornar a saída do linter mais acionável, mas a saída atual está pronta para usar e agir.

<span id="Documentation_of_lint_issues"></span>
== Documentação de problemas de lint ==
{{Main|Help:Lint errors}}

<span id="Why_and_what_to_fix"></span>
== Por que e o que consertar ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Going forward, the [[Special:MyLanguage/Parsing|parsing team]] plans to leverage the Linter extension to identify wikitext patterns:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* that are erroneous (ex: bogus image options – usually caused by typos or because [[phab:T163582|media option parsing in MediaWiki is fragile]]).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* that are deprecated (ex: [[phab:T134423|self-closing tags]])
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* that can break because of changes to the parsing pipeline (ex: [[Special:MyLanguage/Parsing/Replacing Tidy|replacing Tidy with RemexHTML]])
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* that are no longer valid in HTML5 (ex: obsolete tags like center, font)
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* that are potentially broken and can be misinterpreted by the parser compared to what the editor intended them to be (ex: unclosed HTML tags, misnested HTML tags)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Not all of them need to be fixed promptly or even ever (depending on your tolerance for lint). Different goals are advanced by fixing different subsets of the above lint issues. We (the parsing team) will try to be transparent about these goals and will provide guidance about which goals are advanced by fixing which issues.
</div>

'''São fornecidas instruções simplificadas [[Special:MyLanguage/Parsing/Replacing Tidy/FAQ#What will editors need to do?|na página de FAQ]].'''

<span id="Goal:_Replacing_Tidy"></span>
=== Meta: [[Special:MyLanguage/Parsing/Replacing Tidy/FAQ|Substituir o Tidy]] ===

<div lang="en" dir="ltr" class="mw-content-ltr">
As part of addressing technical debt in the parsing pipeline of MediaWiki, we replaced Tidy with a HTML5-based tool. However, doing so would have broken the rendering of a small subset of pages unless certain wikitext patterns were fixed. Specifically, issues found in the <code>deletable-table-tag</code>, <code>pwrap-bug-workaround</code>, <code>self-closed-tag</code>, <code>tidy-whitespace-bug</code>, <code>html5-misnesting</code>, and <code>tidy-font-bug</code> categories. In order to do a timely replacement of Tidy, we classified all these issues as high priority.
</div>

<span id="Goal:_Improving_compliance_between_rendering_of_the_PHP_parser_and_Parsoid"></span>
=== Objetivo: [[Special:MyLanguage/Parsoid/Known differences with PHP parser output|Aprimorar a conformidade entre a renderização do analisador sintático PHP e o Parsoid]] ===
<span lang="en" dir="ltr" class="mw-content-ltr">Right now, the HTML generated by the PHP parser is used for read views and the HTML generated by Parsoid is [[Special:MyLanguage/Parsoid/Users|used by editing tools and the Android app among others]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The parsing team, [[Special:MyLanguage/Parsing#A: Move to adopt Parsoid as the primary MediaWiki wikitext parser|as one of its long-term objectives]], wants to enable the use of Parsoid's output for both read views as well as for editing.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Since Parsoid and RemexHTML are both HTML5-based tools, the lint categories that affect RemexHTML's rendering also affect Parsoid's rendering.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">We haven't yet identified any newer lint issues that affect Parsoid's rendering at this time, but will update this list as we identify any such.</span>

<span id="Goal:_HTML5_output_compliance"></span>
=== Objetivo: [[Special:MyLanguage/Parsing/Notes/HTML5 Compliance|conformidade no resultado do HTML5]] ===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a somewhat complex goal and we haven't yet arrived at an understanding about how important it is to pursue this goal or how far we should go with this. Additionally, it is not yet clear what mechanisms we wish to leverage towards this goal. For example, based on a bunch of discussions in different venues, [[User:Legoktm/HTML+MediaWiki|User:Legoktm/HTML+MediaWiki]] outlines a proposal for handling the html5-deprecated big tag. In any case, fixing issues in the <code>obsolete-tag</code>, <code>self-closed-tag</code> categories advance this goal. Given lack of clarity around this goal, we have accordingly marked the obsolete-tag category as a low-priority goal.
</div>

<span id="Goal:_Clarifying_editor_intent"></span>
Meta: Esclarecer a intenção do editor
<span lang="en" dir="ltr" class="mw-content-ltr">Getting markup right is hard.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Errors inadvertently creep through.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">While the parser does its best in recovering from these errors, in many cases, what the parser does might not truly reflect the editor's original intent.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Given that, we recommend that it is best to fix the issues identified here to clarify the editor's intention.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Issues in the <code>bogus-image-options</code>, <code>fostered-content</code>, <code>misnested-tag</code>, <code>missing-end-tag</code> categories seem to affect this goal.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Since this is a fairly important goal, we have marked most of them with medium priority.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">However, we have marked the missing-end-tag category with a low priority since in a vast majority of cases, the parser does seem to recover fairly accurately.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Nevertheless, we recommend fixing whatever can be fixed without too much effort, if only to assist comprehension by other human editors and tools.</span>

<span id="Goal:_Clean_markup"></span>
=== Meta: Marcação limpa ===

<div lang="en" dir="ltr" class="mw-content-ltr">
Getting markup right is hard. Even in the presence of errors, the parser does a fairly decent job in most cases in figuring out accurately how that piece of markup is supposed to render. But, in much the same way that typos, punctuation and minor grammatical errors can feel unsettling, some editors or those with a developer-mindset might find lint issues in these categories unsettling. We don't recommend spending an inordinate amount of time fixing these issues and, in many scenarios, bots might be able to fix these up as well. <code>misnested-tag</code>, <code>missing-end-tag</code>, <code>stripped-tag</code> lint categories affect this goal.
</div>
<!--
{{Special:PrefixIndex/Help:Extension:Linter/|stripprefix=1}}
-->

== FAQ ==

<span id="When_are_lint_errors_for_a_page_updated?"></span>
=== Quando há erros de lint  para uma página atualizada? ===

<div lang="en" dir="ltr" class="mw-content-ltr">
Currently, all lint categories are populated by errors identified by [[Parsoid]] while parsing a page. When a page (or, template transcluded on a page) is edited, [[Change propagation|ChangeProp]] requests a re-parse of that page from Parsoid, which will send the fresh results to the Linter extension.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This means that when a new category is introduced (or a correction is made to a previous category), it may take a while for all the results to be updated (if ever for pages that are rarely touched). Making a null edit would speed up the process individually. However, in [[phab:T161556]], we're exploring ways to reprocess all pages.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Should pages in X namespace (e.g. talk) be fixed ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The priority is [[Special:MyLanguage/Manual:$wgContentNamespaces|content namespace]]s. The rest largely depend on the wiki. A lot of pages are used as a [[wikipedia:Sandbox_(software_development)|sandbox]], and as such deliberately contain errors.
</div>

<span id="Tools"></span>
== Ferramentas ==

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[w:User:PerfektesChaos/js/lintHint]] – a JavaScript gadget that shows a list of LintErrors (Parsoid messages) live
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[w:Wikipedia:WPCleaner/Linter|WPCleaner]] – a Java program that interfaces with Linter and can also detect some of the errors
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[:ja:User:MawaruNeko/ShowPageLintError.js]] – a user script that shows all lint errors on a page
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://github.com/RazeSoldier/Hclear-bot Bot] by [[User:星耀晨曦]] that can fix {{ll|Help:Extension:Linter/multiple-unclosed-formatting-tags|multiple-unclosed-formatting-tags}} errors.
</div>

<span id="See_also"></span>
== Ver também ==

<div lang="en" dir="ltr" class="mw-content-ltr">
*[[Special:MyLanguage/Parsoid/API#Wikitext -> Lint 2|Parsoid/API#Wikitext to lint]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
*[[Special:MyLanguage/Parsing/Replacing Tidy|Parsing/Replacing Tidy]]
</div>
*{{ll|Parsing/Replacing Tidy/FAQ}}
<div lang="en" dir="ltr" class="mw-content-ltr">
*[[w:Wikipedia:Linter]]
</div>

[[Category:Extension help{{#translation:}}]]
[[Category:Linter{{#translation:}}]]