hengdela的博客

websocket-fmp4、websocket-flv 视频播放器 web端 wsplayer

libuv is a multi-platform support library with a focus on asynchronous I/O. It was primarily developed for use by [Node.js][], but it's also used by [Luvit](http://luvit.io/), [Julia](http://julialang.org/), [pyuv](https://github.com/saghul/pyuv), and [others](https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). ## Feature highlights * Full-featured event loop backed by epoll, kqueue, IOCP, event ports. * Asynchronous TCP and UDP sockets * Asynchronous DNS resolution * Asynchronous file and file system operations * File system events * ANSI escape code controlled TTY * IPC with socket sharing, using Unix domain sockets or named pipes (Windows) * Child processes * Thread pool * Signal handling * High resolution clock * Threading and synchronization primitives

FreeTDS is a free implementation of Sybase's DB-Library, CT-Library, and ODBC libraries. FreeTDS builds and runs on every flavor of unix-like systems we've heard of (and some we haven't) as well as Win32 (with or without Cygwin), VMS, and Mac OS X. Failure to build on your system is probably considered a bug. It has C language bindings, and works also with Perl and PHP, among others.

坐标转换问题的详细了解对于测量很重要，那么请和我一起来讨论这个问题。 首先，我们要弄清楚几种坐标表示方法。大致有三种坐标表示方法：经纬度和高程，空间直角坐标，平面坐标和高程。 我们通常说的WGS-84坐标是经纬度和高程这一种，北京54坐标是平面坐标和高程着一种。 现在，再搞清楚转换的严密性问题，在同一个椭球里的转换都是严密的，而在不同的椭球之间的转换是不严密的。举个例子，在WGS-84坐标和北京54坐标之间是不存在一套转换参数可以全国通用的，在每个地方会不一样，因为它们是两个不同的椭球基准。 那么，两个椭球间的坐标转换应该是怎样的呢？一般而言比较严密的是用七参数法（包括布尔莎模型，一步法模型，海尔曼特等），即X平移，Y平移，Z平移，X旋转，Y旋转，Z旋转，尺度变化K。要求得七参数就需要在一个地区需要3个以上的已知点，如果区域范围不大，最远点间的距离不大于30Km(经验值)，这可以用三参数（莫洛登斯基模型），即X平移，Y平移，Z平移，而将X旋转，Y旋转，Z旋转，尺度变化K视为0，所以三参数只是七参数的一种特例。在本软件中提供了计算三参数、七参数的功能。 在一个椭球的不同坐标系中转换可能会用到平面转换，现阶段一般分为四参数和平面网格拟合两种方法，以四参数法在国内用的较多，举个例子，在深圳既有北京54坐标又有深圳坐标，在这两种坐标之间转换就用到四参数，计算四参数需要两个已知点。更精确的可以提供网格拟合数据,本软件提供计算和应用四参数的功能,也提供了网格拟合的功能

Note that this is a text-only and possibly out-of-date version of the wiki ReadMe, which is located at: http://code.google.com/p/tesseract-ocr/wiki/ReadMe Introduction ============ This package contains the Tesseract Open Source OCR Engine. Originally developed at Hewlett Packard Laboratories Bristol and at Hewlett Packard Co, Greeley Colorado, all the code in this distribution is now licensed under the Apache License: ** Licensed under the Apache License, Version 2.0 (the "License"); ** you may not use this file except in compliance with the License. ** You may obtain a copy of the License at ** http://www.apache.org/licenses/LICENSE-2.0 ** Unless required by applicable law or agreed to in writing, software ** distributed under the License is distributed on an "AS IS" BASIS, ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ** See the License for the specific language governing permissions and ** limitations under the License. Dependencies and Licenses ========================= Leptonica is required. (www.leptonica.com). Tesseract no longer compiles without Leptonica. Libtiff is no longer required as a direct dependency. Installing and Running Tesseract -------------------------------- All Users Do NOT Ignore! The tarballs are split into pieces. tesseract-x.xx.tar.gz contains all the source code. tesseract-x.xx.<lang>.tar.gz contains the language data files for <lang>. You need at least one of these or Tesseract will not work. Note that tesseract-x.xx.tar.gz unpacks to the tesseract-ocr directory. tesseract-x.xx.<lang>.tar.gz unpacks to the tessdata directory which belongs inside your tesseract-ocr directory. It is therefore best to download them into your tesseract-x.xx directory, so you can use unpack here or equivalent. You can unpack as many of the language packs as you care to, as they all contain different files. Note that if you are using make install you should unpack your language data to your source tree before you run make install. If you unpack them as root to the destination directory of make install, then the user ids and access permissions might be messed up. boxtiff-2.xx.<lang>.tar.gz contains data that was used in training for those that want to do their own training. Most users should NOT download these files. Instructions for using the training tools are documented separately at Tesseract wiki http://code.google.com/p/tesseract-ocr/w/list Windows ------- Please use installer (for 3.00 and above). Tesseract is library with command line interface. If you need GUI, please check AddOns wiki page http://code.google.com/p/tesseract-ocr/wiki/AddOns#GUI If you are building from the sources, the recommended build platform is VC++ Express 2008 (optionally 2010). The executables are built with static linking, so they stand more chance of working out of the box on more windows systems. The executable must reside in the same directory as the tessdata directory or you need to set up environment variable TESSDATA_PREFIX. Installer will set it up for you. The command line is: tesseract imagename outputbase [-l lang] [-psm pagesegmode] [configfiles...] If you need interface to other applications, please check wrapper section on AddOns wiki page: http://code.google.com/p/tesseract-ocr/wiki/AddOns#Tesseract_3.0x Non-Windows (or Cygwin) ----------------------- You have to tell Tesseract through a standard unix mechanism where to find its data directory. You must either: ./autogen.sh ./configure make make install sudo ldconfig to move the data files to the standard place, or: export TESSDATA_PREFIX="directory in which your tessdata resides/" In either case the command line is: tesseract imagename outputbase [-l lang] [-psm pagesegmode] [configfiles...] New there is a tesseract.spec for making rpms. (Thanks to Andrew Ziem for the help.) It might work with your OS if you know how to do that. If you are linking to the libraries, as Ocropus does, please link to libtesseract_api. History ======= The engine was developed at Hewlett Packard Laboratories Bristol and at Hewlett Packard Co, Greeley Colorado between 1985 and 1994, with some more changes made in 1996 to port to Windows, and some C++izing in 1998. A lot of the code was written in C, and then some more was written in C++. Since then all the code has been converted to at least compile with a C++ compiler. Currently it builds under Linux with gcc4.4.3 and under Windows with VC++2008. The C++ code makes heavy use of a list system using macros. This predates stl, was portable before stl, and is more efficient than stl lists, but has the big negative that if you do get a segmentation violation, it is hard to debug. The most recent change is that Tesseract can now recognize 39 languages, including Arabic, Hindi, Vietnamese, plus 3 Fraktur variants is fully UTF8 capable, and is fully trainable. See TrainingTesseract for more information on training. Tesseract was included in UNLV's Fo