About Anit Kumar Tarafdar
Creator and maintainer of Invisible Text Copy. I design, build, test, and document this tool so you can generate and verify zero-width and whitespace characters in a clean, predictable way.
Profile
| Category | Details |
|---|---|
| Name | Anit Kumar Tarafdar |
| Role | Founder and Lead Developer Product Engineering Data |
| Location | West Bengal, India |
| Focus areas | Unicode whitespace and zero-width characters, normalization, line breaking, text segmentation, accessibility, testing across apps and browsers |
| Skills | HTML, CSS, JavaScript, Node, Python, basic PHP, build tooling, UI performance, analytics setup, structured data |
| Knowledge | Unicode UAX 14 (Line Breaking), UAX 15 (Normalization), UAX 29 (Text Segmentation), UCD basics |
| Education | B.Tech, Government College of Engineering and Leather Technology |
| Languages | English, Bengali |
| Online | LinkedIn • GitHub |
| Contact | [email protected] |
About the author
I build small, focused tools that solve specific problems. Invisible Text Copy grew from my need to test zero-width characters across editors, devices, and browsers. Many guides listed characters but did not explain how software keeps, strips, or re-encodes them. I track that behavior, publish a support matrix, and keep the site fast and simple.
I prefer client-side logic, minimal dependencies, and clear notes about limits. I also include privacy details and references to the Unicode Standard so anyone can verify the behavior or reproduce tests.
Role in this website
- Product and UX
Define scope, write the About, FAQ, and Support Matrix. Keep flows simple. Avoid surprises when copying invisible output. - Research and testing
Read relevant Unicode docs. Compare character behavior across Chrome, Firefox, Safari, Edge, iOS, Android, Google Docs, Apple Notes, and common web editors. - Engineering and tooling
Build the generator. Add a second generator for fallback. Keep DOM light. Add accessible labels and copy feedback. - Documentation and changelog
Explain each character by code point and expected behavior. Publish the matrix with dates. Note when apps change behavior. - Accessibility and quality
Consider screen readers and copy flows. Prefer semantic HTML and CSS for spacing. Warn about pitfalls. Offer safe alternatives. - Operations
Host, monitor, and handle feedback. Triage bug reports. Update the Support Matrix and the Changelog.
Generators I built
I publish generators as separate pages. They cover:
- Mapped alphabets: bold, italic, cursive, double-struck, bubble, monospace, small caps
- Combining-mark effects: underline, strikethrough, outline, neon, shadow, glow, wavy, cracked, distorted, zalgo
- Directional: reverse, mirror, upside down, curved
- Encodings: binary, Morse, Braille
- Script swaps and themed: Greek, Cyrillic, Runic, leetspeak, emoji decorations, regional flags
- Invisible text: zero-width space (U+200B), braille blank (U+2800)
Methodology snapshot
I publish a full methodology on the site. Here is the short version.
- Environments
Windows 11, macOS, iOS, Android. Hardware varies from low to mid range devices. - Browsers
Chrome, Firefox, Safari, Edge. Test stable releases after notable updates. - Apps and editors
Google Docs, Apple Notes, basic text editors, popular web editors.
I test plain paste and rich paste, and export or save where that changes behavior. - What I record
Keep, Strip, Re-encode, or Varies. I note paste paths, normalization steps, and any rendering quirks. - When I update
After browser or OS releases that affect text, or when editors change paste pipelines. I log dates in the matrix.
What I believe about responsible use
Invisible characters are useful for testing, formatting, soft breaks, and language processing checks. They are not for hiding keywords or cloaking text. I block or discourage uses that break platform rules. The site explains risks and links to the Privacy Policy and Terms.
Notable work on this site
- A Changelog that lists test runs and any behavior changes.=
- Privacy by design. The generator runs in your browser. The site does not send pasted content to a server. See the Privacy Policy for analytics details.
Contact and feedback
Corrections and questions are welcome. Email [email protected].
Include the character, the app or browser, the device and OS, the paste path, and screenshots if possible.
Confirmed fixes go to the Changelog.
Links
Last updated
2025-09-18