fontreplacer fontreplacer

Accessibility
Version: 0.0.18
Last Update: 2017-03-22

Overview

fontreplacer is a Chrome extension developed by Zack Guard. According to the data from Chrome web store, current version of fontreplacer is 0.0.18, updated on 2017-03-22.
31 users have installed this extension. 2 users have rated this extension with an average rating of .

Replace any font with any font stack. Useful for Arial → Helvetica.

Replace any font with any font stack. Useful for converting Arial to something decent like Helvetica.

GitHub repo: https://github.com/z-------------/fontreplacer
Commit history: https://github.com/z-------------/fontreplacer/commits
Issues: https://github.com/z-------------/fontreplacer/issues

Rating

2 ratings

Total Installs

31

Information

Last Update

2017-03-22

Current Version

0.0.18

Size

22.23KiB

Author

Zack Guard

Website

None

Category

Accessibility

Latest Reviews

See More

avatar Tynach
2019-10-08

Open source, and does exactly what I wanted. I don't need to replace Arial, but I *do* need to replace Consolas with Inconsolata. And now I can replace other fonts with various open source equivalents, as well!

It seems to have many options I didn't even think about, such as timed repeated replacement (for websites that set the font with JS I presume, and keep setting it wrong). Not sure how well that works, though thankfully I don't (yet) have a need for it.

By the way, if you do get around to replacing the regex matching with something more 'user friendly', please keep regex as an option still. I'm not currently using that option (I'm just using the extension to replace fonts I don't have with ones I do have that should be equivalent), but in other extensions I use for various purposes I've often cycled through extensions until I found one that accepted regular expression matching.

avatar Tynach
2019-10-08

Open source, and does exactly what I wanted. I don't need to replace Arial, but I *do* need to replace Consolas with Inconsolata. And now I can replace other fonts with various open source equivalents, as well!

It seems to have many options I didn't even think about, such as timed repeated replacement (for websites that set the font with JS I presume, and keep setting it wrong). Not sure how well that works, though thankfully I don't (yet) have a need for it.

By the way, if you do get around to replacing the regex matching with something more 'user friendly', please keep regex as an option still. I'm not currently using that option (I'm just using the extension to replace fonts I don't have with ones I do have that should be equivalent), but in other extensions I use for various purposes I've often cycled through extensions until I found one that accepted regular expression matching.

avatar Tynach
2019-10-08

Open source, and does exactly what I wanted. I don't need to replace Arial, but I *do* need to replace Consolas with Inconsolata. And now I can replace other fonts with various open source equivalents, as well!

It seems to have many options I didn't even think about, such as timed repeated replacement (for websites that set the font with JS I presume, and keep setting it wrong). Not sure how well that works, though thankfully I don't (yet) have a need for it.

By the way, if you do get around to replacing the regex matching with something more 'user friendly', please keep regex as an option still. I'm not currently using that option (I'm just using the extension to replace fonts I don't have with ones I do have that should be equivalent), but in other extensions I use for various purposes I've often cycled through extensions until I found one that accepted regular expression matching.

avatar Tynach
2019-10-08

Open source, and does exactly what I wanted. I don't need to replace Arial, but I *do* need to replace Consolas with Inconsolata. And now I can replace other fonts with various open source equivalents, as well!

It seems to have many options I didn't even think about, such as timed repeated replacement (for websites that set the font with JS I presume, and keep setting it wrong). Not sure how well that works, though thankfully I don't (yet) have a need for it.

By the way, if you do get around to replacing the regex matching with something more 'user friendly', please keep regex as an option still. I'm not currently using that option (I'm just using the extension to replace fonts I don't have with ones I do have that should be equivalent), but in other extensions I use for various purposes I've often cycled through extensions until I found one that accepted regular expression matching.