Contact
Contact Cursive Translator
The email address published for this site is [email protected]. This page carries no contact form and no message field; nothing you write is submitted through it.
This page states what this site asks you to put in a message and what it asks you to leave out. It states no reply time, no support hours and no outcome for anything you send. Treat the sections below as site policy rather than as a description of what happens after you press send.
Subjects this address is published for
Four subjects, and what this site asks you to include with each.
- Faults in a tool. A control that does nothing, a request that returns an error, or behaviour that differs from what the page says. Write the steps in order, from loading the page to the point where it went wrong.
- Accessibility problems. Keyboard traps, focus you cannot see, controls a screen reader announces wrongly or not at all, contrast you cannot read, text that breaks when zoomed or on a narrow viewport. Name the assistive technology and its version.
- Corrections. A statement in how to read cursive, how to read old cursive or can AI read cursive? that you believe is wrong. Quote the sentence and say what you think is wrong with it.
- Privacy questions. Anything the privacy statement leaves unclear. Ask the question in words; do not send an example of your data with it.
What a report should contain
This is the list this site asks you to work through before sending a fault report. It is a request, not a promise about what follows from it.
- The page URL. The exact address you were on. This site publishes four tool pages and five written pages, and "the cursive page" does not identify one of them.
- Browser and device. Name and version, the operating system, and whether it was a phone, tablet or desktop. The text to handwriting page draws with whichever of its fixed font names your device has, so the device is part of the report.
- The steps you took. Numbered, from loading the page to the point where the behaviour changed.
- What you expected and what you saw. Write both.
- Any error text. Copy the message shown on screen as text rather than describing it from memory. The upload tool prints its errors in the status line under the buttons.
What this site asks you never to send
Site policy, stated as a rule rather than as advice. Do not attach or paste any of the following to a message sent to this address:
- Handwriting images or scans. Not the letter, the certificate, the medical note, the diary page or the ledger — whatever it was you were trying to read.
- Private documents of any kind, including material about other people who have not agreed to it.
- API keys, tokens or passwords. No message to this address requires a credential.
- Personal identifiers — names, addresses, account numbers, dates of birth, medical or financial detail.
This site makes no statement about the security of email in transit or at rest, and gives no undertaking about how a message sent to this address is stored or handled. Write the message on the assumption that nothing in it is protected.
Describing a transcription problem in words
Do not attach the page. Describe it instead, using these fields:
- The kind of document. A personal letter in ink, a parish register, a filled-in form, a recipe card, a page of lecture notes.
- The hand and the medium. Joined or partly printed, pencil or ink, faded, bled through from the reverse, written across an earlier page, in a language other than English.
- The capture. Phone photo or flatbed scan, roughly what resolution, lit evenly or with a shadow across it, straight on or at an angle, and the file type and size.
- What the page did. The exact text of the status line: an error message, "No handwriting was recognised in this image", or a transcript that was returned but did not match the page.
- An invented stand-in. To show a misreading without quoting your document, make up a comparable pair of words and say so — for example: "a word like Margaret came back as a word like Mayaret." Label it as invented.
If a sample image is unavoidable, write a line of your own on blank paper, photograph that, and send it in place of the document. What this site's request flow actually consists of is set out in can AI read cursive? and in about this site.
The scope of this address
No reply time is stated, no support hours are stated, and no outcome is undertaken for any report, correction or question sent to this address. Nothing on this page should be read as an undertaking that a message will be answered, investigated or acted on.
This address is not a transcription service, and this site does not offer to read a document on your behalf. The twelve pages listed below, together with this one, are the whole of what is published here. Use of the site is governed by the terms, and the request path is described on the privacy page.
Pages you can check first
Each of these states what it covers. Reading the relevant one before writing is a suggestion, not a condition.
- Cursive translatorThe upload form: accepted types, the 6 MB cap, and the editable box the returned text is placed in.
- Handwriting to textThe same form and the same limits, written for notes, forms and lists.
- Decipher handwritingThe same form and the same limits, written around a checklist for reviewing the returned draft.
- Text to handwritingCanvas controls whose drawing script sends neither typed text nor canvas data; page analytics is disclosed separately.
- How to read cursiveAn observation worksheet: inspect, transcribe, mark uncertainty, compare, verify.
- Cursive reading practiceFour drill sets and a ten-item reading test, with the answer key on the same page.
- How to read old cursiveProvenance fields, exact transcription rules and a four-mark notation.
- Can AI read cursive?This site's request flow, and a test protocol you run on your own page.
- Should cursive be taught in schools?Five reasons for, five against, and what the written standards require.
- AboutWhat the site is built out of and what it does not state.
- PrivacyThe request path, the analytics tag and the site policy.
- TermsThe site terms for using these pages.
The published address is [email protected].