fix: comprehensive ASCII cleaning script to resolve all FORD UTF-8 parsing errors #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
GitHub Pages continues to show 404 errors for example HTML documentation despite previous fixes:
Root Cause Analysis
Investigation revealed that FORD in the CI environment was still reporting UTF-8 parsing errors for multiple files:
These parsing errors prevent FORD from generating HTML files, causing 404 errors on GitHub Pages.
The Solution
Created a comprehensive UTF-8 cleaning script
scripts/clean_example_docs_utf8.shthat:tr -cd '\11\12\15\40-\176'Files Fixed
Verification
All example files are now confirmed
us-asciiencoding:Future Prevention
The script can be run anytime to ensure all example documentation remains FORD-compatible:
This comprehensive fix should resolve all remaining GitHub Pages 404 errors by ensuring FORD can parse every example file successfully in any CI environment.