New requirements for user signatures/zh

許多維基對於使用者自訂簽名有一些要求. 編輯團隊正在徵求您對該計畫的意見，以將其編寫到維基百科的軟體中. 這樣能夠讓在討論頁面上回复特定留言及使用其他一些工具更加方便.

您可以在下面找到建議內容及其原因的詳細資訊：


 * 團隊正在尋求什麼反饋： 意見：您的反饋
 * 為什麼提出此更改： 背景：為何更改？
 * 提出了什麼更改： 計畫：簽名驗證要求
 * 這些更改會怎麼影響您： 影響：變化的影響

如果沒有發生重大阻礙，則可能在2020年4月進行此更改. 如果團隊需要根據您的反饋做出重大更改，則將需要更長的時間.

意見：您的反饋
團隊想要您對此提案的任何反饋.

請您 在討論頁 發表有關這些問題的留言.


 * 1) 簽名驗證會在您的維基上造成任何問題嗎？
 * 2) 您認為團隊在進行此更改之前應該注意些什麼？
 * 3) 不符合新限制的現有簽名應要如何處理？ 例如，是否應禁止使用它們？

請不要因上述問題而限制想法，團隊希望聽到您想分享的任何反饋.

背景：為何更改？
In 2019, volunteers from 20 Wikimedia projects and usergroups, along with staff from the Wikimedia Foundation, participated in the Talk pages consultation. It was an effort to define better tools for on-wiki communication.

One of the outcomes of this consultation was a request for an easier way to reply to specific comments on talk pages.

In order for this feature to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them.

The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself. This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.

This additional consistency in the format of signatures would improve existing features, like "mention" notifications, which are only sent if the signature can be detected in your edit.

計畫：簽名驗證要求
The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature. Under the Editing team's proposal, existing signatures will *NOT* be affected.

禁止一些無效的HTML和其他Linter錯誤
Most importantly, this change would disallow unclosed formatting tags, like  or the corresponding wikitext markup, , without a matching closing tag (in this case,   or  , respectively). Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.

The check would also identify misnested tags, like  (either both of the , or both of the  , tags should be on the outside), and stripped tags, which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above).

Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like  and. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors.

A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at Help:Extension:Linter#Documentation of lint issues.

Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to Parsoid.

要求連結到使用者頁面、討論頁或貢獻頁
Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page. For example, "mention" notifications are not sent, and forthcoming DiscussionTools will not allow replying to comments with these invalid signatures. Gadgets and other tools that interact with signatures also may not work as expected.

This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.

在簽名中禁止“嵌套”的替換引用
Some use of subst: markup and tildes would also be disallowed in signatures. Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments. All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software. Simple subst: markup is still allowed.

現有簽名會發生什麼改變？
Any existing signatures that would become invalid under the new rules are still allowed (grandfathered in). When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid. But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.

We're looking for feedback as to whether you would like existing invalid signatures to be disallowed. If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.

這些更改何時會進行？
Please comment before 31 March 2020. The Editing team will make decisions about this project in early April. The results will be posted on the talk page.

If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback.

我們如何知道有哪些更改正在進行？
We'll include another notice in Tech/News when this change is about to be deployed.

簽名驗證錯誤看起來的樣子如何？
The HTML/lint errors include links to existing documentation about lint errors, such as Help:Extension:Linter/missing-end-tag, and a button to highlight the problematic part of the signature.

The required link errors include example wikitext syntax to use.