REPT in Collabora Office: Build Small Text Patterns with Explicit Counts and Separators
Use Collabora REPT for controlled repetition, visible unit markers and fixed-length labels without guessing undocumented size limits.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: REPT repeats a supplied text string a specified number of times. =REPT("ab";3) is expected to return ababab. It inserts no separator between copies unless the separator is part of the supplied text.
Availability and version history
- Introduced: original Collabora release and launch date are not established by the sources reviewed.
- Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
- Platform scope: online and mobile deployments are not inferred from desktop documentation.
- Checked: October 14, 2026. Direct function documentation and independently modeled text controls; no native Collabora test was performed.
Syntax and controlled counts
=REPT(text;number)
text is the repeated string, and number is the repetition count. These examples use small positive whole numbers. Collabora’s direct page defines the operation but does not publish an exhaustive zero, fractional, negative or maximum-length policy.
The result is text. It does not create multiple cells, duplicate rows or repeat a calculation with different inputs. One formula returns one combined string.
Example 1: inspect exact boundaries
Try these controls in separate cells:
=REPT("ab";1)
=REPT("ab";2)
=REPT("ab";3)
Expected text: ab, abab, ababab. Each additional copy contributes two characters. Corresponding LEN results are 2, 4 and 6.
If a source label already contains punctuation or spaces, those characters repeat too. REPT has no separate option for inserting a delimiter between copies while omitting one at the end.
Example 2: make a separator part of the pattern
=REPT("go|";3)
Expected text: go|go|go|, length 9. The final vertical bar is intentional because it belongs to every repeated unit. If the receiving format forbids a trailing separator, use a different construction rather than assuming REPT trims it.
Compare =REPT("go";3) with expected gogogo. The count is identical; the repeated unit determines all spacing and punctuation.
Advanced example: create a small visible quantity marker
Put positive counts 1, 3, 5 in A2:A4. In B2 enter and fill down:
=REPT("|";A2)
Expected markers are |, ||| and |||||. Keep the numeric count in column A, where it can still be summed or compared. A marker can assist visual scanning, but different fonts and display widths make it unsuitable as a precision chart on its own.
A separate LEN column should return 1, 3, 5 for these one-character units. If you change the unit to [], the expected lengths become 2, 6, 10. Repetition count and character count are equal only when the repeated unit has one character.
Advanced example: construct a fixed-width display identifier
For a deliberately text-valued source 17 and a known five-character display width, use:
=REPT("0";3)&"17"
Expected text: 00017. This is a text label, not a number with a cell format. If the source already has five or more characters, this exact three-zero rule would be wrong; determine the required padding before applying a formula to other inputs.
For the explicit four-character source 2846, =REPT("0";1)&"2846" gives 02846. Both examples supply positive counts, without relying on an unverified zero-count boundary or silently dropping characters from an overlong identifier.
Advanced check: distinguish repetition from multiplication
=REPT("12";3) gives expected text 121212. Arithmetic =12*3 gives numeric 36. Similar-looking inputs express entirely different operations.
Do not use a repeated-text output as proof of a numeric value or a record count unless the encoding convention is explicitly controlled. Preserve the source data and use the text only for its intended presentation role.
Practical limits
Large requested outputs can be inconvenient even before reaching an application limit. The small controls are neither a maximum-size benchmark nor a claim that an Excel limit applies to Collabora. No native count-coercion, negative-count error or performance matrix was established. Keep counts bounded by the actual display task and inspect a representative output before filling a large range.
References and verification
The dedicated Collabora function page was reviewed. Expected outputs are independently modeled text controls, not captured results from the application. Extended-character, coercion and deployment-specific behavior retain the limits stated above.