Tablora · Library
Review a blank record without silently deleting it
A blank line in pasted CSV becomes a one-cell row. See how the inspector reports it and how to decide whether that record should stay.
What a blank line becomes after parsing
When you copy rows from several exports or pages into one block of text, an empty line often slips in between them. The inspector does not quietly drop it. An empty physical line between two records is parsed as a row with a single empty cell, and it stays in the result so that you can see it.
Keeping it visible matters because a blank line can be meaningful. It may mark where one page or batch ended, it may sit where a record was lost during copying, or it may simply be an accident. The parser cannot tell these apart; you can, by looking at the source.
Finding the short row
- Paste the text into Table text and choose the Delimiter, or leave Detect delimiter selected.
- Press Calculate and look at Rows with a different width. A blank line counts there because it has one cell instead of the header's width.
- Scan the preview for an empty row and note what comes before and after it.
- Open the original export or page at the same place and decide whether a record is missing, the gap is a separator, or the line should go.
- Edit a copy of your text, then press Calculate again and confirm the width count is what you expect.
- If you think the blank line marks a page boundary, write down which record follows it before you remove it.
The a,b example in numbers
The page example is a header a,b, an empty line, and the record 1,2, with comma as the Delimiter. The inspector reports 3 rows and 2 columns. Row 2 has 1 cell, so Rows with a different width shows 1. Nothing was converted and no cell text changed.
One detail is easy to miss: a single line break at the very end of the text does not add an extra row. Only an empty line between records shows up as a short row, so a clean file that ends with a newline still reports the right count.
Blank rows in the app versus the browser
The Tablora app reads tables from PDFs, photos and scans, and it leaves out rows and columns in which every cell is empty, because page margins can look like empty cells. If you need a gap preserved, for example between two batches, keep that boundary in your own notes or split the work into separate tables.
In the browser tool, delete the blank line only after you have checked the source. Deleting every short row by habit can join two batches that were meant to stay apart, or hide the place where a record went missing.
Original synthetic example
- Input
- a,b 1,2
- Delimiter
- ,
- Expected records
- 3
- Columns in the first record
- 2
- Width difference
- Row 2 has 1 cells