def rbsr_split(text, max_size=1000, level=0): # Level 0: Section (## Header) # Level 1: Paragraph (\n\n) # Level 2: Sentence (.) # Level 3: Word ( ) if len(tokenizer.encode(text)) <= max_size: return [text]
Use pdfplumber or unstructured.io to extract bounding boxes . RBS-R cares about Y-coordinates. If two text blocks have the same Y-axis, they are the same line. If the Y-axis delta is large, it’s a new paragraph.
How to combine RBS-R with Latex OCR for mathematical PDFs. Have you tried recursive splitting? Share your chunking horror stories in the comments. rbs-r pdf
for segment in splits: # Re-add delimiter except for first segment if current_chunk: segment = delim + segment temp_chunk = current_chunk + segment if len(tokenizer.encode(temp_chunk)) <= max_size: current_chunk = temp_chunk else: if current_chunk: chunks.append(current_chunk) # Recursively split the oversized segment at the next level if level + 1 < len(delimiters): chunks.extend(rbsr_split(segment, max_size, level + 1)) else: # Force split at word boundary chunks.append(segment) current_chunk = ""
return chunks The magic of RBS-R for PDFs isn't just the splitting; it's the inheritance . If the Y-axis delta is large, it’s a new paragraph
if current_chunk: chunks.append(current_chunk)
chunks = [] current_chunk = ""
# Use the current level's delimiter delim = delimiters[level][0] splits = text.split(delim)
If you have a bulleted list with 50 items, a recursive split might try to split at the sentence level inside a bullet, breaking the list semantic. Pre-process lists. Convert \n- Item into a delimiter like [LIST_BREAK] before splitting, then reconstruct. Conclusion: Stop Chunking, Start Structuring RBS-R is not an LLM. It’s not a vector database. It is a hydraulic press for your PDFs—it applies pressure until the content fits the context window, but it always breaks at the joints . Share your chunking horror stories in the comments