Pull Request Checklist

Before submitting, make sure you've checked the following:

• Target branch: Please verify that the pull request targets the dev branch.
• Description: Provide a concise description of the changes made in this pull request.
• Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
• Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
• Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
• Testing: Have you written and run sufficient tests to validate the changes?
• Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
• Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
  • BREAKING CHANGE: Significant changes that may affect compatibility
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to our continuous integration processes or workflows
  • chore: Refactor, cleanup, or other non-functional code changes
  • docs: Documentation update or addition
  • feat: Introduces a new feature or enhancement to the codebase
  • fix: Bug fix or error correction
  • i18n: Internationalization or localization changes
  • perf: Performance improvement
  • refactor: Code restructuring for better maintainability, readability, or scalability
  • style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
  • test: Adding missing tests or correcting existing tests
  • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

• Add the known file formats based on the list of file extensions known by github, this list is nearly 1:1 mapping between them but extracted using python

Added

• Updated the known file formats based on the list of file extensions known by github, This will prevent sending these formats to conversion tools like docling, which will not be able to handle these formats.

Data source

https://github.com/github-linguist/linguist/blob/main/lib/linguist/languages.yml

Extraction script:

import yaml

def extract_extensions(input_file, output_file):
    with open(input_file, 'r', encoding='utf-8') as f:
        content = f.read()

    # Parse the YAML-like structure
    data = yaml.safe_load(content)

    # Collect extensions without leading dots
    extensions = []
    for lang, props in data.items():
        if 'extensions' in props:
            for ext in props['extensions']:
                clean_ext = ext.lstrip('.')  # Remove leading dot
                extensions.append(clean_ext)

    # Remove duplicates and sort
    extensions = sorted(set(extensions))

    # Write to output file as a Python list
    with open(output_file, 'w', encoding='utf-8') as f:
        f.write("extensions = [\n")
        for ext in extensions:
            f.write(f"    '{ext}',\n")
        f.write("]\n")

# Example usage
extract_extensions('languages.yml', 'extensions.py')`

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.