GlyphIndexContact
Email support@glyphindex.site for GlyphIndex questions, bug reports, and content corrections.
Contact
Email support@glyphindex.site for questions, bug reports, or content corrections. This page does not collect or send reports, and the site has no contact form. Please do not include passwords or private documents in your message.
Prepare a useful report
Include a short example that reproduces the problem. Name the page and action, and use a non-sensitive sample rather than a private document.
- The page path and tool or collection name.
- The smallest non-sensitive input that shows the issue, including code points for invisible characters.
- The action you selected and the result you expected.
- The actual result or exact error message.
- Browser name and version, plus whether the issue occurs on a narrow or wide screen.
Page: /tools/codepoint-converter/
Mode: Code points → text
Input: U+2665
Expected: ♥
Actual: [describe what appeared]
Browser: [name and version]For a content correction, quote the sentence or table row and link to a primary source if you have one. For a display problem, include both a screenshot and the code points when possible: they show different parts of the issue.
Help you can use now
Select the manual-copy fallback and check the pasted value.
Read inspector resultsIdentify a suspicious invisible or multi-code-point sequence.
Local favorites and storageUnderstand saving failures and clearing local favorites.
Method and sourcesCheck the data version and computation boundaries.
Leave passwords, access tokens, account details, and private source text out of the example. A short invented sample is usually easier for someone else to reproduce.