Extension:Popups/zh

当用户将鼠标悬停在一个页面和分别的引用时，弹窗（Popups）扩展会预览一篇文章的内容，对于引用，还会显示引用的完整内容.

这个扩展原始Design team的开始，因著名的Navigation popups（导航弹窗）而作. 当前该功能对所有未登录的维基百科用户启用. 参见页面预览以了解扩展运作的描述，以及在此维基媒体项目的更多信息.

引用预览功能最终被加入，并用于实现德语社区的愿望. 有更详细的介绍和更多信息.

依赖
与 网关一起使用时，本扩展依赖于和. 也有可选的依赖项（如果你想作为 Beta 功能启用参考预览），以及 和 （用于检测）.

安裝

 * 安装依赖组件.


 * === 对于非测试站点（常规wiki）的最终LocalSettings设置的示例 ===

-{zh-hans:配置; zh-hant:組態;}-選項


页面预览内容
页面预览弹出窗口会显示一张图像（如果有的话）和一小段文字摘要.

图片
图片来源于，该图片返回与文章相关的单个最合适的缩略图. 它忽略维护模板，小作品，旗帜图标等.

文本
页面预览可以通过配置使用API，该API需要符合页面内容服务摘要端点规范. 对于第三方，我们鼓励使用页面内容服务来在您本地的wiki使用Popups.

您也可以使用扩展. 这个扩展有各种警告，我们不积极支持使用这个API.



参考文献预览内容


参考文献预览窗口的内容直接来源于页面自身的参考文献段落. 此处并不会使用任何外部服务. 如果内容超过弹出窗口大小，则会显示滚动条，以便可以查看所有内容.


 * === 参考资料类型 ===

The reference types displayed are set by using specific CSS-classes on the tag that can be used to encapsulate the content of a reference, e.g.. Currently the following types are supported:,  ,  ,  ,. Apart from that there is always a generic fallback if neither the cite tag was found nor an appropriate class was used. Please note, that it's not recommended to use the CSS-classes directly in wikitext, but rather by creating templates.

Renderers
This extensions currently has only one renderer, that is for ordinary pages.

New renderers for different kind of pages, or things like references can be easily added.

One needs to create a new object with the following methods:



You can see details of these methods in ext.popups.renderer.article.js or this patch that adds a renderer for references.

Page previews API
Every project is different, and what displays in your previews is highly dependent on the content inside your wiki.

Popups extension has been optimized to work with Wikipedia-like content (e.g. wikitext).

If your wiki is using a different kind of content handler (for example as is the case for ) it will need to provide its own API.

The API can be written in any language, but the response of the API must match the spec defined here:

Defining new APIs is out of scope for the Popups extension.

Once defined, you can configure page previews to point to your API using configuration option.



已知問題

 * Users of the extension should note that Page Previews requests previews in the content language of the page. If the preview contains a complete translatable block, then it will be translated. If, however, the preview contains an incomplete translateable block – because a sentence is cut off, say – then it isn't translated and will be displayed in the content language of the page. If you are observing this behavior, then you should consider marking up individual sentences in your lead section. T167852 is for a technical audience but has more information on the underlying problem.
 * Longer math formulas cutting off in preview - long math or chemical formulas (formulas wider than the preview width) display as truncated in previews. We were not able to add a gradient in order to indicate that the formula is continued on the article itself.
 * Small files may be in the "Рage information" (action=info), but not in the "Popups". Some requirements are set here - for a portrait image: exact (min) height 250 px & max width 203 px; for a landscape image: exact (min) width 320 px &  max height 200 px . To display, images must be able to become a thumbnail that is larger or equal to these "exact" sizes. (If you are cropping a large image to make a leading picture for an article, be sure that the picture you are creating is not smaller than the specified sizes.)

Extensibility
In MediaWiki 1.40, extensions and skins can extend the page previews functionality with their own custom preview types. It does this by registering a PluginModules attribute in its extension.json or skin.json file that points to a ResourceLoaderModule that can register a preview type. The plugin module should export information about when the preview should be displayed (via selector), and how the preview data should be retrieved (via gateway library). This feature is still in its infancy, has a few bugs (example) and feedback/bug reports via Phabricator are encouraged.

Why can't I copy and paste text from a preview?
At time of writing, the cons of doing so outweigh the pros. Essentially it boils down to decreasing the touch area to read the article in full. Once Page Previews is deployed on English and German Wikipedia, feel free to reopen this task and reignite the discussion, but right now we have no plans.

How can I change the image that I see on preview?
See Extension:PageImages#Image choice.



如何从页面预览中移除内容？
Any element marked with the  class will be stripped from the summary.

Why is content removed from the summary?
Any HTML element marked with the class,  ,  ,  ,  ,   or   will be removed from the summary. If the text should be displayed in the summary, you should under no circumstances use these classes in any templates that are used within the beginning section of an article.



摘要来自哪里？
These are provided by the summary REST API (Wikimedia production wikis) or the API in case your wiki is using the default   gateway.

Why are parenthetical stripped?
There's a good discussion going on in T91344 in Phabricator. If you have any views on this or see any problems relating to this, please let us know there.

Why don't I see Popups outside of content namespaces?
Popups appear on links to pages in content namespaces only. This is a limitation of Popups; TextExtracts are available from other namespaces. You may work around this by appending more namespaces into.

链接

 * Page Previews help page and central feedback page on MediaWiki.org
 * Reference Previews help page and central feedback page on MediaWiki.org
 * Reference Previews main project page on Meta
 * Related research: Wikimedia Performance Team/Authoring Popups: Best Practices