Skip to content

fix: non-ASCII characters silently ignored in content gap analysis (#122)#163

Open
fazalpsinfo-cmyk wants to merge 1 commit into
OpenAgentHQ:mainfrom
fazalpsinfo-cmyk:fix/non-ascii-gap-122
Open

fix: non-ASCII characters silently ignored in content gap analysis (#122)#163
fazalpsinfo-cmyk wants to merge 1 commit into
OpenAgentHQ:mainfrom
fazalpsinfo-cmyk:fix/non-ascii-gap-122

Conversation

@fazalpsinfo-cmyk

Copy link
Copy Markdown

Fix: Non-ASCII characters in content gap detection

The regex [a-zA-Z] in _check_content_gaps only matches ASCII letters,
silently ignoring non-ASCII characters (accented chars, CJK, emoji, etc.).

Replaced with [^\W\d_] which matches any Unicode letter in Python 3's
Unicode-aware re module. This is a one-character change with no behavioral
impact on ASCII-only content.

Fixes #122

Support my work: https://buymeacoffee.com/muhamedfazalps

…penAgentHQ#122)

The content gap detection used [a-zA-Z] which only matches ASCII
letters, silently ignoring non-ASCII characters (accented chars, CJK,
emoji, etc.). Replaced with [^\W\d_] which matches any Unicode letter
in Python 3's Unicode-aware re module.

Fixes OpenAgentHQ#122
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix: Non-ASCII characters silently ignored in content gap analysis

1 participant