Text guides

Compare line endings and non-breaking spaces in a UTF-8 file

·

Use the original and marked outputs to check whether a text field changed during import. A line break can look the same on screen while using different code points in the file.

Whitespace Visualizer

Find the three line-ending styles in one sample

Select Load example. The first row contains a TAB between Item and Qty, followed by CRLF. The next two rows end in LF and CR respectively. A separate Unicode LINE SEPARATOR occurs before the Hebrew word.

In the summary each of CRLF, LF and CR has a count of one. CRLF groups two code points into one occurrence. For a file of your own, use Open UTF-8 text file before comparing endings. Editing the text in the browser field can convert carriage returns to line feeds.

Find the three line-ending styles in one sample
BreakCode pointsMarker
Windows-style pairU+000D U+000ACRLF
Line feedU+000ALF
Carriage returnU+000DCR
Unicode line separatorU+2028LS

Unicode 17.0 property list including White_SpaceWHATWG textarea API value and newline normalization

Compare the spaces around the quantities

The gap between Tea and 2 has one NBSP at U+00A0. The gap after Coffee has one NNBSP at U+202F. The regular space before 3 is U+0020. Keep Non-breaking spaces selected and turn off Regular spaces to narrow the preview and report.

Choose Download marked text to check the added labels, then Download original for the exact source. If you need to preserve words and quantities together in typeset text, keep the non-breaking spaces. If a machine import expects an ordinary space, compare its input requirements before editing.

Unicode 17.0 property list including White_SpaceUnicode line breaking and non-breaking spaces

Use the download that matches the job

Use Download original to compare file bytes after an import. The tool retains a UTF-8 byte-order mark when present. Use Download JSON report for searchable character labels, counts and source positions after category filtering.

Download marked text for a human review. Its bracketed labels show where selected characters occurred. Text beside the labels can still contain unselected marks, so use the JSON code points when a mark needs a precise identification.

Unicode 17.0 property list including White_SpaceUnicode Character Database and derived properties

Common questions

Why is a normal space counted separately from a non-breaking space?

They have different Unicode code points and line-breaking behavior. The tool leaves the two unchanged and reports them with separate labels and counts.

Why is the selected count lower than the detected count?

The detected count covers every supported mark. The selected count follows the category filters used in the report.

Sources

Put it into practice.

Related guides