Skip to content

docs: Document Windows terminal encoding support & troubleshooting#249

Open
MervinPraison wants to merge 1 commit intomainfrom
claude/issue-244-20260424-1011
Open

docs: Document Windows terminal encoding support & troubleshooting#249
MervinPraison wants to merge 1 commit intomainfrom
claude/issue-244-20260424-1011

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

Fixes #244

This PR adds comprehensive documentation for Windows terminal encoding support and troubleshooting, addressing the automatic UnicodeEncodeError fixes from PraisonAI PR #1545.

Changes

Updated docs/installation.mdx

  • Added Windows-specific note about automatic encoding detection
  • Included PowerShell and CMD commands for enabling full UTF-8 support

Created docs/features/windows-terminal-encoding.mdx

  • Complete troubleshooting guide with symptom, root cause, and solutions
  • Mermaid decision flow diagram showing CLI output mode selection
  • Manual override instructions for PowerShell, CMD, and permanent env vars
  • Best practices for Windows Terminal, WSL, and system configuration
  • Follows AGENTS.md standards: Steps, AccordionGroup, CardGroup components

Updated docs.json

  • Registered new page under Features → Advanced Features group
  • Maintains valid JSON structure

Acceptance Criteria Met

✅ docs/installation.mdx Windows tab includes encoding note
✅ Comprehensive troubleshooting page with Mermaid diagram
✅ Page registered in Features group (not Concepts)
✅ docs.json is valid JSON
✅ Searchable for UnicodeEncodeError/PYTHONIOENCODING
✅ Follows AGENTS.md style guidelines

Generated with Claude Code

…ixes #244)

- Add Windows encoding note to installation.mdx Windows tab
- Create comprehensive troubleshooting guide in docs/features/windows-terminal-encoding.mdx
- Include Mermaid decision diagram with AGENTS.md color scheme
- Cover automatic mitigation, manual UTF-8 setup, and best practices
- Register new page in docs.json under Features > Advanced Features

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 24, 2026 10:15
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 24, 2026

Warning

Rate limit exceeded

@MervinPraison has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 27 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 27 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 016c0e1c-d16c-46cc-8d7a-d3f6310d3970

📥 Commits

Reviewing files that changed from the base of the PR and between 9480b78 and 3d39a0f.

📒 Files selected for processing (3)
  • docs.json
  • docs/features/windows-terminal-encoding.mdx
  • docs/installation.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/issue-244-20260424-1011

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces documentation for Windows Terminal Encoding, detailing how PraisonAI handles legacy code pages and providing setup instructions for UTF-8. The review feedback suggests replacing version placeholders with specific version numbers, correcting language labels in code blocks where CMD syntax was labeled as bash, and addressing invalid comments in JSON examples to ensure compatibility with documentation tools.


<Steps>
<Step title="Automatic Handling">
PraisonAI ≥ v0.0.x automatically detects legacy Windows code pages and renders ASCII-safe output:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The version placeholder v0.0.x should be replaced with the specific version where automatic encoding detection was introduced to provide accurate guidance to users.

Comment on lines +111 to +118
```bash
# Temporary fix
set PYTHONIOENCODING=utf-8
praisonai --help

# Or upgrade to latest version
pip install --upgrade praisonai
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The code block is labeled as bash, but it contains Windows CMD syntax (set) and shell-style comments (#). For clarity and correctness in a Windows-focused guide, the label should be changed to cmd and the comments should use REM or ::.

Comment on lines +137 to +148
```json
// Windows Terminal settings.json
{
"profiles": {
"defaults": {
"font": {
"face": "Cascadia Code"
}
}
}
}
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The JSON code block contains a comment (//), which is not valid in standard JSON. While Windows Terminal's settings.json supports JSONC (JSON with Comments), some documentation tools or strict parsers might fail. It is recommended to remove the comment from the block or use the jsonc language identifier if supported by the documentation framework.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

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.

docs: Document Windows terminal encoding support & troubleshooting (from PraisonAI PR #1545)

2 participants