Contact
Last updated
We want to hear about incorrect results. A converter that is wrong is worse than no converter at all, and the fastest way to fix one is for someone to send us the exact input.
Reporting a wrong result
Please include the following, so we can reproduce it without a round of questions:
- The page URL, for example
/remove-vietnamese-accents/. - The exact text you entered, copied rather than described.
- What the tool returned.
- What you expected it to return, and — if you have one — a link to the standard or source that says so.
A confirmed defect is fixed in the code, the exact case is added to the tool's test set so it cannot regress, and the page's last-updated date changes. We do not silently edit a page to make it look newer.
Copyright and removal requests
See the DMCA page. Send the notice to the same address with “DMCA” in the subject line and we will respond as set out there.
What we can and cannot help with
| We can help with | We cannot help with |
|---|---|
| A conversion that returns the wrong characters | Tax, legal, medical or religious advice |
| A character your system rejects | Administering your own website or data |
| A missing script or numeral system you need | Recovering data after an accident on your side |
| An accessibility problem with a page | Advertising placements or third-party ad content |
Response time
This is a small independent project, so replies usually take a few business days. Defect reports are read first. If you are writing about an advertisement, note that the ads are served by a third party; we can block a category, but we cannot see the individual ad you were shown.
Before you write
If your problem is invisible characters, the Unicode inspector will usually identify it in a few seconds — paste the text and look for control or format characters. If a spreadsheet value refuses to match, the whitespace cleaner reports how many non-breaking or zero-width characters are present before removing them.
A report that can be acted on
The difference between a report that gets fixed and one that stalls is almost always the input.
“The Base64 tool is broken” cannot be reproduced; “aGVsbG8g5LiW55WM decodes to
hello 世界 in my browser but the tool returns an error” can be reproduced in seconds
and turned into a test.
Copy the text rather than describing it. If the value contains characters you cannot see, the inspector can show you the code points so you can paste them. If the problem depends on a file, say what kind and how big; do not attach a document containing anything confidential.
What happens after you write
- Reproduce. The input is run against the engine, outside the page, to see whether the browser is involved.
- Decide whether it is a bug. Sometimes the output is correct for the rule the tool applies, and the fix is to the page text that described the rule.
- Add a test. The reported case becomes a regression test before the fix, so it cannot come back silently.
- Fix and deploy. The page's last-updated date changes; the correction is noted where it matters.
What we cannot fix
A few reports are outside what the site can control. If an advertisement is covering content, the ad is served by a third-party network — we can report the placement, but we cannot remove a specific creative. If a page will not load because of a network or firewall on your side, the home page being reachable will tell you whether the site is up. And if a result depends on a convention your organisation uses but that is not the one the tool documents, the answer is usually to know which convention you need, not to change the tool.
Feature requests
Suggestions for a missing tool are welcome, and are most useful when they describe the task rather than the interface: “I need to convert a Thai Buddhist year to a Gregorian one” is more actionable than “add a date tool”. A requested tool is only published when it can be implemented correctly and verified against a reference — a converter that guesses is worse than one that does not exist.
Privacy of correspondence
Email sent to the address above is read and kept only as long as needed to resolve the report. Do not send credentials, keys, personal data or anything confidential; for a problem with a sensitive value, reduce it to the smallest input that still shows the bug.
Questions about this page? Contact us.