Select

Seeking Technologies to Analyse Handwritten Text

Background / Description

A school of graphology in the UK needs to analyse handwritten text not from a forensic perspective but following its own rules for measuring various features in the characters, lines and spacings.

Technologies and expertise from academia or industry are sought with capabilities in handwriting analysis, based on these requirements. The type of co-operation may include technical partnerships, licensing, or services agreements.

Technical Specifications

The school of graphology is looking for expertise and technologies to collaborate on the analysis of the handwritten text.

There are several software packages commercially available that analyse handwriting. However, most of them are designed for forensic analysis, i.e. identifying the authorship of a text.

There are also solutions for OCR (optical character recognition) and HTR (handwritten text recognition) that are good for digitising archives, searching through them etc. They do look at some features that graphologists are interested in but not nearly enough.

There is an attachment to this write-up that gives sufficient detail to understand the problem. A graphologist needs to painstakingly measure the features of characters, words, lines and spacings, and export statistically solid measurements. These can then be correlated with personal traits. All the loops, crosses, downstrokes etc. give very interesting observations about the author, but its analysis is not just art, it needs to be thorough and scientific.

It is quite possible that there is freeware out there that will do parts of the job. There is a plugin called GraphJ that promises to do a lot but it is not publicly available just yet. Either way, the school of graphology needs to team up with expertise in software who can exploit the pre-existing code and add bespoke features.

The planned tool should be of great interest to the whole community in this niche market so it can be commercialised.

The type of co-operation may include technical co-operation, a services agreement and licensing. The project may be straightforward enough such that the partner is able to quickly come up with a detailed plan and offer the work as a service. It may also be more complex than currently believed, such that the UK organisation and the partner will need to agree on subtasks and milestones, and where significant further input is needed from the UK organisation's end. Presumably, in either case, the UK organisation wishes to keep the rights to the tool under a software license agreement.

If the partner is already active in an adjacent field, shared ownership of the new tool will be considered.

Supporting Documents

Preferred Business Model

  • R&D Collaboration
  • Licensing
  • Business Collaboration (Joint Venture, Distribution)
  • Others

Make an Enquiry