daizw / judou Goto Github PK

rt

Original issue reported on code.google.com by twinsant on 12 Jun 2009 at 5:05

问题描述：
       目前的mm_seg, atom_seg, ch_seg,rmm_seg等函数内部，存在多个进行编码转换的地方，使得编码处理位置分散，一旦代码改动，极易出错。同时，几处代码并没有使用全局的ENCODING变量，而是直接使用'utf-8'制定编码，
问题解决：
       附件中的patch将所有函数修改为只支持unicode内码，利用create_local_seg()生成支持转吗的分词函数。函数接口与当前测试用例兼容。
补丁方法：judou/目录下执行patch -p1 < path_to/encoding-fix-r43.patch

Original issue reported on code.google.com by [email protected] on 18 Oct 2010 at 9:20

Attachments:

• encoding-fix-r43.patch

讨论下具体的细的执行任务吧。

Original issue reported on code.google.com by twinsant on 1 Oct 2009 at 9:39

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 3:00

http://www.python.org/dev/peps/pep-0008/

Original issue reported on code.google.com by twinsant on 12 Jun 2009 at 5:05

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 2:59

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 3:00

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 2:59

setup.py is broken

Original issue reported on code.google.com by lyxint on 23 Apr 2012 at 12:06

在 google code 的 Administer -> Issue Tracking -> Activity Notifications 
下面，设上邮件列表的地址
吧。这样大家可以直接在邮件列表里看见新提的issue和comment

Original issue reported on code.google.com by hongqn on 6 Oct 2009 at 2:41

What steps will reproduce the problem?

1. http://twitter.com/marchliu/status/4678738608
2. 
項目的白皮書仍是slides形式，缺少詳盡和條理性強的較正式��
�檔

What is the expected output? What do you see instead?
希望和別人提到此項目時，能很快說出其不同之處，為何值��
�做。
這樣會更有利于宣傳和吸引開發者。

todo:

整理項目白皮書，用正式的文檔形式發布，明確項目定位和��
�標。

Original issue reported on code.google.com by [email protected] on 7 Oct 2009 at 12:37

目标一：便于安装发行，分离字典系统和算法系统
目标二：各种基于基础代码的小应用，让大家意识到分词的��
�趣

Original issue reported on code.google.com by twinsant on 1 Oct 2009 at 9:40

and other libs.

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 3:03

以后调试能省不少力气

Original issue reported on code.google.com by [email protected] on 13 Jun 2009 at 2:06

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 3:01

by pem

Original issue reported on code.google.com by twinsant on 4 Oct 2009 at 2:59