admk / admk/sembr

Enhanced Markdown Support

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
48
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Enhanced Markdown Support

Summary

This issue tracks the comprehensive markdown support implementation that landed this week, addressing issues #3 (bullet point merging) and #1 (punctuation handling) while introducing full markdown syntax awareness.

What's Implemented
  • Complete markdown processor with semantic line breaks respecting markdown syntax
  • Automatic file type detection using Magika ML-based content analysis
  • Syntax-aware processing for:
    • Bullet points and numbered lists (fixes #3)
    • Block quotes with proper prefix preservation
    • Code blocks (fenced and indented)
    • Headers with ATX and Setext styles
    • Links, images, and reference-style links
    • Emphasis markers (italic, bold)
    • Punctuation handling including % symbols (fixes #1)
Technical Details
  • New processors: sembr/processors/markdown.py (366 lines) with comprehensive AST parsing
  • File type detection: Magika-based auto-detection in sembr/processors/utils.py
  • DRY architecture: Refactored processor system with base classes in sembr/processors/base.py
  • Backward compatibility: Preserves existing LaTeX and plain text support
Known Limitations
  • Nested list edge cases with mixed indentation
  • Footnote reference positioning
  • Task list checkbox alignment
How to Test
# Install latest dev version
uv tool install sembr --from git+https://github.com/admko/sembr.git

# Test markdown files
sembr -i README.md -o README_sembr.md

# Force markdown processing
sembr -t markdown -i input.md -o output.md
Related Issues
  • Closes #3 - Bullet point merging issues
  • Closes #1 - Punctuation disruption (%)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue describes an implementation already landed in sembr/processors/markdown.py, with related detection and base-class changes in sembr/processors/utils.py and sembr/processors/base.py. Start by reviewing those files and running the documented CLI commands; done would require a separately defined change beyond the listed implementation and known limitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.