Reviews for Novel Name Replacer
Novel Name Replacer by Shizu
1 review
- Rated 5 out of 5by Tianna, 5 days agoWorks fantastically! The only true wish I have for it is that there should a 'match case' option for names that double as actual words such as On, Cage, or Lock from Trash of the Count's Family. Replacing On's name with my preferred spelling of Ohn changes every instance of the lowercase 'on' to it as well.
There are several features I think would elevate the experience as well, if you're willing to read them!
* Does not work in reader view.
* I think there should be a more general match transform function; if a character is yelling in capslock, it's gonna look funny to suddenly be lowercase, lol.
* As there is an unlimited amount of replacements, I think the name fields should be collapsible, possibly reorder-able.
* The tabbed menu extends beyond it's window scope for me? There's a horizontal scrollbar. It's a nitpick tbh.
* Not too sure why, but I can't replace anything in parenthesis (). Without those characters works fine however (on AO3 at least).Developer response
posted 17 minutes agoThank you for the detailed feedback and the positive review.
I have implemented the following fixes in version 1.3.0:
1. Match case option - Added a case-sensitive checkbox for each replacement to handle names like "On" that double as common words.
2. Smart case preservation - The extension now maintains capitalization patterns (all caps stay all caps, etc.).
3. Collapsible replacement fields - Each replacement can be collapsed by clicking its header, which shows a preview of the replacement pair.
4. Reorderable replacements - Replacements can now be dragged and dropped to reorder them.
5. Fixed horizontal scrollbar - Adjusted the popup width and added proper responsive constraints.
6. Fixed parenthesis issue - Improved the regex pattern to correctly handle text inside parentheses and other special characters.
Regarding Reader View support: After testing, Reader View resets the page content which removes the replacements. This is a limitation I cannot work around.
All other requested features have been successfully implemented. Thank you again for the thorough feedback.