New Immissions/Updates:
boundless - educate - edutalab - empatico - es-ebooks - es16 - fr16 - fsfiles - hesperian - solidaria - wikipediaforschools
- wikipediaforschoolses - wikipediaforschoolsfr - wikipediaforschoolspt - worldmap -

See also: Liber Liber - Libro Parlato - Liber Musica  - Manuzio -  Liber Liber ISO Files - Alphabetical Order - Multivolume ZIP Complete Archive - PDF Files - OGG Music Files -

PROJECT GUTENBERG HTML: Volume I - Volume II - Volume III - Volume IV - Volume V - Volume VI - Volume VII - Volume VIII - Volume IX

Ascolta ""Volevo solo fare un audiolibro"" su Spreaker.
CLASSICISTRANIERI HOME PAGE - YOUTUBE CHANNEL
Privacy Policy Cookie Policy Terms and Conditions
Wikipedia:討論頁指導方針 - Wikipedia

Wikipedia:討論頁指導方針

维基百科,自由的百科全书

本页在英语维基百科的对应页面是一项指引,但在中文维基百科尚未达成共识,仅供参考。
请参照英语维基对应页面或本页的讨论页内容进一步完善本页,或提议和参与讨论本方针是否可以成为中文维基百科的方针或指引。
捷徑
WP:TPG
WP:討論指引
維基百科的指引
內容

不要介紹自我
不要複製原始資料
消歧義
不要製造惡作劇
胡言亂語

分類

子頁面
模板
列表
頁面分類

編輯

勇於更新頁面
構築網絡
編輯摘要
條目的大小

討論

討論頁指導方針
在討論頁上簽名
達成共識

態度

禮儀
侮褻
不要為闡釋觀點而擾亂維基百科
不要傷害新手
用戶頁

格式
格式手冊

請參見方針

維基百科中的討論頁讓編者能討論其相應條目頁或計畫頁的編輯改善建議。條目討論頁不應該被使用者利用成為發佈個人主觀意見的平台。

當在討論頁上撰寫意見時,某些意見往往會產生不良後果,但是其他使用者則重視良好的討論技巧。討論頁最基本的規則為交流、禮貌和為人設想。以下的指引能協助使用者有效地利用討論頁面。

目录

[编辑] 中立的觀點

[编辑] 維護維基百科的方針

A talk page is research for the article, and the policies that apply to articles also apply to talk pages. Research and debate should meet the same standards of verification, neutral point of view and no original research. There is reasonable allowance for speculation, suggestion and personal knowledge with a view to prompting further investigation, but it is a serious misuse of a talk page to continue to argue any point that has not met policy requirements.

Assume good faith and treat the other person in the discussion as a fellow editor, who is a thinking, feeling person, trying to contribute positively to Wikipedia, just like you - unless, of course, you have objective proof to the contrary, which can be validated by a third party. Someone's disagreeing with you is no such proof!

Pay particular attention to Wikipedia:Biographies of living persons:

Editors should remove any negative material about living persons that is either unsourced, relies upon sources that do not meet standards specified in Wikipedia:Reliable sources, or is a conjectural interpretation of a source.[1]

[编辑] 如何使用條目的討論頁

  • 交流:If in doubt, make the extra effort so that other people understand you and you get a proper understanding of others. Being friendly is a great help. It is always a good idea to explain your views; it is less helpful for you to voice an opinion on something and not explain why. Giving an opinion helps in convincing others and reaching consensus.
  • 回應主題:討論頁不是聊天室,所有的討論都必須與條目的改善建議有關,無關的討論將受到刪除。
  • Be positive:Article talk pages should be used for ways to improve an article, not to criticize, pick apart, or vent about the current status of an article. However, if you feel something is wrong, but aren't sure how to fix it, then by all means feel free to draw attention to this and ask for suggestions from others.
  • 保持客觀:Talk pages are not a forum for editors to argue their own different points of view about controversial issues. They are a forum to discuss how the different points of view obtained from secondary sources should be included in the article, so that the end result is neutral and objective (which may mean including conflicting viewpoints). The best way to present a case is to find properly referenced material. (For an alternative forum for personal opinions, see the m:Wikibate proposal.)
  • Deal with facts: The talk page is the ideal place for all issues relating to verification. This includes asking for help to find sources, comparing contradictory facts from different sources, and examining the reliability of references. Asking for a verifiable reference to support a statement is often better than arguing against it.
  • Share material: The talk page can be used to store material from the article which has been removed because it is not verified, so that time can be given for references to be found. New material can sometimes be prepared on the talk page until it is ready to be put into the article.
  • Discuss edits: The talk page is particularly useful to talk about edits. If one of your edits has been reverted, and you change it back again, it is good practice to leave an explanation on the talk page and a note in the edit summary that you have done so. The talk page is also the place to ask about another editor's changes. If someone queries one of your edits, make sure you reply with a full, helpful rationale.
  • Make proposals: New proposals for the article can be put forward for discussion by other editors if you wish. Proposals might include changes to specific details, page moves, merges or making a section of a long article into a separate article.

[编辑] 良好的習慣

  • 在討論頁上簽名:要在討論頁上簽名,只需輸入四個波浪號(~~~~)便行,它們將自動換成你的用戶名和時間郵戳,就好像這樣:Example 03:44 2007年1月1日 (UTC)。請注意所有人都沒可能留下匿名留言,因為就算你沒有在留言時簽名,你的用戶名稱或IP地址都會記錄在頁面歷史中。
  • 避免過多的文字特效:請注意過多的文字特效會使別的使用者有被騷擾的感覺,亦讓人感覺到這些留言帶強烈的語氣,例如是斜體文字粗體文字,以及英文中完全的大寫字母和過多的感嘆號,就像是「SHOUTING」及「叫嚷!!!!!」。但是適當的文字特效能夠突顯你想表達的關鍵字句,讓讀者能易於理解你的留言。
  • 留言要簡潔:如果你的留言超過100字時請考慮簡化文字的長度。長而雜亂的留言通常都難以讓其他用戶理解,並且用戶通常都會不理會或誤解你的留言。如果你真的需要撰寫一篇詳細、逐點說明的留言,參閱下面了解如何整理你的留言。
  • Keep the layout clear: Keep the talk page attractively and clearly laid out, and avoid repetition, muddled writing, and unnecessary digressions. Talk pages with a good signal to noise ratio are more likely to attract continued participation.
  • Read the archives: Many article talk pages contain links to archives, which contain earlier discussions. If you are a new editor to an article, be sure to read them, as they often deal with common content disputes and resolutions to them. You may well find your questions and/or objections have already been answered.
  • 使用合適的語言:No matter to whom you are addressing your comments, it is preferred that you use English on English Wikipedia talk pages. This is because comments should be comprehensible to the community at large. If the use of another language is unavoidable, please provide a translation of the comments if possible or on request. If you cannot, it is your responsibility to either find a fluent third party to do so or to contact a translator through the Wikipedia:Embassy.
  • 如何投票:Some pages invite you to vote on a topic. Add your vote as a bullet (*) underneath the relevant topic and bold (''') your actual vote. Your vote will typically not carry much weight unless you include your rationale for making it. Make sure to sign your post (~~~~), as described above. Note that polling is not a substitute for discussion.
  • 集中討論: avoid posting the same thread in multiple forums. This fragments discussion of the idea, creating discussions in separate places with no interchange of ideas. This is rarely desirable, and leads to redundant effort where an idea that has already been adequately addressed has to be considered all over again. Instead, solicit discussion in only one location, either an existing talk page or a new project page, and if needed advertise that in other locations using a link. See also: mb:ForestFire
    If you find a fragmented discussion, it may be desirable to move all posts to one of the locations, removing them from the other locations and adding a link.

[编辑] 不能接受的行為

Please note that some of the following are of sufficient importance to be official Wikipedia policy. Violations (and especially repeated violations) may lead to the offender being banned from Wikipedia.

  • 不要人身攻擊:A personal attack is saying something negative about another person. This mainly means:
    • 不要侮辱他人:Don't make ad hominem attacks, such as calling someone an idiot or a fascist. Instead, explain what is wrong with an edit and how to fix it.
    • 不要威脅別人:For example, threatening people with "admins you know" or having them banned for disagreeing with you.
    • 不要訴諸法律威脅: Threatening a lawsuit is highly disruptive to Wikipedia, for reasons given at the linked page.
    • 永不提供個人資料:Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely.
  • 不要歪曲別人意見:The record should accurately show significant exchanges that took place, and in the right context. This usually means:
    • Be precise in quoting others.
    • When describing other people's contributions or edits, use diffs. The advantage of diffs in referring to a comment is that it will always remain the same, even when a talk page gets archived or a comment gets changed.
    • As a rule, don't edit others' comments. Exceptions are described in the next section.

[编辑] 編輯意見

[编辑] 別人意見

It is not necessary to bring talk pages to publishing standards, so there is no need to correct typing errors, grammar, etc. It tends to irritate the users whose comments you are correcting. Never edit someone's words to change their meaning.

Editing others' comments is generally not allowed. Exceptions are:

  • If you have their permission
  • Removing prohibited material such as libel and personal details
  • Removing personal attacks and incivility. Please read WP:ATTACK#Removal_of_text and WP:CIVIL#Removing_uncivil_comments before removing anything.
  • Unsigned comments: You are allowed to append {{unsigned}} or one of its variants to the end of someone's comment if they have failed to sign it. The form is {{subst:unsigned|USER NAME OR IP}}, which results in —The preceding unsigned comment was added by USER NAME OR IP (talk • contribs) ..
  • Interruptions: In some cases, it is OK to interrupt a long contribution, either by a short comment (as a reply to a minor point) or by a headline (If the contribution introduces a new topic. In that case, add "<small>Headline added to (reason) by ~~~~</small>"). In such cases, please add {{subst:interrupted|USER NAME OR IP}} before the interruption.
  • When a long comment has formatting errors, rendering it difficult to read. In this case, restrict the edits to formatting changes only and preserve the content as much as possible.

[编辑] 個人意見

It is best to avoid having to change one's comments. Other users may already have quoted you with a diff (see above) or have otherwise reacted to your statement. Therefore, use "Show preview" and think about how your statement may look to others before you save it.

Changing or deleting comments after someone replied is likely to cause problems, because it will put the reply in a different context. In that case you have several options:

  • Ask the person who replied (on their talk page) if it's OK to delete or change your text
  • use strike-through or a place holder to show it is a retrospective alteration.
    • Strike-through is typed <s>like this</s> and ends up like this.
    • A placeholder is a text such as "[Thoughtless and stupid comment removed by the author.]". This will ensure that your fellow editors' irritated responses still make sense. In turn, they may then wish to replace their reply with something like, "[Irritated response to deleted comment removed. Apology accepted.]"

[编辑] 爭議

If you are having a disagreement or a problem with someone's behavior, please read Wikipedia:Resolving disputes.

Some examples of talk pages on controversial topics are Talk:Abortion, Talk:Capitalism, Talk:Socialism, Talk:Jesus Christ, and Talk:Evolution.

[编辑] 技術和格式標準

[编辑] 排版

  • Answer a post underneath it: Then the next post will go underneath yours and so on. This makes it easy to see the chronological order of posts. The one at the bottom is the latest.
  • Separate multiple points with whitespace: If a single post has several points, it makes it clearer to separate them with a paragraph break (i.e. a blank line).
  • Indent your post: This makes it easy to see that you are a different user to the previous post. Any indentation system is acceptable. The important thing is that the sequence of talk should be easy to follow. There are two main systems:
    • 1) Each post indents by one regardless of user: The thread starts as above, but each new post is indented by one extra colon (:), regardless who made the post. When the post is indented too far, the next post can start at the left margin again, marked (Unindent). Sometimes a post in this system will develop its own sub tree to discuss a particular response in more detail.
    • 2) Each user has a specific indentation: The first contributor is all the way to the left, the following person starts with one colon (:), and the one after starts with two colons (::) and the one after with three colons (:::) and so on. Then, when the first contributor responds, they start at the left margin again, and the second, third and fourth persons continue to mark themselves with one, two and three colons respectively. Each user's posts are vertically aligned. However, this system tends to break down when there are many different contributors, as there are only a few usable indentation levels.

[编辑] 新話題和標題

See also Headings.

  • Start new topics at the bottom of the page: If you put a post at the top of the page, it is confusing and can also get easily overlooked. The latest topic should be the one at the bottom of the page.
  • Make a new heading for a new topic: It will then be clearly separated into its own section and will also appear in the TOC (table of contents) at the top of the page. A heading is easy to create with == either side of the words, as in == Heading ==. The "Post a comment" feature can be used to do this automatically. (If you're using the default Wikipedia:Skin, you can use the "+" tab next to the "Edit this page" tab instead.) Enter a subject/heading in the resulting edit page, and it will automatically become the section heading.
  • Keep headings on topics related to the article. It should be clear from the heading which aspect of the article you wish to discuss.
  • Keep headings neutral: A heading should indicate what the topic is, but not communicate a specific view about it.
    • Don't praise in headings: You may wish to commend a particular edit, but this could be seen in a different light by someone who disagrees with the edit!
    • Don't be critical in headings: This includes being critical about details of the article. Those details were written by individual editors, who may experience the heading as an attack on them.
    • Never address other users in a heading: A heading should invite all editors to respond to the subject addressed.
  • Section headings appear in edit summaries: This happens automatically. If you add your own particular edit summary after it, other users can see what section you have posted in.
  • An example of good practice: If your problem with the article Dinosaur is that it states that "All dinosaurs walked on two legs," do not write a heading on the talk page: "This article is completely wrong and stupid," or, "Morons think all dinosaurs walk on two legs," or even "All dinosaurs did not walk on two legs." Rather, attempt to make your headings welcoming to those you disagree with. Try, "Did all dinosaurs walk on two legs?", "Dinosaur locomotion", or, "Brontosauri walked on four legs". This will make it easy for people to address that issue. Note that, due to the above rule, the heading you choose will appear in the watchlists of everyone who is watching the page, each time someone contributes to that section. A heading that piques interest tends to draw more people into the discussion.

[编辑] 標記

  • Feel free to ignore typographical conventions: Do what you need to to make your points clear. The Manual of Style is for articles. However, please note the following point:
  • Avoid HTML markup: Use of HTML markup where equivalent wikimarkup works fine is frowned upon, except the use of <s> (strike-through) operator for retracting parts of your own posts that have since been superseded, as stated above. (Using <s> on another user's posts is covered by "Don't misrepresent other people", above.)
  • Substitution: Although you may help to substitute warnings on user talk pages, it is not recommended and is also quite tedious for the average human, which is why there are bots that do the job. (See MeatBall:ContextSwizzling).

[编辑] 連結、時間和頁面名稱

  • Make links freely: Links to articles are as useful on talk pages as anywhere else, and links to non-existent articles can help get them onto the most wanted pages list.
  • Use UTC when referring to a time, e.g. the time of an edit or page move.
  • When mentioning the name of the page, cite the current name: This applies when a page is moved (i.e. retitled). In such a case, the Talk page is usually also moved. If you continue to use the old name, it will be confusing, especially for new editors to the article.

[编辑] 當頁面文字過長時

  • Archive — don't delete: When a talk page has become too large or a particular subject is no longer being discussed, don't delete the content — archive it. Here's how:
    • Create a new page (see Help:Starting a new page and Wikipedia:How to archive a talk page for details).
    • Place the page in a talk or Wikipedia talk namespace.
    • Give it a suitable name: usually this is simply by adding "archive" to the original name.
    • Explain on the archive page where the text you plan to archive will come from and provide a link.
    • Cut the relevant content from the original page and paste it into the new page.
    • Replace the text on the original page with a link to the archive.
    • Sometimes you may find it suitable to leave a summary of the discussion on the talk page and provide a link to the full text in the archive.
  • Summarize ("refactor"): See Wikipedia:Refactoring talk pages for details on why and how to refactor talk pages.

[编辑] 討論頁模板

One exception to the style guideline is the template talk page. This is because the talk page usually functions as two pages, so it's recomended to use level 1 headers to separate the issues. Example:

=Documentation=
=Discussion=

or

= Documentation =
= Discussion =

The primary reason for doing this is that using section=new will create a level 2 heading, and it's preferable to separate discussion and documentation so a new comment is placed under discussion. See also {{doctl}}.

[编辑] 參見

其他语言

Static Wikipedia (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu -

Static Wikipedia 2007 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu -

Static Wikipedia 2006 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu

Static Wikipedia February 2008 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu