{"action":"created","issue":{"url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/238","repository_url":"https://api.github.com/repos/tesseract-ocr/tesseract","labels_url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/238/labels{/name}","comments_url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/238/comments","events_url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/238/events","html_url":"https://github.com/tesseract-ocr/tesseract/issues/238","id":136371518,"number":238,"title":"Arabic language (right to left in writing) stored (left to right) after create PDF Searchable","user":{"login":"tbadran","id":17473681,"avatar_url":"https://avatars.githubusercontent.com/u/17473681?v=3","gravatar_id":"","url":"https://api.github.com/users/tbadran","html_url":"https://github.com/tbadran","followers_url":"https://api.github.com/users/tbadran/followers","following_url":"https://api.github.com/users/tbadran/following{/other_user}","gists_url":"https://api.github.com/users/tbadran/gists{/gist_id}","starred_url":"https://api.github.com/users/tbadran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbadran/subscriptions","organizations_url":"https://api.github.com/users/tbadran/orgs","repos_url":"https://api.github.com/users/tbadran/repos","events_url":"https://api.github.com/users/tbadran/events{/privacy}","received_events_url":"https://api.github.com/users/tbadran/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2016-02-25T12:16:31Z","updated_at":"2016-02-26T20:23:50Z","closed_at":null,"body":"I have tested latest release 3.05 on windows platform to OCR Arabic document to PDF (searchable) and when choose text from output PDF file it seems stored in opposite (left to right) and letters should be stored from (Right to left)!!!\r\n\r\ni.e. original text In Arabic is\r\nمرحبا\r\nStored in PDF as text as\r\nابحرم"},"comment":{"url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/comments/189468045","html_url":"https://github.com/tesseract-ocr/tesseract/issues/238#issuecomment-189468045","issue_url":"https://api.github.com/repos/tesseract-ocr/tesseract/issues/238","id":189468045,"user":{"login":"amitdo","id":13571208,"avatar_url":"https://avatars.githubusercontent.com/u/13571208?v=3","gravatar_id":"","url":"https://api.github.com/users/amitdo","html_url":"https://github.com/amitdo","followers_url":"https://api.github.com/users/amitdo/followers","following_url":"https://api.github.com/users/amitdo/following{/other_user}","gists_url":"https://api.github.com/users/amitdo/gists{/gist_id}","starred_url":"https://api.github.com/users/amitdo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amitdo/subscriptions","organizations_url":"https://api.github.com/users/amitdo/orgs","repos_url":"https://api.github.com/users/amitdo/repos","events_url":"https://api.github.com/users/amitdo/events{/privacy}","received_events_url":"https://api.github.com/users/amitdo/received_events","type":"User","site_admin":false},"created_at":"2016-02-26T20:23:50Z","updated_at":"2016-02-26T20:23:50Z","body":"@roozgar\r\n\r\nFirst, although I contributed some code and documentation to the project, I'm not an insider. 99% of the Tesseract code is written by devs from Google.\r\n\r\nThe current OCR engine used for Arabic is 'Cube'.\r\n\r\nWhat Ray said/wrote about Cube?\r\n\r\n> Hmm cube.\r\nIts a dead-end. It didn't really contribute very much so nobody at google wants to work on it...  The *only* thing cube was really good at was Hindi. \r\n\r\n>Cube added Convolutional NN, but improvement was\r\ndisappointing.\r\n\r\n>###Cube\r\n>\r\n* Standard Convolutional Neural Network character classifier.\r\n* Uses over-segmentation and (a different) beam search for\r\ncharacter segmentation.\r\n* Implemented as an alternative word recognizer.\r\n* Achieves about 50% reduction in errors on Hindi when run together\r\nwith Tesseract’s word recognizer.\r\n* Improvement for other languages disappointing: few % for major\r\nslow-down (3x).\r\n* Training code unmaintaine, unused.\r\n\r\n>The next version is likely to include a new classifier implementation that uses neural nets. (bye bye cube probably.)\r\n\r\nIt seems that Ray is planning to release soon (in march?) a new (beta?) version of Tesseract (4.0?), that will include a new OCR engine based on LSTM.\r\n\r\n\r\nWhat Ray said/wrote about LSTM?\r\n\r\n>LSTM Integration\r\n* LSTM code based on OCROpus Python implementation.\r\n* Expanded capabilities including 2-D, and input of Tesseract\r\nfeatures, as well as images.\r\n* Fully integrated with Tesseract at the line level. (May change)\r\n* Visualization with existing Viewer API.\r\n* Training code included (unlike cube).\r\n\r\nWith LSTM, OCR for printed Arabic (not real handwrite) can reach 95% character accuracy.\r\n\r\n\"Offline Printed Urdu Nastaleeq Script Recognition\r\nwith Bidirectional LSTM Networks\"\r\nhttp://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.447.4577&rep=rep1&type=pdf"}}