Google has an open source OCR software called: tesseract-ocr http://code.google.com/p/tesseract-ocr/
Seems there’s a problem with the code, at least in Visual Studio, it does not build successfully. Not sure if it’s true for its Linux version(Tried recently, it works!).
Instead, there’s a free(?) software, which is basically a wrapper for this, called Free OCR: http://softi.co.uk/freeocr.htm
1. SSH tunnel
ssh -g -L <local port>:<remote server>:<remote port> <username on ssh server>@<remote ssh server>
use your password on ssh server
2. mout samba partition on the remote server
smbmount <remote samba share folder> <local folder> -o <windows domain username>, ip=127.0.0.1, port=<local port>
use windows domain password
e.g.
ssh -g -L 9999:*.cs.cmu.edu:139 hwkang@*.cs.cmu.edu
smbmount //*.cs.cmu.edu/samba/hwkang samba1 -o username=hwkang,ip=127.0.0.1,port=9999
I am pretty sure I am not the only one, who would feel frustrated every time reading a paper using hand-waving *-like phrases, “RANSAC-like”, “Tree-like”, etc. If the detail is not important, why would one use it in the paper? If it appears in a paper, please either explain it, or give reference to some sort of technical report.