[Bug]: Arabic Text Reversal and RTL Encoding Issues During Export

Aperta
  • Qualcosa non va?
#979 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
documentation

Direzione di ricerca

The issue covers several converters (PDF to Markdown, PDF to Text, PowerPoint to PDF) with no file, test or entry point named, and the Files involved field is empty. Start by reproducing with an Arabic PDF and locating the text extraction path in the C# converter code, then check how bidi ordering is applied. Done would mean extracted Arabic text reads in logical order in the output, but the fix needs bidi and shaping knowledge, so this is not a good first issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
What happened?
Summary :

When exporting or converting files containing Arabic text (e.g., PDF to Markdown, PDF to Text, or PowerPoint to PDF) using Filee, the Arabic characters and words are rendered in reverse order (Left-to-Right instead of Right-to-Left), and characters appear disconnected or mirrored.

1. Environment
  • Application Name: Filee
  • Affected Operations:
  • PDF to Markdown conversion
  • PDF to Text extraction
  • PowerPoint to PDF conversion
  • Language/Encoding: Arabic (RTL - Right-to-Left scripts)
2. Steps to Reproduce
  • Attempt to export or convert the file into Markdown, plain text, or PDF.
  • Open the resulting output file.
3. Expected Behavior
  • Arabic text should maintain correct Unicode shaping and Right-to-Left (RTL) reading direction.
  • Words and letters should appear in their standard, readable form (e.g., "البطولة المفتوحة").
4. Actual Behavior
  • Text strings are extracted or rendered backwards and broken.
  • Examples observed from exports:
  • البطولة appears as ةلبطولةا or البطولةا.
  • المفتوحة appears as ةحوتفملا.
  • Formatting and spacing get corrupted due to improper handling of bidirectional text (Bidi) and Arabic script shaping.
5. Additional Notes

Please investigate the text extraction and rendering engine (OCR / conversion pipeline) to ensure proper Unicode support, Bidi algorithm handling, and RTL text direction preservation for Arabic documents.

What did you expect?

Before Converting

Image

After Converting

Image
Steps to reproduce
  1. Attempt to export or convert the file to Markdown, plain text, or PDF.
  2. Open the resulting output file.
Files involved

No response

Filee version

2.2.0

Operating system

Win10

Engines page status

No response

Log
Lingua principale
C#
Stelle
3.6k
Fork
192
Merge medio
7h 17m
PR unite (30g)
393

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di KnifeLemon/Filee

Tutte le issue di KnifeLemon/Filee

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.