LineBreaks

Contact

Email rlaejrtn16@gmail.com. There is no contact form on this site, deliberately — a form would need a server, and the whole point of LineBreaks is that there isn't one.

Reporting a wrong result

Every table here is generated by running the tool, so a wrong cell means a wrong function, which makes the report worth a great deal and the fix quick. The most useful message contains four things:

  1. The exact input. If it contains invisible characters, switch on Show invisible characters and describe what the badges say, or paste the byte sequence.
  2. The mode and any options you changed.
  3. What you got.
  4. What you expected, and why. The "why" is the part that turns a report into a test case.

Reporting a sourcing problem

If a character name, a specification quote or an attribution on this site is wrong, out of date, or cites an edition that has moved on, that is the most serious kind of error here and it will be corrected quickly. The about page lists every source with a note on how it was obtained; pointing at the row is enough.

Suggesting a character

The tool handles a specific set of invisible characters. If your text carries one it does not recognise — a break form, a space variant, an invisible formatting character — send an example. The whitespace inventory is generated by scanning Unicode categories, so adding a genuine gap is usually a one-line change.

Things this address cannot help with

  • Recovering text you lost. Nothing you paste is stored anywhere, including here, so there is nothing to recover. The browser's undo in the input box is the only history that exists.
  • Fixing a PDF or a document. This site works on text you have already copied out. Extraction problems — wrong reading order, missing spaces, mangled ligatures — happen before the text reaches the box.
  • Advice about your data. If a file matters, keep a copy before transforming it. That is the whole of the advice.

What makes a report easy to act on

Almost every wrong result here is a disagreement about what counts as a line break or what counts as blank, and bytes settle those disagreements where argument cannot. So the one thing worth putting in a message above all else is the byte sequence of the input. Press Show invisible characters, and if the badges do not already tell the story, paste a short reproduction — five lines that fail are worth more than five hundred that mostly work, and the whole document rarely helps.

Some disagreements are about policy, and those are worth sending too — say so, and say why. Several behaviours on this site were decided rather than discovered: whether a line holding a no-break space counts as blank, whether a form feed should split a line, whether the hyphen in well-known survives a wrap. Each of those is documented on the page that implements it, with the reasoning, precisely so that disagreeing with the choice is possible. A message that says "I would have chosen the other way, because…" is a useful message; it can turn into a new option, where a bug report would have turned into a fix.

What happens to a report

Every table on this site is generated at build time by calling the same functions the tool calls, and the test suite asserts the cells and reads the shipped prose looking for sentences that no longer match the data. That means a genuine bug report turns into a test case first and a fix second, and the fix cannot silently break a sentence elsewhere on the site — the build fails instead. It also means the turnaround on a reproducible report is short, because there is no manual checking step to schedule.

Reports that cannot be reproduced are still worth sending. "This document came out wrong and here it is" is a perfectly good message even without a diagnosis; working out which of the twenty invisible characters was responsible is the part this project is for.

Reuse

The embed snippet on the front page puts the converter on your own site without a build step. If you want to reproduce one of the tables in an article, please link back — the tables are generated at build time, so a copy taken today can silently go stale while the original stays correct.