{"action":"created","issue":{"url":"https://api.github.com/repos/tmbdev/clstm/issues/26","labels_url":"https://api.github.com/repos/tmbdev/clstm/issues/26/labels{/name}","comments_url":"https://api.github.com/repos/tmbdev/clstm/issues/26/comments","events_url":"https://api.github.com/repos/tmbdev/clstm/issues/26/events","html_url":"https://github.com/tmbdev/clstm/issues/26","id":97927586,"number":26,"title":"Future / Documentation / Roadmap / Stuff of that sort","user":{"login":"tobimensch","id":9920531,"avatar_url":"https://avatars.githubusercontent.com/u/9920531?v=3","gravatar_id":"","url":"https://api.github.com/users/tobimensch","html_url":"https://github.com/tobimensch","followers_url":"https://api.github.com/users/tobimensch/followers","following_url":"https://api.github.com/users/tobimensch/following{/other_user}","gists_url":"https://api.github.com/users/tobimensch/gists{/gist_id}","starred_url":"https://api.github.com/users/tobimensch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tobimensch/subscriptions","organizations_url":"https://api.github.com/users/tobimensch/orgs","repos_url":"https://api.github.com/users/tobimensch/repos","events_url":"https://api.github.com/users/tobimensch/events{/privacy}","received_events_url":"https://api.github.com/users/tobimensch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-29T12:47:41Z","updated_at":"2015-08-21T17:20:16Z","closed_at":null,"body":"Hi,\r\n\r\nI was working on a GUI for scanning PDF documents and I was looking\r\nfor a way to have correct OCR under Linux and to sandwich the text into the generated PDFs.\r\n\r\nObviously the state of open source OCR isn't stellar, everything I tried wasn't exactly a breeze\r\nto setup and most importantly the actual detection was quite bad for example with tesselact and\r\nall the other known open source projects.\r\n\r\nThen I read about ocropy/ocropus/clstm, and finally was relieved that someone was at last working from scratch on an innovative modern approach, that was actually being actively developed and some of the results I saw in one online tutorial where a guy modified the model for typewriter fonts and it worked rather good were promising.\r\n\r\nSo I got ocropy to work on Fedora and tried it with the standard model on a simple plain PDF document I had scanned. The results were just as terrible as with the other open source OCRs, if not worse, although it really is a high resolution scan with normal looking fonts. I felt disappointed to be honest.\r\n\r\nFrom the documentation/README.md and so on I didn't get a lot of information about where the project is going and where it might need some help. The basic concepts are explained well, but I didn't get a good picture of where the problems of the project are and what is done to solve them.\r\nIt seems \"the model\" is just a file that was uploaded sometime ago, but doesn't get actively maintained and improved currently.\r\n\r\nI  would be interesting to know what the obstacles currently are for supporting more fonts/fontstyles and so on. Is there any plan for what the next milestones should be? Is there any guide how people can best help the project to fix bugs, add features, refactor code, improve models and so on.\r\n\r\nI'm writing this in this project, because I really see it as the same project basically.\r\n\r\nTo summarize:\r\n- It would be nice if you kept a detailed TODO list for clstm and ocropy\r\n- It would be nice to have a Roadmap for both those projects as a whole where\r\nimportant milestones are defined\r\n- The documentation should explain how people can help with development,\r\nespecially how models can be created and improved upon, so that they can\r\neventually be included as \"official\" models. Do you for example require some\r\nexample PDFs from people that currently don't work well in order for you to\r\nimprove future models?\r\n\r\nI'm sorry, if this doesn't fit into \"issues\". Feel free to remove or move this, I just\r\nwanted to express that what's going on with ocropy/clstm development seems\r\nlike a blackbox from the outside.\r\n "},"comment":{"url":"https://api.github.com/repos/tmbdev/clstm/issues/comments/133501392","html_url":"https://github.com/tmbdev/clstm/issues/26#issuecomment-133501392","issue_url":"https://api.github.com/repos/tmbdev/clstm/issues/26","id":133501392,"user":{"login":"tmbdev","id":333887,"avatar_url":"https://avatars.githubusercontent.com/u/333887?v=3","gravatar_id":"","url":"https://api.github.com/users/tmbdev","html_url":"https://github.com/tmbdev","followers_url":"https://api.github.com/users/tmbdev/followers","following_url":"https://api.github.com/users/tmbdev/following{/other_user}","gists_url":"https://api.github.com/users/tmbdev/gists{/gist_id}","starred_url":"https://api.github.com/users/tmbdev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmbdev/subscriptions","organizations_url":"https://api.github.com/users/tmbdev/orgs","repos_url":"https://api.github.com/users/tmbdev/repos","events_url":"https://api.github.com/users/tmbdev/events{/privacy}","received_events_url":"https://api.github.com/users/tmbdev/received_events","type":"User","site_admin":false},"created_at":"2015-08-21T17:20:16Z","updated_at":"2015-08-21T17:20:16Z","body":"> It would be nice if you kept a detailed TODO list for clstm and ocropy. It would be nice to have a Roadmap for both those projects as a whole where important milestones are defined.\r\n\r\nUnfortunately, the development of ocropy and clstm is largely driven by a lot of internal project timelines and other considerations. I'll try to add some comments to the READMEs, though."}}