当前阅读模式似乎只会提取标题、正文和描述字段，而实际上作者和发布时间对于文章来说也是蛮重要的信息。但简阅没有相关字段可以填入匹配规则。希望可以添加相关字段。
如 Firefox 的阅读模式等都会提取作者和发布时间，如 Mozilla 维护的 Readibility.js
会匹配：

    // property is a space-separated list of values
    var propertyPattern = /\s*(dc|dcterm|og|twitter)\s*:\s*(author|creator|description|title|site_name)\s*/gi;

    // name 

See the Intermezzo here:

https://docs.python.org/3/tutorial/controlflow.html#intermezzo-coding-style

Which does a good job of summarizing PEP8 and benefits from existing in the official Python tutorial.

URL:- https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
The below code snippet is not coming in the output pdf.
mvn --version
However, another code snippet appearing properly
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
![image](https://user-images.githubusercontent.com/354596/47339163-16508d00-d6e6-11e8-872b-a1f10d96d55

There are some new functions added on 0.5.7 that are not in the README.md so the used has to read the code in order to know that they exist. The ideal would be having them all in the README with the others

Graby configuration: (in services.yml on a Wallabag instance)

    wallabag_core.graby:
        class: Graby\Graby
        arguments:
            -
                http_client:
                    ua_browser: 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)'
                    rewrite_url:
                        'weibo.com':
                            '

刚迎来了第三位成员, 俗话说三人成群, 也许是时候讨论一下这个社区的运行方式了. 本人是第一次在github新建orgnization, 之前参与过另一个以外国程序员为主的org, 觉得大氛围挺专业, 而且这种公开讨论的形式效率挺高. 希望大家随意聊聊. 比如对这个社区的期望, 个人的目标, 如何利用github进行主题讨论, 任何对我的问题, 或者任何其他话题. @buyouyuan @jeromechan

下面是已有的讨论较多的话题. 为避免此帖太长, 如对其中一些有兴趣可以直接在那里发表; 如果有新主题或不同意见非常欢迎开新issue讨论(类似论坛开新帖):

• 发展中文API
  • 创建新API
  • [汉化已有的英文API](https://gi

As you can see browsing Cadmium shards source code, several entities (for lack of a better word) are declared in different locations and in different ways.

This issue is not just a namespace or redundancy issue but we'd benefit by having fundamental classes or structs describing the tokens, sentences and documents we're dealing with.

I've started in the pos_tagger declaring such structs an