Skip to content
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

capitalize "if" and "en" - chicago style #10

Open
kevinlawler opened this issue Oct 7, 2024 · 2 comments
Open

capitalize "if" and "en" - chicago style #10

kevinlawler opened this issue Oct 7, 2024 · 2 comments

Comments

@kevinlawler
Copy link

kevinlawler commented Oct 7, 2024

Remove if and en from short words list

Capitalize if and en as in Chicago style

could add a command-line flag like --chicago if for some reason you're attached to the other styles

@ap
Copy link
Owner

ap commented Oct 16, 2024

The whole thing is an implementation of John Gruber’s style, who basically follows the NY Times Manual of Style. I’m not super keen on deviations from that, though I’m not opposed to adding a switch to tweak it. However I don’t know if --chicago sets the right expectations; is that all that an option with that name should change? Then again, if actually implementing the Chicago style means too many changes, I would balk at that as well, so…

However – the module version of the code already allows modifying the small-word list by changing the @SMALL_WORD array, so you can already make that change yourself if you are using it from other Perl code. And I wouldn’t mind adding a command line option to the program version of the code to read a replacement small-word list from a file. Would that get you sorted?

@kevinlawler
Copy link
Author

My first preference is a --chicago or --cmos. When I looked at it the only change i noticed was this change in the word list. This could be accomplished by a simple setminus of the two items. See https://capitalizemytitle.com/style/Chicago/ I don't think the bar here should be full and total compliance, but rather "what can we quickly get in a script of this scope".

My second preference is to accept the wordlist file change.

My use case is I use this via homebrew but my current version has this hacked in which is senseless and unmaintainable versus having it upstream.

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

No branches or pull requests

2 participants