SimpleWebUtils
ENKO

Document Workflow

Add fixed labels and delimiters to copied lines safely

Add a literal prefix or suffix to copied rows, preserve their original line endings, handle blank lines deliberately, and validate the destination format before import.

Written and tested by Published: Reviewed:

How this workflow was checked

In Add Prefix or Suffix to Every Line, the “Prepare fixed ticket labels without changing CRLF separators” fixture was run without repairing or simplifying its input. We verified the transition from “Confirm what one source line means” to “Decide blank-line and final-delimiter behavior”, compared the final artifact or values, and reviewed “Treating wrapped display text as source lines” plus “Modifying accidental blank rows” as non-success paths.

Each of the three ticket lines received exactly one OPS: prefix, the original order and CRLF separators remained intact, and numbering was not simulated with a fixed string.

Open Add Prefix or Suffix to Every Line | Preserve Line Endings

Problem

Adding one label or delimiter to hundreds of copied rows by hand is slow and easy to misalign. A broad find-and-replace can also normalize Windows line endings, add text to accidental blank rows, create an unwanted trailing comma, or produce output that looks like valid JSON or SQL without being valid. The reliable approach is to preserve the source, define one literal insertion rule, compare exact line counts, and validate the final destination syntax separately.

When to use this

  • A spreadsheet column was copied as one plain-text value per line and every value needs the same fixed marker.
  • Log or support-note lines need one environment, ticket, or source label before sharing.
  • A Markdown draft needs the same bullet marker before each nonblank item.
  • A plain import list needs a comma or semicolon after each value, with the final delimiter handled explicitly.
  • A Windows, Unix, classic Mac, or mixed-ending text file must retain its original line separators during a small edit.

Steps

  1. Step 1

    Keep an untouched source copy

    Save the original clipboard block or file before editing. Note whether the source came from a spreadsheet, terminal, PDF, or editor because hidden blank rows and line endings can differ even when the text looks identical on screen.

  2. Step 2

    Confirm what one source line means

    Check wrapped cells, multiline values, and accidental trailing rows. A visual wrap inside an application is not always a real line ending, while an embedded newline inside a copied cell may create an additional source line.

  3. Step 3

    Enter one literal prefix or suffix rule

    Type the exact characters and spaces that every selected line needs. The rule is fixed, so a prefix such as 1. does not increment and quote characters do not escape the original value.

  4. Step 4

    Decide blank-line and final-delimiter behavior

    Choose whether empty and whitespace-only lines should remain untouched. If a suffix acts as a delimiter, decide whether the final modified line should omit it; skipped blank lines after that item do not become the final modified line.

  5. Step 5

    Compare counts and separators

    Run the formatter and compare source lines with modified lines. Review the reported LF, CRLF, CR, or mixed separator type and confirm whether a terminal line ending was preserved before copying the output.

  6. Step 6

    Validate the destination, then sample the import

    Use a matching parser or linter for JSON, CSV, SQL, shell, or HTML rather than trusting visual appearance. Import or run a small non-sensitive sample first, check escaping and types, and only then use the full result.

Example

Prepare fixed ticket labels without changing CRLF separators

Input

login timeout
missing invoice
retry failed

Output

OPS: login timeout
OPS: missing invoice
OPS: retry failed

Common mistakes

Using a fixed prefix for sequential numbering

A literal affix repeats exactly. Use Add Line Numbers when each row needs a different increasing value, then verify the numbering pattern separately.

Treating wrapped display text as source lines

A narrow spreadsheet cell or editor pane can wrap one value over several visual rows. Inspect the copied plain text so prefixes are not added to display wraps or embedded multiline fields unexpectedly.

Modifying accidental blank rows

An empty row can receive a prefix and suffix just like a visible value. Compare source and modified counts, and leave blank lines unchanged when they are only separators.

Assuming quotes or commas make valid structured data

Literal quotes do not escape quotes, backslashes, delimiters, or newlines already inside a value. Use the dedicated JSON or CSV converter when the destination requires parsing rules.

Skipping a small destination test

Shells, databases, templates, and importers interpret characters differently. Test a redacted sample and verify the stored or executed result before processing the full list.

FAQ

Can this create 1, 2, 3 numbering automatically?

No. It repeats one literal prefix or suffix. Use Add Line Numbers for an increasing sequence, then return to this tool only if every numbered row also needs the same fixed text.

Will CRLF files be converted to LF?

No. CRLF, LF, CR, and mixed separators are preserved exactly, including a separator at the end of the input. Check the reported line-ending type when the destination depends on it.

Should I modify blank lines?

Modify them only when an empty row is an intentional item. For paragraph gaps or accidental spreadsheet rows, leave blank lines unchanged and compare the modified-line count with the values you expect.

How do I avoid a comma after the final value?

Enter the comma as the suffix and enable the final-suffix option. It removes the suffix from the last line that is actually modified, even if untouched blank lines follow it.

Does wrapping each line in quotes produce valid JSON or CSV?

Not necessarily. Existing quotes, backslashes, commas, and embedded newlines require format-specific escaping. Use a JSON or CSV converter and validate the complete structure before import.

Can I use the result directly in a shell command or SQL query?

Only after context-specific validation and parameterization. Literal prefixes and suffixes do not prevent shell injection or SQL injection, and sensitive production values should not be tested in an untrusted destination.