-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle case changes in article titles #26
Comments
You mean things like That may in itself cause trouble under Windows or a Mac with the default case insensitive file system, but Linux should be fine. I'd be willing to take a look at any pull request if you want to try fixing this. Other can you make a small test wiki and provide the XML dump as a test case (I don't have ready access to a MediaWiki instance to try this on myself anymore)? |
Actually rather than making a small test case, if you are willing to send me your real XML dump (e.g. to my Google Mail address), and details of the page(s) which break, I might be able to try it out some time next week. |
I ran into this myself in some recent testing, and it is due to trying to run this on a case insensitive file system (like Windows and some macOS drives). As part of the Python 3 work going into v1.1.0, this will now trigger an error and abort. Try running under Linux, or if using a Mac, a case sensitive file system. See 5aad3f8 and the preceding commits. It may be possible to handle the special case of renaming the page's case, i.e. git remove old case, git add new case, so leaving this issue open. |
In v2.0.0 of the script (i.e. the current master), the process is now:
This means the two files So, sadly this issue as a WON'T FIX. And this was annoying as my primary machine is a Mac where I couldn't run this. |
The script appears to not correctly handle case changes in article titles. It aborts with a git error about unknown files due to
git add
andgit commit
referencing a filename with incorrect case.The text was updated successfully, but these errors were encountered: