-
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
Using custom Font #5
Comments
First of all, thanks for letting me know of this issue. |
Thanks for your fast response! |
This weekend I've been working on this and, while I thought this would be pretty straightforward, it seems it will take a bit longer to implement than planned, as, right now, the chrome extensions API doesn't support changing a request body[1][2]. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=104058 |
It seems I won't have the time needed to look into this (I don't even know if it's possible without submitting a PR to chome&firefox) till a few months later, so it will probably take a while. |
Wow, good job! |
Thanks, if you find any issue installing it just let me know :) |
Just had to add "_" in front of the file name. "_gkai00mp.ttf" |
Hello, I am also kind of getting into same issue with my decks. All the external images, js files and css files in the card returns error in console as file_not_found. I am using the annotation of '_' before each file and it works perfectly fine in Anki. In chrome, only the html part shows up but not the images, js and css those are in collection.media. |
Hello,
i'm using a custom font for my chinese cards.
Unfortunately since the AnkiConnect update, that font doesn't work anymore.
Console output:
chrome-extension://ihoaepdiibjbifnhcjoaddgcnfgjmjdk/_gkai00mp.ttf net::ERR_FILE_NOT_FOUND
When I put that font file in
C:\Users\<USER>\AppData\Local\Google\Chrome\User Data\Default\Extensions\ihoaepdiibjbifnhcjoaddgcnfgjmjdk\0.4_0
it works for 1 second after Chrome detects an extension corruption.I kindly ask you to add a function for custom fonts.
The text was updated successfully, but these errors were encountered: